# Give Claude live crypto market data in five minutes with MCP

*Funding rates, open interest, ETF flows and backtests inside your AI client, plus a way to run strategies from a chat.*

Ask a chat model what funding looks like right now and you will get a polite guess. It has no live data. The Model Context Protocol fixes that by letting an AI client call outside tools, and Central Command runs a remote MCP server with 27 crypto tools you can connect in a few minutes.

## See what's there without an account

The server is at:

```
https://rtcelwjnrbmfmrywacky.supabase.co/functions/v1/mcp
```

Listing the tools and their prices is free and needs no key. You can try it from a terminal:

```bash
curl -s -X POST https://rtcelwjnrbmfmrywacky.supabase.co/functions/v1/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"cc.list_catalog","arguments":{}}}'
```

That returns 26 endpoints with a price on each, from $0.0005 to $0.05 a call. They include `fear-greed`, `funding-rates`, `open-interest`, `etf-flows`, `economic-calendar`, `cme-gap`, `asset-scanner`, `market-news`, `strategy-backtest` and `agent-strategy`.

## Two ways to pay

- **A linked key.** Mint an API key on the [Connect Claude page](/go/blog-mcp?to=/connect-claude). Calls are free for linked accounts.
- **Pay per call with x402.** No account needed. Call a paid tool without a key and the server answers with a 402 and payment details, settled in USDC on Base. This suits an autonomous agent with its own wallet.

## Connect your client

**Claude Code:**

```bash
claude mcp add --transport http central-command \
  https://rtcelwjnrbmfmrywacky.supabase.co/functions/v1/mcp \
  --header "X-Api-Key: YOUR_KEY"
```

**Cursor and other clients that take JSON:**

```json
{
  "mcpServers": {
    "central-command": {
      "url": "https://rtcelwjnrbmfmrywacky.supabase.co/functions/v1/mcp",
      "headers": { "X-Api-Key": "YOUR_KEY" }
    }
  }
}
```

**Clients that can't send custom headers,** such as a web connector form, can pass the key in the URL by adding `?apiKey=YOUR_KEY`. Treat that URL like a password.

## Things to ask

Once it's connected, try these:

- "What's the current funding rate environment? Show me anything extreme."
- "Run the asset scanner and find coins with unusual open interest changes."
- "Backtest a mean reversion strategy on ETH that fades 2-sigma Bollinger bands, 4H timeframe."
- "Create a paper strategy: scalp BTC on 15m using VWAP and volume spikes, 2x leverage."
- "Show my portfolio: open positions, unrealized PnL, and any strategies running."

The last two need a linked account with a BloFin connection.

## What it can and can't do with your account

Letting an AI near a trading account should make you nervous, so here are the limits:

- Strategies deploy stopped. Nothing starts on its own.
- Live orders need your explicit request plus a `confirm_live` flag on the call.
- There is no withdrawal access.

Start with read-only market questions and see whether the answers are useful before you connect anything that can trade.

## Going further

The [MCP page](/go/blog-mcp?to=/mcp) has the current details, and the [API catalog](/go/blog-mcp?to=/api) lists every endpoint if you would rather call them directly from your own code.

---

*Disclosure: I build Central Command, which earns a commission from BloFin on members' trading. This article was drafted with AI assistance. It is not financial advice. Leveraged trading can lose all of your money.*