Coingecko TypeScript MCP Server

It is generated with Stainless.

Installation

Direct invocation

You can run the MCP Server directly via npx:

export COINGECKO_PRO_API_KEY="My Pro API Key"
export COINGECKO_DEMO_API_KEY="My Demo API Key"
export COINGECKO_ENVIRONMENT="pro"
npx -y @coingecko/coingecko-mcp@latest

Via MCP Client

There is a partial list of existing clients at modelcontextprotocol.io. If you already have a client, consult their documentation to install the MCP server.

For clients with a configuration JSON, it might look something like this:

{
  "mcpServers": {
    "coingecko_api": {
      "command": "npx",
      "args": ["-y", "@coingecko/coingecko-mcp", "--client=claude", "--tools=dynamic"],
      "env": {
        "COINGECKO_PRO_API_KEY": "My Pro API Key",
        "COINGECKO_DEMO_API_KEY": "My Demo API Key",
        "COINGECKO_ENVIRONMENT": "pro"
      }
    }
  }
}

Exposing endpoints to your MCP Client

There are two ways to expose endpoints as tools in the MCP server:

Exposing one tool per endpoint, and filtering as necessary
Exposing a set of tools to dynamically discover and invoke endpoints from the API

Filtering endpoints and tools

You can run the package on the command line to discover and filter the set of tools that are exposed by the MCP Server. This can be helpful for large APIs where including all endpoints at once is too much for your AI's context window.

You can filter by multiple aspects:

--tool includes a specific tool by name
--resource includes all tools under a specific resource, and can have wildcards, e.g. my.resource*
--operation includes just read (get/list) or just write operations

Dynamic tools

If you specify --tools=dynamic to the MCP server, instead of exposing one tool per endpoint in the API, it will expose the following tools:

list_api_endpoints - Discovers available endpoints, with optional filtering by search query
get_api_endpoint_schema - Gets detailed schema information for a specific endpoint
invoke_api_endpoint - Executes any endpoint with the appropriate parameters

This allows you to have the full set of API endpoints available to your MCP Client, while not requiring that all of their schemas be loaded into context at once. Instead, the LLM will automatically use these tools together to search for, look up, and invoke endpoints dynamically. However, due to the indirect nature of the schemas, it can struggle to provide the correct properties a bit more than when tools are imported explicitly. Therefore, you can opt-in to explicit tools, the dynamic tools, or both.

See more information with --help.

All of these command-line options can be repeated, combined together, and have corresponding exclusion versions (e.g. --no-tool).

Use --list to see the list of available tools, or see below.

Specifying the MCP Client

Different clients have varying abilities to handle arbitrary tools and schemas.

You can specify the client you are using with the --client argument, and the MCP server will automatically serve tools and schemas that are more compatible with that client.

--client=<type>: Set all capabilities based on a known MCP client
- Valid values: openai-agents, claude, claude-code, cursor
- Example: --client=cursor

Additionally, if you have a client not on the above list, or the client has gotten better over time, you can manually enable or disable certain capabilities:

--capability=<name>: Specify individual client capabilities
- Available capabilities:
  - top-level-unions: Enable support for top-level unions in tool schemas
  - valid-json: Enable JSON string parsing for arguments
  - refs: Enable support for $ref pointers in schemas
  - unions: Enable support for union types (anyOf) in schemas
  - formats: Enable support for format validations in schemas (e.g. date-time, email)
  - tool-name-length=N: Set maximum tool name length to N characters
- Example: --capability=top-level-unions --capability=tool-name-length=40
- Example: --capability=top-level-unions,tool-name-length=40

Examples

Filter for read operations on cards:

--resource=cards --operation=read

Exclude specific tools while including others:

--resource=cards --no-tool=create_cards

Configure for Cursor client with custom max tool name length:

--client=cursor --capability=tool-name-length=40

Complex filtering with multiple criteria:

--resource=cards,accounts --operation=read --tag=kyc --no-tool=create_cards

Running remotely

Launching the client with --transport=http launches the server as a remote server using Streamable HTTP transport. The --port setting can choose the port it will run on, and the --socket setting allows it to run on a Unix socket.

Authorization can be provided via the following headers:

Header	Equivalent client option	Security scheme
`x-cg-pro-api-key`	`proAPIKey`	proKeyAuth
`x-cg-demo-api-key`	`demoAPIKey`	demoKeyAuth

A configuration JSON for this server might look like this, assuming the server is hosted at http://localhost:3000:

