MCP server for AI agents

SwiftNodes runs a hosted Model Context Protocol server, so Claude Code, Cursor, Codex and other MCP clients can look up chains and endpoints, check method support, and make RPC calls without you pasting URLs into the chat.

Server URL

https://rpc.swiftnodes.io/mcp

Streamable HTTP transport with JSON responses. Send your API key as Authorization: Bearer <key> (or x-api-key). Without a key the public tools still work.

Claude Code

export SWIFTNODES_API_KEY=...   # from the dashboard, or: swiftnodes project setup
claude mcp add --transport http --scope user swiftnodes https://rpc.swiftnodes.io/mcp \
  --header "Authorization: Bearer $SWIFTNODES_API_KEY"

Cursor and other clients

Add a remote server to your MCP config (for Cursor, ~/.cursor/mcp.json):

{
  "mcpServers": {
    "swiftnodes": {
      "url": "https://rpc.swiftnodes.io/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Prefer a local process? The same public tools run over stdio with npx -y swiftnodes-mcp(source).

Tools

Tool	What it does	Key
list_chains	Every chain we serve: slug, chain ID, live status, and whether WebSocket and archive are available. Filter by name.	no
get_chain	One chain in detail, with HTTP, WebSocket and archive URL templates.	no
get_pricing	Plans, prices and rate limits.	no
get_method_support	Which JSON-RPC methods work on which chain, probed weekly through the customer path (trace, debug, eth_getProof, archive and more).	no
probe_endpoint	Check any public EVM endpoint: chain ID, block height, archive capability and latency, or make one call.	no
rpc_call	Make a JSON-RPC call on any chain with your key. Counts against your plan like any other request.	required
get_account	Your plan, limits, requests used this month and the restrictions on the key in use. Never returns key values.	required

Limits and safety

rpc_call goes through the normal endpoint, so your plan's rate limit, monthly cap and any IP or origin restrictions on the key apply.
No tool returns your key. Tell your agent to read it from SWIFTNODES_API_KEY and never print it.
probe_endpoint only reaches public addresses and does not follow redirects.

Next: the CLI writes your key and URLs into .env, and the agent cookbook has tested prompts that use both.