CoinGecko MCP Pro

CoinGecko Pro MCP Server
Real-Time Crypto Data for AI

Q: I'm getting connection timeout or network errors. What should I do?

First, check your internet connection and verify that the MCP endpoint URL is accessible from your browser. Some corporate firewalls or restrictive networks may block the endpoint. If you're on a work network, you may need to ask your IT team to whitelist the domain. If your client doesn't handle HTTP streaming well, try the SSE fallback endpoint.

Q: How do I fix npx or mcp-remote package errors?

Ensure Node.js is properly installed on your system. Check by running node --version and npm --version in your terminal. Test if mcp-remote is accessible with npx mcp-remote --version. If you get permission errors, try clearing the npm cache with npm cache clean --force, or clear the MCP auth cache with rm -rf ~/.mcp-auth.

Q: Where can I find logs to debug connection issues?

For Claude Desktop: on macOS check ~/Library/Logs/Claude/mcp*.log, on Windows check %LOCALAPPDATA%\Claude\Logs\, on Linux check ~/.local/share/Claude/logs/. For other MCP clients, consult your client's documentation for log file locations.

Q: The server is responding but queries aren't working. What's wrong?

Check if the tools are loaded by asking your MCP client to list available tools. Ensure you're using natural language queries rather than calling functions directly. Try simple queries first like "What's the current price of Bitcoin?" before attempting complex multi-step operations.

Bring your API key. Get dedicated throughput.

Connect any MCP-compatible AI to live prices, historical charts, DeFi pools, NFT collections, and more — with your own CoinGecko API key for higher rate limits and production-grade availability.

76+ tools 1M+ assets Your API key HTTP & SSE

Endpoints

HTTP

Primary · streamable-http · recommended for all modern clients

SSE

Fallback · use if your client doesn't handle streaming well

🔑 API Key Required: This is the Pro MCP server. You must provide your own CoinGecko API key to authenticate requests and access your dedicated rate limits.

Protocol Support: If you've got a client that natively supports the current MCP specification, you can connect directly to /mcp. You may use the SSE implementation at /sse if your client does not handle streaming well.

Connect

In Claude.ai, open Settings → Integrations → Add integration.
Paste the endpoint URL and name the connection CoinGecko Pro.

https://mcp.pro-api.coingecko.com/mcp
Save. CoinGecko Pro will appear as a custom integration with your dedicated rate limits.

Run this command once in your terminal.

claude mcp add --transport http coingecko https://mcp.pro-api.coingecko.com/mcp
CoinGecko Pro tools are available immediately in any Claude Code session — no restart needed.
Verify with claude mcp list.

Edit your Claude Desktop configuration file.
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Add the CoinGecko Pro MCP server using mcp-remote.

