MCP for Grok

Before you start

The agent can only install what the project is set up to receive. Add the @efferd registry first. Quick Setup walks through that.

Pro blocks need EFFERD_REGISTRY_TOKEN in .env.local. Free blocks do not need a token. The server reads components.json, so it uses the style you already chose.

Add the server

From the project, register the local shadcn server. Everything after -- is the command Grok runs:

grok mcp add shadcn -- npx shadcn@latest mcp

That writes ~/.grok/config.toml. The same table by hand:

[mcp_servers.shadcn]
command = "npx"
args = ["shadcn@latest", "mcp"]

Grok also loads a project .mcp.json and .cursor/mcp.json, so a Claude or Cursor setup in this repo is picked up too.

Confirm

Run grok mcp list. shadcn should be listed. grok mcp doctor shadcn reports whether the process started.

Try it

Once the server is connected, copy a prompt and give it to your agent.

Find a hero section from @efferd

Build a landing page using @efferd blocks

Add a pricing block from @efferd

Guidelines

• Match style to the UI you initialized. Use radix-* for Radix, or base-* for Base UI.
• For a large block, have the agent run npx shadcn@latest view @efferd/hero-1 first so it can look at the files before adding them.
• Keep EFFERD_REGISTRY_TOKEN out of git. A Pro install stops if the token is missing.
• Copy the item name from the block preview. A name you invent will not install.
• Leave {style} in the registry URL. The agent fills it in from components.json.

Next steps

• Ask for a block by the name on its preview. The prompts above are a starting point.
• If shadcn does not connect, the shadcn MCP documentation covers troubleshooting.
• Other clients are on the MCP page.