Coingecko-mcp-server MCP Server

Coingecko-mcp-server is an MCP integration. Crypto market data via CoinGecko — prices, markets, history, trending, and deep coin metadata.

Packages and local setup

The published npm package is @cyanheads/coingecko-mcp-server, version 0.1.4. Its declared MCP transport is stdio.

The package declares COINGECKO_API_KEY: Optional CoinGecko Demo API key. Present → sent as the x-cg-demo-api-key header for the dedicated Demo tier (10k/mo, 100 rpm). Absent → keyless public tier.; MCP_LOG_LEVEL: Sets the minimum log level for output (e.g., 'debug', 'info', 'warn')..

The published npm package is @cyanheads/coingecko-mcp-server, version 0.1.4. Its declared MCP transport is streamable-http.

The package declares MCP_TRANSPORT_TYPE: Selects the HTTP transport.; COINGECKO_API_KEY: Optional CoinGecko Demo API key. Present → sent as the x-cg-demo-api-key header for the dedicated Demo tier (10k/mo, 100 rpm). Absent → keyless public tier.; MCP_HTTP_HOST: The hostname for the HTTP server.; MCP_HTTP_PORT: The port to run the HTTP server on.; MCP_HTTP_ENDPOINT_PATH: The endpoint path for the MCP server.; MCP_AUTH_MODE: Authentication mode to use: 'none', 'jwt', or 'oauth'.; MCP_LOG_LEVEL: Sets the minimum log level for output (e.g., 'debug', 'info', 'warn')..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.4 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.