{ "mcpServers": { "coingecko": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://mcp.pro-api.coingecko.com/mcp"] } } }
Quit and reopen Claude Desktop. Look for the hammer icon to confirm the connection.
Requires Node.js for npx.

Open Cursor Settings with ⌘ Shift J (macOS) or Ctrl Shift J (Windows/Linux).
Select Skills and Integrations and paste the configuration.

{ "mcpServers": { "coingecko": { "url": "https://mcp.pro-api.coingecko.com/mcp" } } }
Save and restart Cursor. CoinGecko Pro tools will be available in agent sessions.

Open the Command Palette with ⌘ P and search for MCP: Add Server.
Select HTTP (HTTP or Server-Sent Events) and enter the endpoint URL.

https://mcp.pro-api.coingecko.com/mcp
Name the server CoinGecko Pro and confirm. Activate via MCP: List Servers → Start Server.

Edit your Windsurf MCP configuration file at ~/.codeium/windsurf/mcp_config.json.
Add the CoinGecko Pro MCP server.

{ "mcpServers": { "coingecko": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://mcp.pro-api.coingecko.com/mcp"] } } }
Restart Windsurf — CoinGecko Pro tools will be available in your session.

Open or create ~/.codex/config.json.
Add the CoinGecko Pro MCP server.

{ "mcpServers": { "coingecko": { "url": "https://mcp.pro-api.coingecko.com/mcp" } } }
Run codex — CoinGecko Pro tools are available automatically.

Open or create ~/.gemini/settings.json.
Add the CoinGecko Pro MCP server.

{ "mcpServers": { "coingecko": { "httpUrl": "https://mcp.pro-api.coingecko.com/mcp" } } }
Restart Gemini CLI — CoinGecko Pro tools will be available in your session.

Open or create opencode.json in your project root, or ~/.config/opencode/opencode.json for global config.
Add the CoinGecko Pro MCP server.

{ "$schema": "https://opencode.ai/config.json", "mcp": { "coingecko": { "type": "remote", "url": "https://mcp.pro-api.coingecko.com/mcp" } } }
Restart OpenCode — CoinGecko Pro tools will be available.

Open Warp and navigate to Settings → AI → MCP Servers.
Click Add, paste the endpoint URL, and name it coingecko.

https://mcp.pro-api.coingecko.com/mcp
Save. CoinGecko Pro tools are available immediately — no restart needed.

Open Zed settings via the command palette: zed: open settings.
File location: ~/.config/zed/settings.json
Add the CoinGecko Pro context server.

{ "context_servers": { "coingecko": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://mcp.pro-api.coingecko.com/mcp"] }, "settings": {} } }

Requires Node.js for npx.
Restart Zed to load the new context server.

Open or create ~/.amp/config.json.
Add the CoinGecko Pro MCP server.

{ "mcpServers": { "coingecko": { "url": "https://mcp.pro-api.coingecko.com/mcp" } } }
Restart Amp — CoinGecko Pro tools will be available in your session.

For clients with native streamable-http support (n8n, Codex, Amp), use the primary endpoint directly.

https://mcp.pro-api.coingecko.com/mcp
For clients that only support SSE, use the fallback endpoint.

https://mcp.pro-api.coingecko.com/sse
If your client requires a local bridge, use mcp-remote.

npx mcp-remote https://mcp.pro-api.coingecko.com/mcp

Requires Node.js. Prefer native transport where supported.

Getting Started

Visit the CoinGecko Pro MCP documentation for a step-by-step guide on how to connect with your API key.

If you are using Claude Pro, you may refer to the connectors guide as another method to connect with the MCP.

Don't have an API key yet? Get your CoinGecko Pro API key →

76+

Available Tools

1M+

Assets Covered

24/7

Uptime

100+

Networks

What you can ask

"What's the current price of Bitcoin?" simple_price

"Show me the top 10 cryptocurrencies by market cap" coins_markets

"What are the trending coins today?" trending_search

"What are the top DEX pools on Solana?" onchain_pools_network

"Do a technical analysis on Bitcoin historical price since the beginning of time" coin_ohlc · market_chart_range

"Show me the top NFT collection market data" nfts_markets

What's covered

Prices & Markets

Live prices, caps, volumes, and rankings across 1M+ assets.

Historical Data

OHLCV charts, price history, and long-range trend analysis.

DeFi & On-chain

Pool data, liquidity, and token analytics across 100+ networks.

NFT Analytics

Collection floor prices, volumes, and marketplace stats.

Exchanges

CEX and DEX tickers, trading pairs, and volume data.

Trending & Discovery

Trending coins, search, categories, and emerging projects.

Resources & Documentation

Helpful links and additional information.

📚

MCP Protocol

Official MCP Documentation

🦎

CoinGecko API

API Documentation & Reference

🤖

Claude Desktop

Download Claude Desktop

⚡

n8n Workflows

Workflow Automation Platform

🔧

MCP GitHub

Open Source Repository

📖

Integration Guide

Anthropic MCP Guide

Frequently Asked Questions

Quick answers to common questions about setting up and using the CoinGecko Pro MCP Server.

Setup & Configuration

Why aren't the tools appearing after I added the configuration?

Make sure you restart your MCP client completely after adding the configuration. The client needs to reload to discover the new server and its tools.

For Claude Desktop, quit the app entirely and reopen it. Simply refreshing or starting a new conversation won't pick up configuration changes.

I'm getting connection timeout or network errors. What should I do?

First, check your internet connection and verify that https://mcp.pro-api.coingecko.com/mcp is accessible from your browser.

Some corporate firewalls or restrictive networks may block this endpoint. If you're on a work network, you may need to ask your IT team to whitelist the domain.

You can also try testing the connection with: curl https://mcp.pro-api.coingecko.com/mcp

If your client doesn't handle HTTP streaming well, try the SSE fallback at https://mcp.pro-api.coingecko.com/sse.

How do I fix npx or mcp-remote package errors?

Ensure Node.js is properly installed on your system. You can check by running node --version and npm --version in your terminal.

Test if the mcp-remote package is accessible by running: npx mcp-remote --version

If you get permission errors, try clearing the npm cache: npm cache clean --force

Also try clearing the MCP auth cache: rm -rf ~/.mcp-auth

API Keys & Rate Limits

Do I need my own CoinGecko API key to use this server?

Yes. The Pro MCP server requires your own CoinGecko API key to authenticate requests and apply your dedicated rate limits.

If you don't have one yet, get your CoinGecko API key here. If you'd prefer a keyless experience, use the free public MCP server instead.

Can I use this for commercial or production applications?

Yes. The Pro MCP server is designed for production use. With your own API key, you get dedicated rate limits and the reliability needed for commercial applications.

Please review CoinGecko's terms of service for your specific subscription tier and use case.

Compatibility & Debugging

Which MCP clients are compatible with this server?

The server works with any MCP-compatible client that supports remote servers — Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, n8n, and more.

Clients that don't support HTTP natively (like Claude Desktop) can use the mcp-remote bridge package.

Where can I find logs to debug connection issues?

Claude Desktop logs:

# macOS
~/Library/Logs/Claude/mcp*.log

# Windows
%LOCALAPPDATA%\Claude\Logs\

# Linux
~/.local/share/Claude/logs/

For other MCP clients, consult your client's documentation for log file locations.

The server is responding but queries aren't working. What's wrong?

Check if the tools are being loaded properly by asking your MCP client to list available tools.

Ensure you're using natural language queries rather than trying to call functions directly.

Try simple queries first like "What's the current price of Bitcoin?" before attempting complex multi-step operations.

Don't have an API key yet?

Get your API key →

CoinGecko Pro MCP ServerReal-Time Crypto Data for AI

Endpoints

Connect

Getting Started

What you can ask

What's covered

Prices & Markets

Historical Data

DeFi & On-chain

NFT Analytics

Exchanges

Trending & Discovery

Resources & Documentation

Frequently Asked Questions

Don't have an API key yet?

CoinGecko Pro MCP Server
Real-Time Crypto Data for AI