Skip to content

Connect 21st.dev to Gemini CLI

Community marketplace of React components, templates, shadcn themes and shaders, with a hosted MCP server for agents. Browsing is free; copying more than a few components a day needs a membership.

MCP serverOfficialChecked 2026-11-16

Before you start

  • Gemini CLI installed (see its MCP documentation (opens in a new tab)).
  • 21st.dev is available on macOS, Windows, Linux and the web.
  • Get an API key at 21st.dev/mcp and set it as API_KEY_21ST in your environment. Keys from the old Magic console no longer work. AI generation tools only appear when your account has AI access. Each component page also shows its own shadcn CLI command.
  1. Step 1: Add 21st.dev to Gemini CLI

    Add it from the terminal

    Run this in your project folder. It saves the server to the project's .gemini/settings.json.

    Terminal
    gemini mcp add --transport http --header 'x-api-key: ${API_KEY_21ST}' 21st-dev https://21st.dev/api/mcp

    Or edit the config file

    Add this to .gemini/settings.json in your project, or to ~/.gemini/settings.json to use it in every project.

    .gemini/settings.json
    {
      "mcpServers": {
        "21st-dev": {
          "httpUrl": "https://21st.dev/api/mcp",
          "headers": {
            "x-api-key": "${API_KEY_21ST}"
          }
        }
      }
    }
    Good to know
    • Gemini CLI reads API_KEY_21ST from your environment when it loads its settings, so the token stays out of the file.
  2. Step 2: Check it's connected

    Terminal
    gemini mcp list

    In a Gemini CLI session, run /mcp to see each server, its status and its tools.

  3. Step 3: Try a first request

    Ask Gemini CLI something that only works with 21st.dev connected:

    Say to Gemini CLI
    Search 21st.dev for a pricing section that fits this page and show me how to adapt it.

If it doesn't work

  • Since June 2026, Gemini CLI works with a paid Gemini API key or an enterprise licence. If you signed in with a personal Google account, use Google Antigravity instead.
  • gemini mcp add saves to the project's .gemini/settings.json by default. Add --scope user to save it to ~/.gemini/settings.json for every project.
  • Local servers only show as connected in folders you trust. Run gemini trust in the project folder.
  • Gemini CLI hides environment variables that look like secrets from servers unless the server's env block lists them.