MCP server

moco-mcp bundles the whole registry into an MCP server, so Claude can browse, search, and install components for you.

Setup

One command:

Terminal

claude mcp add moco -- npx -y moco-mcp

Or add it to your project’s .mcp.json so the whole team gets it:

.mcp.json

{
  "mcpServers": {
    "moco": { "command": "npx", "args": ["-y", "moco-mcp"] }
  }
}

Add the same server block to claude_desktop_config.json (Settings → Developer → Edit Config):

claude_desktop_config.json

{
  "mcpServers": {
    "moco": { "command": "npx", "args": ["-y", "moco-mcp"] }
  }
}

Tool	What it returns
`list_components`	Every item with title, description, and tags
`search_components`	Query by name, tag, or description
`get_component`	Full source files, dependencies, and usage example for one item
`get_theme`	The token contract, for retheming
`get_setup`	One-time install instructions

You: “add a before/after slider to my post”
Claude calls search_components and finds compare
Claude calls get_component and get_setup
Claude writes compare.tsx + compare.css into components/moco/ and wires the import

No CLI, no copy-paste, no tab-switching.

Read-only. All five tools are annotated read-only — the server never writes to your filesystem. Claude writes the files, under your normal permission flow.
No network. The registry is bundled into the package at build time; the server makes no network calls at runtime.
Nothing to configure. No tokens, no env vars, no state.