Home / MCP / CoinMarketCap MCP Server

CoinMarketCap MCP Server

Provides CoinMarketCap data via MCP across markets, OHLCV, and global metrics with tiered access.

javascript

44stars

View on GitHub

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
    "mcpServers": {
        "coinmarketcap": {
            "command": "npx",
            "args": [
                "-y",
                "@shinzolabs/coinmarketcap-mcp"
            ],
            "env": {
                "COINMARKETCAP_API_KEY": "your-key-here",
                "SUBSCRIPTION_LEVEL": "Basic",
                "PORT": "3000",
                "TELEMETRY_ENABLED": "true"
            }
        }
    }
}

You run a dedicated MCP server that exposes CoinMarketCap data through a standardized interface. It lets you fetch market data, OHLCV data, exchange metadata, and global metrics with tiered access, while keeping parameters type-safe and easy to compose in your own applications.

How to use

Connect your MCP client to the CoinMarketCap MCP Server to access a wide range of data endpoints. You can run the server locally using Node-based execution or install it remotely via Smithery. Once your server is running, configure your MCP client to reference the server and supply your CoinMarketCap API key and a subscription level. The client can then request cryptocurrency data, exchange information, OHLCV histories, and other metrics according to your subscribed level.

How to install

Prerequisites: you need Node.js and npm or pnpm installed on your machine. You will also need a CoinMarketCap API key and a chosen subscription level.

# 1) NPX Local Install
# Add a local MCP server reference to your MCP client config
# Use npx to run the MCP server without a local install

# Example MCP client config:
{
  "mcpServers": {
    "coinmarketcap": {
      "command": "npx",
      "args": [
        "@shinzolabs/coinmarketcap-mcp"
      ],
      "env": {
        "COINMARKETCAP_API_KEY": "your-key-here",
        "SUBSCRIPTION_LEVEL": "Basic" // See options below
      }
    }
  }
}
```

```bash
# 2) Build from Source
# Clone the repository

git clone https://github.com/shinzo-labs/coinmarketcap-mcp.git

# Install dependencies (use your preferred package manager)
pnpm i

# Start the server from source when running locally
# Add the following to your MCP client config if you build from source:
{
  "mcpServers": {
    "coinmarketcap": {
      "command": "node",
      "args": [
        "/path/to/coinmarketcap-mcp/index.js"
      ],
      "env": {
        "COINMARKETCAP_API_KEY": "your-key-here",
        "SUBSCRIPTION_LEVEL": "Basic" // See options below
      }
    }
  }
}
```

```bash
# 3) Smithery Remote Server (Recommended)
# Use Smithery CLI to install and connect to the remote MCP server

npx -y @smithery/cli install @shinzo-labs/coinmarketcap-mcp

# Enter your API key and subscription level when prompted
```]} ,{

Additional configuration and options

Configure environment and transport settings to suit your deployment. The server supports environment variables for API keys and subscription levels, plus optional transport port and telemetry toggles. You can adjust these in your MCP client configuration or environment as needed.

Notes and considerations

- The server provides extensive data access across Cryptocurrency, Exchange, DEX, Global Metrics, Index, Tools, and other categories, with features gated by subscription level. - Keep your API key secure and rotate it if you suspect exposure. - Telemetry is enabled by default to help improve the service; you can opt out if desired.

Security and privacy

Only anonymous telemetry is collected by default to improve the product. No personally identifiable information is collected through telemetry. Review access controls and restrict API key usage to trusted clients.

Troubleshooting

If you encounter connection issues, verify that your API key is valid and your subscription level includes the features you request. Ensure that the MCP server process has access to the network and that the port (default 3000) is open if you expose the HTTP transport. Check environment variables for accuracy and consistency across client and server configurations.

Available tools

cryptoCurrencyMap

Get mapping of all cryptocurrencies

getCryptoMetadata

Get metadata for one or more cryptocurrencies

allCryptocurrencyListings

Get latest market quote for 1-5000 cryptocurrencies

cryptoQuotesLatest

Get latest market quote for 1 or more cryptocurrencies

cryptoCategories

Get list of all cryptocurrency categories

cryptoCategory

Get metadata about a cryptocurrency category

exchangeMap

Get mapping of all exchanges

exchangeInfo

Get metadata for one or more exchanges

exchangeAssets

Get list of all assets available on an exchange

dexInfo

Get metadata for one or more decentralised exchanges

dexListingsLatest

Get latest market data for all DEXes

dexNetworksList

Get list of all networks with unique IDs

dexSpotPairsLatest

Get latest market data for all active DEX spot pairs

dexPairsQuotesLatest

Get latest market quotes for spot pairs

dexPairsOhlcvLatest

Get latest OHLCV data for spot pairs

dexPairsOhlcvHistorical

Get historical OHLCV data for spot pairs

dexPairsTradeLatest

Get latest trades for spot pairs

globalMetricsLatest

Get latest global cryptocurrency metrics

cmc100IndexLatest

Get latest CoinMarketCap 100 Index value and constituents

cmc100IndexHistorical

Get historical CoinMarketCap 100 Index values

priceConversion

Convert an amount of one cryptocurrency or fiat currency into another

getPostmanCollection

Get Postman collection for the API

fiatMap

Get mapping of all fiat currencies

keyInfo

Get API key usage and status

fearAndGreedLatest

Get latest Fear & Greed Index

fearAndGreedHistorical

Get historical Fear & Greed Index values