Use BlockReq with AI Assistants

BlockReq publishes its docs in forms that AI assistants and coding agents can read directly, and runs a public MCP server. Everything below is generated from the same catalogs and templates as these pages, so it stays in sync with them.

Machine-readable docs

Resource	What it holds
llms.txt	An index of every docs page, grouped by topic, following the llmstxt.org format
llms-full.txt	The core docs in one Markdown file, with a network capability table and every JSON-RPC method once
Markdown pages	Every page is also available as Markdown: add `index.md` to its URL, for example `https://blockreq.com/docs/build/api-reference/ethereum/eth_getBalance/index.md`
networks.json	Every published network with its host, public URL, private URL pattern, WSS, and archive and proof/debug/trace flags
OpenRPC	One OpenRPC document per EVM network, listing exactly the methods documented for it

Point a general-purpose agent at https://blockreq.com/docs/llms.txt and let it follow the links it needs.

The blockreq-rpc Agent Skill

The blockreq-rpc skill teaches a coding agent how to call BlockReq: endpoint URLs, how to pick the network host, which methods need archive data or are limited to proof/debug/trace networks, eth_subscribe over WSS, Request Counting and plan limits, short viem, ethers, curl, and web3.py examples, and common pitfalls.

Browse it: SKILL.md, with networks and methods references.
Download it: blockreq-rpc.zip.
Install it from GitHub: blockreq/skills is a Claude Code plugin marketplace that syncs this skill from the ZIP above every day.

Claude Code

Install the plugin from the blockreq/skills marketplace:


/plugin marketplace add blockreq/skills
/plugin install blockreq-rpc@blockreq

Or copy the skill in yourself. For your user, so every project can use it:


mkdir -p ~/.claude/skills && cd ~/.claude/skills
curl -fsSLO https://blockreq.com/docs/agent-skills/blockreq-rpc.zip
unzip -o blockreq-rpc.zip && rm blockreq-rpc.zip

For one project, unzip it into that project's .claude/skills/ folder so it is committed with the code. Either way the skill lives in a blockreq-rpc/ folder, and Claude Code loads it when a task involves BlockReq RPC.

Claude.ai

Download blockreq-rpc.zip and upload it as a custom skill in Claude.ai. Custom skills need a Pro, Max, Team, or Enterprise plan with code execution enabled; see Anthropic's Using Skills in Claude for where to upload.

Other agents

Agents that do not read Agent Skills can use https://blockreq.com/docs/llms.txt, or load SKILL.md and its reference files as instructions.

The BlockReq MCP server

https://mcp.blockreq.com/mcp is a remote MCP server over Streamable HTTP. It is public, free, and read-only, and it works without an API key or sign-in. Connect it with your BlockReq API key as a bearer token (Authorization: Bearer <API key>) and call_rpc uses your own private endpoint instead of the shared public trial.

Tool	What it does
`list_chains`	Lists every published network with its host, public URL, private URL pattern, WSS, and archive and proof/debug/trace flags
`get_chain`	Returns one network's URLs, flags, API reference page, and documented JSON-RPC methods
`search_docs`	Searches these docs, in English or Chinese, and returns titles, URLs, and snippets
`get_doc_page`	Returns one docs page as Markdown
`get_method_reference`	Returns a method's parameters, result, example, and endpoints on one EVM network, from its OpenRPC document
`call_rpc`	Calls a read-only method on an EVM network's public trial endpoint, or on your own endpoint when you connect with an API key or a signed-in account: `eth_blockNumber`, `eth_chainId`, `eth_getBalance`, `eth_call`, `eth_getLogs`, `eth_getTransactionByHash`, `eth_getTransactionReceipt`, `eth_getCode`, `eth_getStorageAt`, and `eth_getBlockByNumber`

Without a key, call_rpc goes through the same rate-limited public trial endpoint as https://<host>/v1/rpc/public, so it serves recent state only, without deep history, debug, or trace, and every client that shares an IP address shares that limit. With a key, it calls https://<host>/v1/rpc with your key in the X-API-Key header: the call counts against your account's Requests (the Free plan includes 3,000,000 every 30 days) and gets your plan's limits and history, and the key must belong to an endpoint that covers the network. The server never returns or logs your key. eth_getLogs takes numeric fromBlock and toBlock at most 1,000 blocks apart, or a blockHash, and responses above 256 KB are refused. The server cannot sign or send transactions. Production code should call a private endpoint with an API key instead.

Claude Code


claude mcp add --transport http blockreq https://mcp.blockreq.com/mcp \
  --header "Authorization: Bearer $BLOCKREQ_API_KEY"

Leave out --header to use the public trial. Add --scope user to make it available in every project. See Connect Claude Code to tools via MCP.

Cursor

Add the server to ~/.cursor/mcp.json, or to .cursor/mcp.json in one project:


{
  "mcpServers": {
    "blockreq": {
      "url": "https://mcp.blockreq.com/mcp",
      "headers": { "Authorization": "Bearer ${env:BLOCKREQ_API_KEY}" }
    }
  }
}

Leave out headers to use the public trial.

See Cursor's Model Context Protocol docs.

Claude.ai and other hosted clients: connect your account

Hosted clients run on their provider's servers, so their users share a few IP addresses and one public trial limit. Add https://mcp.blockreq.com/mcp/account instead:

The client sends you to blockreq.com to sign in and approve access.
call_rpc then uses your active endpoint on each network, and every call counts against your Requests.
You need an active endpoint for each network you call; create one at blockreq.com/dashboard.
The client never receives your API key.
Claude.ai: add https://mcp.blockreq.com/mcp/account as a custom connector and connect when asked; see Anthropic's Get started with custom connectors using remote MCP. To try it without an account, add https://mcp.blockreq.com/mcp instead.
Other clients that support MCP authorization (OAuth 2.1 with dynamic client registration) connect to https://mcp.blockreq.com/mcp/account the same way.

Other clients

Any client that supports remote MCP servers over Streamable HTTP: use the URL https://mcp.blockreq.com/mcp, and add the header Authorization: Bearer <API key> if the client allows custom headers.
Clients that only start local (stdio) servers can bridge to it with npx mcp-remote https://mcp.blockreq.com/mcp.