Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt

Use this file to discover all available pages before exploring further.

Claude-specific MCP setup needs a tighter path than the generic MCP overview: where to connect, what tools appear, and how to keep API keys out of chat. The 0xArchive MCP Server is the @0xarchive/mcp-server package. It runs locally over stdio, uses OXARCHIVE_API_KEY, and exposes typed 0xArchive market-data tools to MCP-capable hosts. Claude Code is a host that can consume MCP servers when configured.

Claude Code Recipe

1

Store the API key

Keep the key in the shell, host secret store, or local environment used by Claude Code.
export OXARCHIVE_API_KEY="0xa_your_api_key"
2

Add the MCP server

Register the local stdio package as the 0xArchive MCP server.
claude mcp add 0xarchive \
  -s user \
  -t stdio \
  -e OXARCHIVE_API_KEY="$OXARCHIVE_API_KEY" \
  -- npx -y @0xarchive/mcp-server
3

Ask for one bounded call

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

What Claude Should Know

RuleWhy
MCP is a tool surface, not the agentPrevents setup language from treating the server as the host
OpenAPI remains route mapPrevents invented endpoint names
Venue family comes firstPrevents core, Spot, HIP-3, HIP-4, and Lighter mixups
Data-quality checks gate downstream jobsPrevents stale data from entering backtests, alerts, exports, or models
Request IDs should be preservedMakes failures supportable and auditable

Claude MCP Task Packet

After the server is configured, give Claude a narrow tool-calling packet.
FieldExample
Venue familyHyperliquid core, Spot, HIP-3, HIP-4, or Lighter
Symbol and windowBTC for the last hour, km:US500 for one bounded HIP-3 request, or HYPE-USDC Spot
Tool goalSummary, candles, funding, freshness, coverage, incidents, or route validation
Quality ruleInclude request ID, freshness state, coverage, or incident context when available
Stop ruleAsk before account/key/payment tools, exports, broad loops, or unsupported venues
If Claude cannot call a named 0xArchive MCP tool, fix the MCP configuration 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 is using local SKILL.md workflows instead of MCP tools. Use OpenAPI and SDKs if the goal is generated application code. Use REST API when you need raw HTTP behavior.

Security Notes

Do not paste real API keys into prompts or checked-in MCP config. Avoid remote MCP URLs unless 0xArchive has published a hosted endpoint for that environment. The documented default is local stdio execution.

Next Step

Use MCP Server for the full MCP page and Coding Agents for Claude Code recovery rules.
Last modified on May 20, 2026