MCP

Give coding agents a structured map of every component.

Every registry item carries agent-facing metadata: a one-line summary, when to use it, when not to, props, pitfalls, accessibility notes and examples. The Fujin MCP server serves it in layers so an agent only pays for what it reads.

ToolReturnsTypical size
list_itemsName, type and summary for every item~35 tokens per item
get_itemFull guidance for one item, no sourcea few hundred tokens
get_item_sourceThe files that would be installedfull source
search_itemsRanked matches for a querysmall
get_install_commandExact command, including dependenciesone line

Setup

npx fujin mcp init --client claude

Or add it by hand:

.mcp.json
{
  "mcpServers": {
    "fujin": {
      "command": "npx",
      "args": ["-y", "@fujin/mcp@latest"]
    }
  }
}

The shadcn MCP server (npx shadcn@latest mcp) also works: it reads the same registry, and the metadata is included in every item under meta.fujin.

Markdown docs

Every docs page is also available as plain markdown. Append .md to the URL: /docs/components/button.md.

On this page