Skip to main content
Connect Claude, ChatGPT, Codex, Cursor, or another MCP-capable client to https://mcp.0xarchive.io/mcp, and it can pull 0xArchive market data through typed tools instead of guessing endpoints. With your approval it can also set up your open 0xArchive Terminal. There is nothing to install or run locally, and you sign in with OAuth: the server needs no 0xArchive API key.

Connect

The client opens a sign-in through its built-in OAuth flow, at the authorization server https://auth.0xarchive.io. Approve mcp:market.read, the scope for market data. The client keeps the access token, so do not add an Authorization header or an 0xArchive API key yourself. When mcp:feedback.write is offered, it lets the connected agent call submit_feedback. A reconnect alone does not upgrade an existing read-only grant: the client must request the write scope and you must approve it once. An agent may then decide when to send feedback without asking before each report. The tool returns a receipt ID, not a response-time or fix promise. See Send product feedback for the fields and privacy guidance.

Client setup

Every client uses the same server URL and its own OAuth sign-in. If you already have MCP servers configured, add 0xArchive without replacing the other entries. Do not configure an API key or a static Authorization header in any client.
In Claude Code, run /mcp, select 0xarchive, and choose Authenticate. Complete the browser sign-in and approve mcp:market.read; Claude Code keeps the resulting OAuth access token in its own credential handling. Then ask for a BTC market summary. Claude Code MCP documentation
  1. Open 0xArchive in Claude’s connector directory and add the connector.
  2. Sign in to 0xArchive and approve the connection.
  3. Enable it from + → Connectors in your conversation.
For Team and Enterprise workspaces, an owner first adds the connector in Organization settings → Connectors; each member then connects their own account.To add it as a custom connector instead, open Customize → Connectors, click + → Add custom connector, name it 0xArchive, enter https://mcp.0xarchive.io/mcp, then click Connect and complete the OAuth sign-in. Claude custom connector guide
  1. Open the 0xArchive plugin by Archive Labs Inc and choose Install plugin.
  2. Connect it, sign in to 0xArchive, and approve the connection.
  3. Choose Try in chat to start a conversation with 0xArchive.
You can also find it by searching for 0xArchive in ChatGPT’s Plugins directory.To add it as a custom MCP connection instead, enable Developer mode in Settings → Security & Login, open Plugins and use the + button to add an MCP connection, name it 0xArchive, enter https://mcp.0xarchive.io/mcp, and complete OAuth authentication. Then select it from + → More in a new conversation. ChatGPT MCP connection guide
Complete the OAuth sign-in. To start authentication separately, run codex mcp login 0xarchive. The CLI and IDE extension share MCP configuration; use /mcp in the Codex terminal interface to check the connection. Codex MCP documentation
Add this entry to .cursor/mcp.json in your project. For a user-wide connection, use ~/.cursor/mcp.json.
Open Cursor’s MCP settings, connect 0xarchive, and complete the OAuth sign-in. Enable the server’s tools for Agent. Cursor MCP documentation
Run MCP: Add Server from the Command Palette, choose an HTTP server, and enter https://mcp.0xarchive.io/mcp. Or add it to .vscode/mcp.json:
Start the server and complete the browser OAuth flow. Use MCP: List Servers to check its status, then enable the tools you need in chat. VS Code MCP documentation
Antigravity CLI is the current choice for personal Google accounts. Add this to .agents/mcp_config.json in your project:
Open /mcp in Antigravity CLI to reload the configuration and check the server, then complete its OAuth prompt. Use serverUrl, not Gemini CLI’s httpUrl field.Gemini CLI remains available with Gemini Code Assist Standard or Enterprise licenses or paid Google API access. From your project directory:
Start Gemini, run /mcp auth 0xarchive, and complete the browser OAuth flow. /mcp shows the server and its available tools. Antigravity MCP documentation · Gemini CLI MCP documentation · Google client availability
Grok web: open Grok’s Connectors page, choose New Connector → Custom, enter https://mcp.0xarchive.io/mcp, and complete the OAuth sign-in. For Business and Enterprise organizations, a team admin first provisions the connector.Grok Build:
Grok starts the OAuth flow when the server is first used. In the terminal interface, /mcps opens the MCP settings and i starts authentication for the selected server. Grok connectors · Grok Build MCP documentation
Run hermes mcp test 0xarchive to check the connection. The OAuth bearer access token stays in Hermes’s credential handling. When Hermes presents tool selection, enter select, review the checklist, and enable only the tools you intend to use: all discovered tools begin selected, so deselect any tool you do not want exposed to the agent. Hermes MCP documentation
Run openclaw mcp doctor 0xarchive --probe to check the connection. Use OpenClaw’s MCP tool controls to choose which agents or sessions can use it. OpenClaw MCP guide · OAuth setup
Add this entry to opencode.json:
Run opencode mcp auth 0xarchive and complete the browser sign-in. opencode mcp list shows the authentication status. OpenCode MCP documentation
Devin Local and Devin CLI: Devin Local, the default agent for new editor tabs, uses the Devin MCP configuration. From your project directory:
Cascade: add this to ~/.codeium/windsurf/mcp_config.json:
Open Cascade’s MCP settings, enable the server, and complete its OAuth sign-in. Select the tools you need if you reach the client’s tool limit. Sign in separately in each client you use. Devin MCP configuration · Windsurf Cascade MCP settings
  1. Open Cline’s MCP Servers panel and the Remote Servers tab.
  2. Enter 0xarchive as the name and https://mcp.0xarchive.io/mcp as the URL.
  3. Choose Streamable HTTP and click Add Server.
  4. Click Authenticate when the server requests OAuth, then finish the browser sign-in.
