Skip to main content

Real-Time Prices

Live and historical prices, market caps, and trading volumes.

Market Intelligence

Exchange data, trending coins, and market analytics.

Onchain Analytics

Token and pool data across DEXes and networks.

​
Servers

ServerEndpointDetails
Free (Keyless)https://mcp.api.coingecko.com/mcpNo API key needed.
Shared rate limits.
Use your API keyhttps://mcp.pro-api.coingecko.com/mcpCoinGecko API key required.
Higher limits, full tool set.
Local@coingecko/coingecko-mcpPro or Demo API key.
Runs on your machine. GitHub →
  • Both servers support /mcp (Streamable HTTP) and /sse (Server-Sent Events).
  • Always prefer /mcp — only fall back to /sse if your client doesn’t support Streamable HTTP.
See the full list of available tools and methods.

​
Connect to Remote Server

1

Add connector

Go to Settings > Connectors on claude.ai.
2

Enter server details

  • Name: CoinGecko
  • Remote MCP server URL:
    ServerURL
    Free (Keyless)https://mcp.api.coingecko.com/mcp
    Use your API keyhttps://mcp.pro-api.coingecko.com/mcp
Click Add.Using your API key opens a browser tab to enter it on first connection.
Get an API key →

​
Setup your Local Server

Run the server on your machine using @coingecko/coingecko-mcp. Requires Node.js.
1

Open config

Edit claude_desktop_config.json (find this file).
2

Add server

{
  "mcpServers": {
    "coingecko": {
      "command": "npx",
      "args": [
        "-y",
        "@coingecko/coingecko-mcp"
      ],
      "env": {
        "COINGECKO_PRO_API_KEY": "YOUR_API_KEY",
        "COINGECKO_ENVIRONMENT": "pro"
      }
    }
  }
}
Replace YOUR_API_KEY with your actual API key.
Get a free Demo key or upgrade to Pro →
3

Restart Claude Desktop

Restart to load the new server.

​
FAQ

The Free server requires no authentication and uses shared rate limits. The API key server gives you higher rate limits and access to the full tool set — including premium endpoints available on your CoinGecko plan.
Use a local server if you need full control over the runtime, want to avoid browser-based OAuth, or prefer passing your API key via environment variables instead of the browser auth flow.
/mcp uses Streamable HTTP — the newer, recommended transport. /sse uses Server-Sent Events, an older protocol. Always prefer /mcp unless your client only supports SSE.
Any client that supports the Model Context Protocol — including Claude (Web, Desktop, Code), Cursor, Windsurf, and others. The setup steps on this page use Claude as an example, but the endpoints and configs work with any MCP-compatible client.
Yes. Each tool call the AI makes through MCP triggers one or more API requests, which count toward your plan’s rate limit and credits.

Share Feedback

Help us improve MCP — share your suggestions and feedback.