Claude MCP setup

This is the Claude-specific path for the 0xArchive MCP server: where to connect, what tools appear, and how to keep your API key out of chat. For the full reference, see MCP server. The server is hosted at https://mcp.0xarchive.io/mcp. Claude Code connects over HTTP with your API key as a bearer token. Nothing runs locally.

Claude Code recipe

Store the API key

Keep the key in the shell or secret store Claude Code reads.

export OXARCHIVE_API_KEY="0xa_your_api_key"

Add the MCP server

claude mcp add --transport http 0xarchive \
  https://mcp.0xarchive.io/mcp \
  --header "Authorization: Bearer $OXARCHIVE_API_KEY"

Ask for one bounded call

Start with one venue family, one symbol, one data family, and one small window. Ask Claude to name the route before it calls a tool.

What Claude should know

Rule	Why
MCP is a tool surface, not the agent	Keeps setup language from treating the server as the host
OpenAPI stays the route map	Prevents invented endpoint names
Venue family comes first	Prevents core, Spot, HIP-3, HIP-4, and Lighter mixups
Data-quality checks gate downstream jobs	Keeps stale data out of backtests, alerts, exports, and models
Request IDs should be preserved	Makes failures supportable and auditable

Task checklist

After the server is connected, give Claude a narrow tool-calling checklist.

Field	Example
Venue family	Hyperliquid core, Spot, HIP-3, HIP-4, or Lighter
Symbol and window	`BTC` for the last hour, `km:US500` for one bounded HIP-3 request, or `HYPE-USDC` Spot
Tool goal	Summary, candles, funding, freshness, coverage, incidents, or route validation
Quality rule	Include request ID, freshness state, coverage, or incident context when available
Stop rule	Ask before account, key, or billing tools, exports, broad loops, or venues outside Hyperliquid and Lighter

If Claude cannot call a named 0xArchive tool, fix the connection before asking it to analyze data. If it can call tools but cannot name the venue family, keep the task in clarification mode.

Use another surface when

Use CLI if the job is a shell command or CI task. Use Skill if the Claude environment uses local SKILL.md workflows instead of MCP tools. Use OpenAPI and SDKs for generated application code. Use REST API when you need raw HTTP behavior.

Security

Do not paste real API keys into prompts or checked-in MCP config. Pass the bearer token through Claude Code’s environment or secret store. Account, key, and billing tools change account state, so keep them behind explicit approval.

Plans and limits

Free gets the full catalog; paid plans raise your limits

Every tier, including Free, gets the full catalog: L2, L3, and L4 order books, order flow, TP/SL, trades, candles, funding, open interest, and liquidations, plus WebSocket access. Tiers differ only on credits, rate limits, concurrency, WebSocket scale, and replay speed.

Upgrade to Pro →

Next step

Use MCP server for the full MCP reference and Coding agents for Claude Code recovery rules.

API reference

SDKs & tooling

AI & agents

Claude Code recipe

What Claude should know

Task checklist

Use another surface when

Security

Next step

​Claude Code recipe

​What Claude should know

​Task checklist

​Use another surface when

​Security

​Next step

Claude Code recipe

What Claude should know

Task checklist

Use another surface when

Security

Next step