If Authenticate is missing, update Cline before connecting. Cline MCP documentation
Use the same server URL with a client that supports Streamable HTTP and OAuth. Add https://mcp.0xarchive.io/mcp as a remote HTTP MCP server, let the client discover the authorization server, and approve the scopes it asks for. Do not substitute an API key or a manually pasted bearer token. For custom integrations, read the OAuth resource metadata and the MCP authorization specification.
If a client connects but a call fails, see Troubleshooting.

First request

Listing tools discovers the available operations without retrieving market data or spending data credits. It does not count as your first data result. To inspect allowance and reset time before a market-data call, use the authenticated account-usage request. Ask your client, in a new conversation:

Get a BTC market summary on Hyperliquid.

The client calls get_summary with BTC and answers with the BTC mark price, oracle price, funding rate, open interest, 24-hour volume, and 24-hour liquidation volume, as of the timestamp the tool returns. The connection works when a tool call returns data with its timestamp. If the client asks which venue you mean, answer it; if it calls a different tool, name get_summary in your prompt. Keep later prompts as narrow as this one: one venue family, one symbol, one data type, and one small window. Ask the client to name the tool it will call and that tool’s inputs before it calls; a tool name guessed from a REST route will fail.

What the tools do

Read-only market-data tools are organized by venue family: Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, Lighter, and data quality. They never submit orders or change account state. Lighter tools cover both Lighter deployments: get_lighter_* tools read Lighter mainnet and get_rh_lighter_* tools read Lighter on Robinhood Chain. The account positions tools (get_account_positions, get_account_positions_history, get_account_position_changes, get_market_positions, get_market_positions_summary, and get_lighter_accounts) read the Account positions routes and take a venue of hyperliquid, hip3, lighter, or rh-lighter. Your plan sets credits and the history window, as it does for REST, and each tool returns only the data its venue family has. For current funding requests, call the Hyperliquid and Lighter tools separately. Preserve the source units and timestamp from each response.

Set up your Terminal

With Terminal access approved, the client can set up your open 0xArchive Terminal for you. It can build and change views, choose each chart’s market, timeframe, studies and indicators, put In play on a view to rank a venue’s markets live, draw levels, and set price alerts. Ask for what you trade, such as “a swing-trading view for SOL on the daily, 4-hour and 1-hour”, and the Terminal is set up while you watch. It shows which client is working and each step as it runs, and Undo takes back anything the client changed. Nothing it does places orders or touches trading keys, and price alerts only notify.

Connect it

  1. Connect the server as above. When your client’s consent screen asks, approve Terminal access: See how your open Terminal is set up (mcp:terminal.read) and Set up your open Terminal (mcp:terminal.write). A client you connected before Terminal access existed does not have it. Disconnect it and connect again to approve it.
  2. Open terminal.0xarchive.io in a browser and sign in with the same 0xArchive account.
  3. Ask the client for what you want. Each call goes to your open Terminal tab (the one you had in front most recently), which runs it and answers.
If no Terminal tab is open, the call fails with terminal_not_open and a link: open the Terminal, sign in, and ask again. Terminal access works over OAuth only, and an 0xArchive API key is refused with oauth_required. ChatGPT and Codex do not show the Terminal tools yet; use another client above for them.

The Terminal tools

  • terminal_read needs mcp:terminal.read or mcp:terminal.write. It reads without changing anything: get_state (the views and the screen’s size), read_guide (how to decide what to build, the view format, every command and panel), read_view (a view as a document) and find_indicators.
  • terminal_run needs mcp:terminal.write. It runs any command: write_view, open_view, delete_view, undo, draw_level, add_price_alert, remove_marks and the read commands.
