Connect Cursor to shads

Install

Add to Cursor

The button opens Cursor and asks you to confirm. It installs the public tools; add a key afterwards for Pro tools.

Or edit the config file by hand:

~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this repo)

{
  "mcpServers": {
    "shads": {
      "url": "https://mcp.shads.app"
    }
  }
}

Use the project file for team-shared config and keep the key in an environment variable.

Add your API key (optional)

Skip this for public themes. Pro adds your saved themes and AI generation.

Create a key in Account settings → API keys (Pro plan). Keep it out of git.

Export SHADS_API_KEY in your shell profile, then use:

{
  "mcpServers": {
    "shads": {
      "url": "https://mcp.shads.app",
      "headers": {
        "Authorization": "Bearer ${env:SHADS_API_KEY}"
      }
    }
  }
}

Check that it works

Open Cursor Settings → Tools & MCP and check that shads shows a green status dot.

Then ask your assistant:

Use the shads MCP server and run connection_status.

It returns the server version, whether your API key was accepted, and which tools are unlocked.

Try it

• Use shads to install the Workspace theme in this repo.
• Use shads to list the starter themes.
• Use shads to validate this theme.json.

More jobs: recipes.

Troubleshooting

• shads is listed but disabled. Enable it in Cursor Settings → Tools & MCP, then start a new chat.
• The agent ignores shads. Name the server in your prompt (for example “use shads to …”) when several MCP servers are active.

More general fixes: MCP troubleshooting. Vendor documentation: Cursor MCP docs (checked 2026-10-19).