CoinMarketCap MCP Skill

---

name: cmc-mcp

description: |

Fetches cryptocurrency market data, prices, technical analysis, news, and trends using the CoinMarketCap MCP.

Use for ANY question involving cryptocurrencies, tokens, or blockchain markets, even if the user doesn't explicitly ask for data. This includes price checks, portfolio questions, market analysis, coin comparisons, holder metrics, technical indicators, and news.

Trigger: "bitcoin", "ETH", "crypto", "token price", "market cap", "how is [coin] doing", "/cmc-mcp"

license: MIT

compatibility: ">=1.0.0"

homepage: https://github.com/coinmarketcap/skills-for-ai-agents-by-CoinMarketCap

source: https://github.com/coinmarketcap/skills-for-ai-agents-by-CoinMarketCap

user-invocable: true

requires-credentials:

- name: X-CMC-MCP-API-KEY

description: CoinMarketCap API key for MCP access

obtain-from: https://pro.coinmarketcap.com/login

storage: MCP server configuration (mcpServers in settings)

allowed-tools:

- mcp__cmc-mcp__search_cryptos

- mcp__cmc-mcp__get_crypto_quotes_latest

- mcp__cmc-mcp__get_crypto_info

- mcp__cmc-mcp__get_crypto_metrics

- mcp__cmc-mcp__get_crypto_technical_analysis

- mcp__cmc-mcp__get_crypto_latest_news

- mcp__cmc-mcp__search_crypto_info

- mcp__cmc-mcp__get_global_metrics_latest

- mcp__cmc-mcp__get_global_crypto_derivatives_metrics

- mcp__cmc-mcp__get_crypto_marketcap_technical_analysis

- mcp__cmc-mcp__trending_crypto_narratives

- mcp__cmc-mcp__get_upcoming_macro_events

---

# CoinMarketCap MCP Skill

You have access to CoinMarketCap data through MCP tools. Use these tools to provide comprehensive, data-rich answers to crypto-related questions.

Prerequisites

Before using CMC tools, verify the MCP connection is working. If tools fail or return connection errors, ask the user to set up the MCP connection:

{
  "mcpServers": {
    "cmc-mcp": {
      "url": "https://mcp.coinmarketcap.com/mcp",
      "headers": {
        "X-CMC-MCP-API-KEY": "your-api-key"
      }
    }
  }
}

Get your API key from https://pro.coinmarketcap.com/login

Core Principle

Err on the side of fetching more data. A complete answer from multiple tools is better than a partial answer that leaves users asking for more. When in doubt, call additional tools to gather comprehensive data.

Workflow

1. Always Search First

When a user mentions a cryptocurrency by name or symbol, search for it first to get the ID:

User: "How is Solana doing?"
→ Call search_cryptos with query "solana"
→ Get ID (e.g., 5426)
→ Then call other tools using that ID

Most tools require the numeric CMC ID, not the name or symbol. The search tool returns: id, name, symbol, slug, and rank.

2. Batch Requests When Useful

When dealing with multiple coins, batch the requests:

User: "Compare BTC, ETH, and SOL"
→ Search for each to get IDs: 1, 1027, 5426
→ Call get_crypto_quotes_latest with id="1,1027,5426"

This is more efficient than separate calls and allows for direct comparison in the response.

3. Match Tools to Query Type

**For price and market data:**

**For coin background and links:**

**For technical analysis:**

**For recent news:**

**For holder and distribution data:**

**For concept explanations:**

**For overall market health:**

**For derivatives and leverage data:**

**For total market cap technical analysis:**

**For trending themes:**

**For upcoming catalysts:**

Error Handling

**If search returns no results:**

1. Report that the coin was not found

2. Ask the user to clarify or check the spelling

3. Suggest alternatives if the query might be ambiguous

**If a tool fails or times out:**

1. Retry once for transient errors

2. If still failing, note which data is unavailable and proceed with other tools

3. For price queries, `get_crypto_quotes_latest` is critical. If it fails after retry, inform the user data is temporarily unavailable.

4. For background queries, `get_crypto_info` failure means note "Project info unavailable" and provide what you can from other tools

**If rate limited (429 error):**

1. Inform the user the API is rate limited

2. Suggest waiting a moment before retrying

3. Consider if fewer tool calls could answer the question

Adapting to User Sophistication

Read context cues from the user's query: