MCP

NOWNodes MCP server

Give your AI assistant direct access to NOWNodes documentation for 120+ networks through the Model Context Protocol (MCP). Once connected, a compatible assistant can look up supported networks, browse RPC methods and parameters, check API-key requirements, and generate ready-to-run request examples.

About MCP

The Model Context Protocol (MCP) is an open standard that lets AI assistants call external tools through a uniform interface. An MCP server publishes tools; a compatible assistant — Claude, Cursor, Codex, and others — discovers and calls them as needed.

The NOWNodes MCP server connects your AI tools to documentation. It exposes seven tools for listing supported networks, browsing RPC methods and their parameters, checking API-key requirements, searching the docs, and generating request examples in curl, Node.js, and Python — covering 120+ networks including Bitcoin, Ethereum, Solana, TON, BNB Smart Chain, TRON, and XRP.

Configure your agent

The server is hosted remotely and works with any MCP-compatible assistant — including Claude (Code, Desktop, and claude.ai), OpenAI (Codex and the Responses API), Cursor, VS Code, Windsurf, and Zed. Connect by pointing your client at the endpoint over Streamable HTTP (not SSE):

https://mcp.nownodes.io/mcp

Pass an access token as Authorization: Bearer <token> only if the deployment requires it. You can obtain your access token in your NOWNodes personal account:

https://account.nownodes.io/profile/statistics

Claude Code

claude mcp add --transport http nownodes https://mcp.nownodes.io/mcp \
  --header "Authorization: Bearer $YOUR_NOWNODES_TOKEN"

Codex — add to ~/.codex/config.toml, then export YOUR_NOWNODES_TOKEN before running codex:

[mcp_servers.nownodes]
url = "https://mcp.nownodes.io/mcp"
bearer_token_env_var = "YOUR_NOWNODES_TOKEN"

JSON-config clients — Cursor, VS Code, Windsurf, Zed, and others share this base configuration:

{
  "mcpServers": {
    "nownodes": {
      "type": "http",
      "url": "https://mcp.nownodes.io/mcp",
      "headers": { "Authorization": "Bearer <YOUR_NOWNODES_TOKEN>" }
    }
  }
}

Adjust the file location and, where noted, the field names:

Claude Desktop, claude.ai, and ChatGPT — add the endpoint as a custom connector in the client's connectors/integrations settings, and provide the token as a Bearer token if prompted. Some web clients require OAuth for public remote connectors; if you cannot pass a Bearer token, connecting end users at scale requires OAuth on the NOWNodes side.

Responses API — attach the server as an MCP tool:

const response = await client.responses.create({
  model: "gpt-5.5",
  input: "Show supported NOWNodes networks and an example request for ETH.",
  tools: [{
    type: "mcp",
    server_label: "nownodes",
    server_url: "https://mcp.nownodes.io/mcp",
    authorization: process.env.YOUR_NOWNODES_TOKEN,
    require_approval: "never"
  }]
});

If a client cannot send headers, use OAuth, an individual URL issued through a proxy layer, or a client that supports Bearer tokens. Field names vary between clients: url, serverUrl, endpoint, transport: "http", type: "streamable-http".

Usage

Once connected, ask your assistant in natural language from its normal chat or prompt input — you do not call the tools by name. If the connection works, the assistant uses the NOWNodes MCP tools instead of answering from memory. Example prompts:

Find methods for btc-mainnet related to block.

Available tools

Supported chains

The server currently supports 120+ networks, including Bitcoin, Ethereum, Solana, TON, BNB Smart Chain, TRON, XRP, Cardano, and Dogecoin. The list changes over time, so query it at runtime — ask your assistant to call nownodes_list_chains for the current set.

To request a network that is not yet supported, or a dedicated server for a specific network, contact [email protected].

Troubleshooting

Server does not appear — confirm the URL, that the client supports remote / Streamable HTTP, that you restarted the client after editing the config, and that the token is passed in Authorization: Bearer ....

401 Unauthorized — the token is missing or incorrect.

403 Origin is not allowed — a browser-based client's origin is not allowlisted. Contact [email protected] to add it.

Client cannot send an Authorization header — use OAuth. Bearer tokens suit IDEs, CLIs, and API clients that allow custom headers.

Security

• Do not put a real API key in public prompts.
• Generated examples use YOUR_API_KEY unless you specify otherwise.
• The MCP does not execute or sign transactions.
• For public, large-scale connections, prefer OAuth over a shared Bearer token.