MCP Server
Let Claude search and install components from any conversation. The ParticleUI MCP server exposes your component library as a set of tools that Claude Code — or any MCP-compatible AI client — can call directly.
What the MCP server enables
Setup
Add to Claude config
Add the MCP server with a single command in your terminal:
claude mcp add @particleui/mcpOr configure it manually in your Claude config file:
{
"mcpServers": {
"particleui": {
"command": "npx",
"args": ["-y", "@particleui/mcp"],
"env": {
"PARTICLEUI_TOKEN": "pui_your_token_here"
}
}
}
}Restart Claude Code
Quit and reopen Claude Code (or run /mcp restart in an existing conversation) to pick up the new server. You should see particleui listed when you type /mcp.
Use it in conversation
Ask Claude in plain language — it will call the right tool automatically:
Add a glowing card component to my project.
I'll search for a glowing card component in ParticleUI.
Calling search_components with “glowing card”…
Found GlowCard — a card with a radial glow that follows your cursor. Installing it now.
Calling install_component with “glow-card”…
Done. GlowCard has been added to src/components/ui/glow-card.tsx.
Available tools
The server exposes four tools that Claude can call:
list_componentsReturns the full catalogue of available components with names, descriptions, and Pro/free status.
get_componentFetches the full source, props API, and usage examples for a single component by name.
install_componentRuns the particleui-cli install command for a component in your project directory.
search_componentsSemantic search across all components — finds the best match for a description like "animated card with tilt effect".
Other MCP clients
The ParticleUI MCP server follows the Model Context Protocol spec and works with any compatible client including Cursor, Zed, and custom agent frameworks. The server command is always npx -y @particleui/mcp — consult your client's docs for the config format.