appCN MCP server

@app-cn/mcpgives your AI coding agent — Claude Code, Cursor, Windsurf, Codex — first-class access to appCN. Agents can discover components, read their full docs, get the exact install command, and learn appCN's design tokens, so the code they write matches the system instead of guessing.

Add it to your agent

The server runs on demand via npx — nothing to install globally. It reads from the live appCN registry, so it always reflects the latest published components.

Claude Code

claude mcp add appcn -- npx -y @app-cn/mcp

Cursor / Windsurf (mcp.json)

{
  "mcpServers": {
    "appcn": {
      "command": "npx",
      "args": ["-y", "@app-cn/mcp"]
    }
  }
}

VS Code (.vscode/mcp.json)

{
  "servers": {
    "appcn": {
      "command": "npx",
      "args": ["-y", "@app-cn/mcp"]
    }
  }
}

Tools

Five tools take an agent from “what’s available?” to a correctly-installed, on-brand component.

Tool	What it does
list_components	List every appCN component (optionally filtered to base or ai), each with its one-line delight detail.
search_components	Find components by intent — “chat input”, “voice indicator”, “streaming message”.
get_component	The full payload for one component: docs, source files, npm + registry dependencies, and the install command.
get_install_command	The exact command to add a component — appCN CLI, shadcn URL, or namespaced — per package manager.
get_design_guide	appCN’s motion/haptic tokens and house rules, so the code your agent writes feels like appCN.

Environment

Point the server at a different registry for local development or a self-hosted fork.

# pass via your MCP client's env config
APPCN_REGISTRY_URL=http://localhost:3100/r

Defaults to https://appcn.vercel.app/r — the same registry the CLI and the install commands on every component page point at.

How it relates to shadcn’s MCP

appCN is a standard shadcn-compatible registry, so shadcn’s own MCP can install appCN components too.

Register "@app-cn" in your components.jsonand shadcn's MCP can browse and install appCN by name. What @app-cn/mcpadds on top is the appCN-specific knowledge the generic registry JSON doesn't carry: the delight detail, usage examples, accessibility notes, and the motion/haptic design guide — the things that make agent-authored code actually feel like appCN.