{
  "mcpServers": {
    "coingecko_coingecko_typescript_api": {
      "url": "http://localhost:3000",
      "headers": {
        "x-cg-pro-api-key": "My Pro API Key"
      }
    }
  }
}

The command-line arguments for filtering tools and specifying clients can also be used as query parameters in the URL. For example, to exclude specific tools while including others, use the URL:

http://localhost:3000?resource=cards&resource=accounts&no_tool=create_cards

Or, to configure for the Cursor client, with a custom max tool name length, use the URL:

http://localhost:3000?client=cursor&capability=tool-name-length%3D40

Importing the tools and server individually

// Import the server, generated endpoints, or the init function
import { server, endpoints, init } from "@coingecko/coingecko-mcp/server";

// import a specific tool
import getAssetPlatforms from "@coingecko/coingecko-mcp/tools/asset-platforms/get-asset-platforms";

// initialize the server and all endpoints
init({ server, endpoints });

// manually start server
const transport = new StdioServerTransport();
await server.connect(transport);

// or initialize your own server with specific tools
const myServer = new McpServer(...);

// define your own endpoint
const myCustomEndpoint = {
  tool: {
    name: 'my_custom_tool',
    description: 'My custom tool',
    inputSchema: zodToJsonSchema(z.object({ a_property: z.string() })),
  },
  handler: async (client: client, args: any) => {
    return { myResponse: 'Hello world!' };
  })
};

// initialize the server with your custom endpoints
init({ server: myServer, endpoints: [getAssetPlatforms, myCustomEndpoint] });

Available Tools

The following tools are available in this MCP server.

Resource `asset_platforms`:

get_asset_platforms (read): This endpoint allows you to query all the asset platforms on CoinGecko

Resource `coins`:

get_id_coins (read): This endpoint allows you to query all the metadata (image, websites, socials, description, contract address, etc.) and market data (price, ATH, exchange tickers, etc.) of a coin from the CoinGecko coin page based on a particular coin ID

Resource `coins.categories`:

get_list_coins_categories (read): This endpoint allows you to query all the coins categories on CoinGecko

Resource `coins.list`:

get_new_coins_list (read): This endpoint allows you to query the latest 200 coins that recently listed on CoinGecko

Resource `coins.markets`:

get_coins_markets (read): This endpoint allows you to query all the supported coins with price, market cap, volume and market related data

Resource `coins.top_gainers_losers`:

get_coins_top_gainers_losers (read): This endpoint allows you to query the top 30 coins with largest price gain and loss by a specific time duration

Resource `coins.contract`:

get_coins_contract (read): This endpoint allows you to query all the metadata (image, websites, socials, description, contract address, etc.) and market data (price, ATH, exchange tickers, etc.) of a coin from the CoinGecko coin page based on an asset platform and a particular token contract address

Resource `coins.contract.market_chart`:

get_range_contract_coins_market_chart (read): This endpoint allows you to get the historical chart data within certain time range in UNIX along with price, market cap and 24hr volume based on asset platform and particular token contract address

Resource `coins.history`:

get_coins_history (read): This endpoint allows you to query the historical data (price, market cap, 24hrs volume, ...) at a given date for a coin based on a particular coin ID

Resource `coins.market_chart`:

get_range_coins_market_chart (read): This endpoint allows you to get the historical chart data of a coin within certain time range in UNIX along with price, market cap and 24hr volume based on particular coin ID

Resource `coins.ohlc`:

get_range_coins_ohlc (read): This endpoint allows you to get the OHLC chart (Open, High, Low, Close) of a coin within a range of timestamp based on particular coin ID

Resource `exchanges`:

get_id_exchanges (read): This endpoint allows you to query exchange's data (name, year established, country, ...), exchange volume in BTC and top 100 tickers based on exchange's ID
get_list_exchanges (read): This endpoint allows you to query all the exchanges with ID and name

Resource `exchanges.tickers`:

get_exchanges_tickers (read): This endpoint allows you to query exchange's tickers based on exchange's ID

Resource `exchanges.volume_chart`:

get_range_exchanges_volume_chart (read): This endpoint allows you to query the historical volume chart data in BTC by specifying date range in UNIX based on exchange's ID

Resource `global`:

get_global (read): This endpoint allows you query cryptocurrency global data including active cryptocurrencies, markets, total crypto market cap and etc

Resource `nfts`:

get_id_nfts (read): This endpoint allows you to query all the NFT data (name, floor price, 24hr volume ...) based on the NFT collection ID
get_list_nfts (read): This endpoint allows you to query all supported NFTs with ID, contract address, name, asset platform ID and symbol on CoinGecko
get_markets_nfts (read): This endpoint allows you to query all the supported NFT collections with floor price, market cap, volume and market related data on CoinGecko

