Give Gemini CLI live crypto market data — prices, funding, open interest, liquidations, market regimes, Fear & Greed, dealer gamma and whale activity — as native MCP tools.
Two parts: the Agent Skill (knowledge) and the MCP server (live tools). Gemini CLI configures MCP servers in ~/.gemini/settings.json under mcpServers, and supports remote HTTP (httpUrl + headers) as well as stdio (command/args).
Install the skill with the skills CLI so Gemini knows how to use our data and workflows. See the Agent Skill page for what's inside.
npx skills add Crypto-Data-API/cryptodataapi-skills -g -y
Because our auth is a custom X-API-Key header, the cleanest path is to edit ~/.gemini/settings.json and use the remote httpUrl form with a headers block. Replace cdk_live_YOUR_KEY with your key — free one at cryptodataapi.com/login.
Prefer a subprocess? Use the stdio block instead. You can also scaffold a server with gemini mcp add --transport http cryptodataapi https://cryptodataapi.com/mcp, then add the header line in settings.json (CLI header flags vary by version).
{
"mcpServers": {
"cryptodataapi": {
"httpUrl": "https://cryptodataapi.com/mcp",
"headers": { "X-API-Key": "cdk_live_YOUR_KEY" }
}
}
}
{
"mcpServers": {
"cryptodataapi": {
"command": "npx",
"args": ["-y", "cryptodataapi-mcp"],
"env": { "CRYPTODATA_API_KEY": "cdk_live_YOUR_KEY" }
}
}
}
Start Gemini CLI and run /mcp to confirm the server and its tools loaded. Then ask for a market read — see the example prompts below.
“What's the current market regime and which strategy baskets fit it?”
“Compare BTC funding rates across exchanges and flag crowded positioning.”
“Which coins have the highest liquidation risk right now?”
“Summarize the daily snapshot as a short morning market brief.”
“Is dealer gamma amplifying or dampening BTC moves today?”
No. The skill is free and the Free API tier (no card) covers the whole market-wide picture. Per-coin quant, gamma and whale signals need Pro.
Use httpUrl (remote HTTP) with a headers block — no Node, always current, and it passes our X-API-Key cleanly. Use command (stdio, the cryptodataapi-mcp bridge) if you'd rather run a local subprocess; it needs Node.js and reads CRYPTODATA_API_KEY.
Run /mcp inside Gemini CLI to see connection status. A failed HTTP server usually means a typo in httpUrl or a missing/invalid X-API-Key; a failed stdio server usually means Node/npx isn't on PATH. Fix and restart the CLI.
Missing an agent, a config that changed, or a step that didn't work? Tell us and we'll fix it.