Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

MCP

MCP clients

A setup guide for each of 38 clients, plus any other that speaks MCP. Each page has the config, with your URL filled in when you're signed in.

The shadcn.io MCP works in any client that speaks MCP. Each guide has the config with your URL already in it when you're signed in with Pro, how to check the connection, and that client's own FAQ.

Editors

Terminal agents

Extensions

Apps and cloud agents

Any other client

Your MCP URL is on your dashboard, with Pro. The server speaks MCP over HTTP (streamable HTTP), so most clients take the URL as is: add a remote server named shadcnio and paste it.

With a header

Where a client sets headers, keep the token out of the URL: use the plain endpoint as the URL and send Authorization: Bearer <your token>. Security and limits says why.

Through mcp-remote

A client that only runs local commands (stdio) reaches the server through the mcp-remote bridge, which needs Node.js:

{
  "mcpServers": {
    "shadcnio": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "<your MCP URL>"]
    }
  }
}

On Windows, run npx through cmd:

{
  "mcpServers": {
    "shadcnio": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "mcp-remote", "<your MCP URL>"]
    }
  }
}

Then check the connection: Troubleshooting calls the server by hand, without a client.

FAQ

Which clients have a guide?

  1. Editors, terminal agents, extensions, and apps are grouped on this page. Each guide has the config, a way to check it, and that client's own questions.

What if my client isn't listed?

If it speaks MCP over HTTP, add a remote server named shadcnio and paste your URL. A client that only runs local commands uses the mcp-remote block on this page.

Why is the config empty until I sign in?

The URL holds your token. Signed in with Pro, Copy takes the whole config. Signed out, the page asks you to sign in first.

Should the token go in the URL or a header?

A header, when the client allows it: Authorization: Bearer, and the plain endpoint as the URL. A token in a query string can land in logs. Security and limits says why.