Each call takes steps, a list of {"name": ..., "args": ...} run in order, and answers each one. A good first call is terminal_read with [{"name": "read_guide"}, {"name": "get_state"}]. A view is a document: read_view gives it, the client changes it, and write_view sets it. These are the commands the Terminal gives a browser agent, described in terminal.0xarchive.io/llms.txt. To stop a client, disconnect it under Connected MCP clients in your account. Its Terminal calls stop within a minute.

When to use the MCP server

For live streaming, use WebSocket. The MCP server covers REST-shaped and historical workflows.

Permissions

The protected-resource metadata for https://mcp.0xarchive.io/mcp names the authorization server and lists the scopes the server offers. It advertises exactly the scopes its enabled tools need and nothing beyond them, so that metadata, and the consent screen your client shows you, are the live answer to what this server can do. If a scope is not listed there, the tools behind it are not enabled on the server you are connected to.
Read the live scope list
  • mcp:market.read: always offered. It reads market data: summaries, order books, trades, candles, funding, open interest, liquidations, instruments, and data quality.
  • mcp:terminal.read and mcp:terminal.write: offered when the Terminal tools are enabled on the server. mcp:terminal.read lets the client see how your open Terminal is set up. mcp:terminal.write lets it change your views, drawings and price alerts; it never places orders or touches trading keys.
  • mcp:webhooks.read and mcp:webhooks.write: offered when the webhook configuration tools are enabled on the server, and absent from the metadata when they are not. mcp:webhooks.write lets the client create and change your webhook configuration, so approve it only when you want that, and have the client ask before each change.
Whatever the metadata lists, the server does not advertise account creation, API key management, or billing and plan changes. Use your dashboard on the 0xArchive website for those.

Troubleshooting

Use the response to distinguish a sign-in problem from a missing tool, insufficient scope or an unfinished retrieval.

A historical retrieval returns partial with no records

partial means the workflow has not established a complete result for the requested window. It does not, by itself, mean the archive is empty. Read reason, any error, the coverage metadata and the number of source calls before deciding what to do next.
  • If continuation is returned, pass it to retrieve_historical_data to resume the same query.
  • If retrievalFinished is true with no continuation, the available source pages are exhausted. Inspect the reported coverage or boundary limitation instead of creating a cursor.
  • A successful trades or L4-diff request does not establish order-history coverage: they read different datasets.
For Hyperliquid order lifecycle events, use family: "hyperliquid" and dataset: "order_history" with the historical workflow. The raw tool is get_order_history; it takes coin rather than symbol:
This is a one-page call template, not a returned dataset. If the raw result supplies nextCursor, pass that exact value as cursor with the same explicit bounds and filters. A workflow continuation and a raw cursor are not interchangeable. If the result is still unexplained, email [email protected] with the tool name, arguments, complete response and any requestId. Remove credentials before sending.

No 0xArchive tools are listed, and the client reports a sign-in or authorization error

Authentication failed: the server answers HTTP 401 with a WWW-Authenticate header when the bearer token is missing, invalid, or expired. Repeat the client’s OAuth sign-in. Do not add an API key or a static Authorization header. A 503 saying authentication verification is temporarily unavailable clears on retry without changing credentials.

The tool you asked for is not in the client’s tool list

The server you connected to does not offer it, or the client’s tool selection turned it off. Check scopes_supported in the OAuth resource metadata. If mcp:webhooks.read and mcp:webhooks.write are absent, the webhook tools are not enabled on this server. Otherwise, enable the tool in the client’s tool settings.

The tool is listed, but the call returns insufficient_scope

The connection was granted without the scope the error names. The webhook tools need mcp:webhooks.read to read and mcp:webhooks.write to change anything. terminal_read needs mcp:terminal.read or mcp:terminal.write, and terminal_run needs mcp:terminal.write. Reconnect through the client’s OAuth flow and approve that scope.

Security

OAuth bearer access tokens are client-managed. Never paste an OAuth token, API key, or other credential into prompts, logs, shared chat, checked-in config, or command arguments. The hosted MCP endpoint requires no 0xArchive API key. Review the discovered tools and the permissions you grant before enabling them in your client: the market-data tools are read-only, the tools behind mcp:webhooks.write change your webhook configuration, and terminal_run changes your Terminal’s views, drawings and price alerts. An agent with mcp:feedback.write can send reports to 0xArchive without prompting for each one; do not grant that scope to agents you do not trust to make that decision.

Next step

Ask for a history window next:

Fetch ETH one-hour Hyperliquid candles for the last 24 hours.

The client calls get_candles for ETH with a 1h interval and answers with 24 hourly bars, each with open, high, low, close, and volume.
Last modified on November 15, 2026