Resource `nfts.market_chart`:

get_nfts_market_chart (read): This endpoint allows you query historical market data of a NFT collection, including floor price, market cap, and 24hr volume, by number of days away from now

Resource `onchain.categories`:

get_onchain_categories (read): This endpoint allows you to query all the supported categories on GeckoTerminal
get_pools_onchain_categories (read): This endpoint allows you to query all the pools based on the provided category ID

Resource `onchain.networks`:

get_onchain_networks (read): This endpoint allows you to query all the supported networks on GeckoTerminal

Resource `onchain.networks.new_pools`:

get_networks_onchain_new_pools (read): This endpoint allows you to query all the latest pools across all networks on GeckoTerminal
get_network_networks_onchain_new_pools (read): This endpoint allows you to query all the latest pools based on provided network

Resource `onchain.networks.dexes`:

get_networks_onchain_dexes (read): This endpoint allows you to query all the supported decentralized exchanges (DEXs) based on the provided network on GeckoTerminal

Resource `onchain.networks.pools.multi`:

get_addresses_pools_networks_onchain_multi (read): This endpoint allows you to query multiple pools based on the provided network and pool address

Resource `onchain.networks.pools.info`:

get_pools_networks_onchain_info (read): This endpoint allows you to query pool metadata (base and quote token details, image, socials, websites, description, contract address, etc.) based on a provided pool contract address on a network

Resource `onchain.networks.pools.ohlcv`:

get_timeframe_pools_networks_onchain_ohlcv (read): This endpoint allows you to get the OHLCV chart (Open, High, Low, Close, Volume) of a pool based on the provided pool address on a network

Resource `onchain.networks.pools.trades`:

get_pools_networks_onchain_trades (read): This endpoint allows you to query the last 300 trades in the past 24 hours based on the provided pool address

Resource `onchain.networks.tokens.multi`:

get_addresses_tokens_networks_onchain_multi (read): This endpoint allows you to query multiple tokens data based on the provided token contract addresses on a network

Resource `onchain.networks.tokens.info`:

get_tokens_networks_onchain_info (read): This endpoint allows you to query token metadata (name, symbol, CoinGecko ID, image, socials, websites, description, etc.) based on a provided token contract address on a network

Resource `onchain.networks.tokens.top_holders`:

get_tokens_networks_onchain_top_holders (read): This endpoint allows you to query top token holders based on the provided token contract address on a network

Resource `onchain.networks.tokens.holders_chart`:

get_tokens_networks_onchain_holders_chart (read): This endpoint allows you to get the historical token holders chart based on the provided token contract address on a network

Resource `onchain.networks.tokens.ohlcv`:

get_timeframe_tokens_networks_onchain_ohlcv (read): This endpoint allows you to get the OHLCV chart (Open, High, Low, Close, Volume) of a token based on the provided token address on a network

Resource `onchain.networks.tokens.pools`:

get_tokens_networks_onchain_pools (read): This endpoint allows you to query top pools based on the provided token contract address on a network

Resource `onchain.networks.tokens.trades`:

get_tokens_networks_onchain_trades (read): This endpoint allows you to query the last 300 trades in the past 24 hours, across all pools, based on the provided token contract address on a network

Resource `onchain.pools.megafilter`:

get_pools_onchain_megafilter (read): This endpoint allows you to query pools based on various filters across all networks on GeckoTerminal

Resource `onchain.pools.trending_search`:

get_pools_onchain_trending_search (read): This endpoint allows you to query all the trending search pools across all networks on GeckoTerminal

Resource `onchain.search.pools`:

get_search_onchain_pools (read): This endpoint allows you to search for pools on a network

Resource `onchain.simple.networks.token_price`:

get_addresses_networks_simple_onchain_token_price (read): This endpoint allows you to get token price based on the provided token contract address on a network

Resource `search`:

get_search (read): This endpoint allows you to search for coins, categories and markets listed on CoinGecko

Resource `search.trending`:

get_search_trending (read): This endpoint allows you query trending search coins, NFTs and categories on CoinGecko in the last 24 hours

Resource `simple.price`:

get_simple_price (read): This endpoint allows you to query the prices of one or more coins by using their unique Coin API IDs

Resource `simple.supported_vs_currencies`:

get_simple_supported_vs_currencies (read): This endpoint allows you to query all the supported currencies on CoinGecko

Resource `simple.token_price`:

get_id_simple_token_price (read): This endpoint allows you to query one or more token prices using their token contract addresses