Connect Gemini CLI to shads

Install

Add this to the config file:

~/.gemini/settings.json (or .gemini/settings.json in a project)

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

Streamable HTTP servers use the “httpUrl” key.

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.

Gemini CLI cannot read environment variables for headers, so the key goes into the config file. Do not commit that file.

{
  "mcpServers": {
    "shads": {
      "httpUrl": "https://mcp.shads.app",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Check that it works

Run /mcp inside Gemini CLI.

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

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