# CoinGecko MCP server > Query crypto prices, market data, trending coins and on-chain DEX data from the CoinGecko API. - Listing: https://mcp.tc/i/coingecko - Connect: use the server's own URL `https://mcp.api.coingecko.com/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: none - Category: [Finance & Payments](https://mcp.tc/c/finance-payments) - Vendor: CoinGecko - Homepage: - Repository: - Package: npm `@coingecko/coingecko-mcp` ## About Connects an assistant to the CoinGecko API for cryptocurrency prices, market data, trending coins and on-chain DEX data. It uses a code-mode design with two tools: one searches the SDK documentation, the other runs TypeScript against a pre-authenticated SDK client and returns the result. The hosted endpoint at mcp.api.coingecko.com needs no sign-in or API key, but the keyless tier has shared rate limits and can return HTTP 429. A Pro endpoint (mcp.pro-api.coingecko.com) accepts OAuth or an API key for higher limits and the full tool set. A local package, @coingecko/coingecko-mcp, runs through npx with a Pro or Demo key and needs Deno. ## What it can do - Search CoinGecko SDK documentation for methods and parameters - Run TypeScript against a pre-authenticated CoinGecko SDK client - Fetch current crypto prices in chosen currencies - Look up market data and trending coins - Query on-chain DEX data - Combine several API calls in one code run ## Tools (2) - `execute`: Run TypeScript with an async run(client) function against the CoinGecko SDK and return its output. (read-only) - `search_docs`: Search the SDK documentation for methods, parameters and usage examples. (read-only) ## Example prompts - "What is the current price of bitcoin and ethereum in USD?" - "Show me the trending coins on CoinGecko right now." - "Find the top 10 coins by market cap and their 24h change." - "Look up the SDK method for historical price data of solana." ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http coingecko https://mcp.api.coingecko.com/mcp ``` 2. Start Claude Code and type `/mcp`. **coingecko** should show as connected. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Settings → Connectors** and click **Add custom connector**. 2. Name it **CoinGecko** and paste this URL: ```url https://mcp.api.coingecko.com/mcp ``` 3. Click **Add**. Its tools appear in the chat’s tools menu. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://mcp.api.coingecko.com/mcp` and click **Add**. 3. Turn it on in a chat from the tools menu. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://mcp.api.coingecko.com/mcp` as the server URL and choose **No authentication**. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "coingecko": { "url": "https://mcp.api.coingecko.com/mcp" } } } ``` ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"coingecko","type":"http","url":"https://mcp.api.coingecko.com/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "coingecko": { "type": "http", "url": "https://mcp.api.coingecko.com/mcp" } } } ``` ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "coingecko": { "serverUrl": "https://mcp.api.coingecko.com/mcp" } } } ``` 2. Refresh the MCP server list in Cascade. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add coingecko --url https://mcp.api.coingecko.com/mcp ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.coingecko] url = "https://mcp.api.coingecko.com/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http coingecko https://mcp.api.coingecko.com/mcp ``` This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "coingecko": { "type": "http", "url": "https://mcp.api.coingecko.com/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.api.coingecko.com/mcp`. ## Details - Server version: 8.1.0 - MCP protocol version: 2025-11-25 - Last checked: 2026-10-03 (reachable) - Listed: 2026-10-03 - Updated: 2026-10-04 --- Source: https://mcp.tc/i/coingecko (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report