Give Cursor live crypto market data — prices, funding, open interest, liquidations, market regimes, Fear & Greed, dealer gamma and whale activity — as native MCP tools its agent can call.
Two parts: the Agent Skill (knowledge) and the MCP server (live tools). Cursor supports both remote HTTP and stdio MCP servers, configured in .cursor/mcp.json (project) or ~/.cursor/mcp.json (global).
.cursor/mcp.json · ~/.cursor/mcp.json
Skills · ~/.claude/skills/ (skills CLI)
Agent docs →
Install the skill with the skills CLI so Cursor's agent 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
Add the cryptodataapi server to .cursor/mcp.json (create it if needed). Use the remote HTTP block (recommended — no Node) or the stdio block if you prefer a local bridge. Replace cdk_live_YOUR_KEY with your key — free one at cryptodataapi.com/login.
Cursor picks it up automatically; check Settings → MCP to confirm the server is connected and its tools are enabled. Tip: keep real keys out of a committed mcp.json — Cursor supports ${env:NAME} interpolation for secrets.
{
"mcpServers": {
"cryptodataapi": {
"url": "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" }
}
}
}
In Cursor's agent (Composer), ask for a market read — see the example prompts below. The agent will call the tools directly.
“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?”
“Pull the daily snapshot and scaffold a Python script that alerts on regime changes.”
“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.
In .cursor/mcp.json — either as an X-API-Key header (remote) or a CRYPTODATA_API_KEY env var (stdio). To avoid committing it, use ${env:CRYPTODATA_API_KEY} and set the variable in your environment.
Open Settings → MCP and confirm the server is green/enabled (toggle it if needed), then reload. A red server usually means a bad URL or, on stdio, that npx/Node isn't on PATH. If tools 401, fix the key.
Missing an agent, a config that changed, or a step that didn't work? Tell us and we'll fix it.