RouteMesh MCP Server

@routemesh/mcp is a local stdio MCP server for querying blockchain data through RouteMesh.

At a glance

• Query multiple EVM chains from one MCP server.

• Pull useful on-chain data quickly (blocks, txs, logs, balances, fees).

• Use generic JSON-RPC when you need methods beyond built-in tools.

• Reduce RPC endpoint management overhead with RouteMesh routing + failover.

• Plug into Cursor as an on-demand command, not a background daemon.

Related MCP server: dRPC Agent Skills

Prompt examples

• "List chains that match base and show me their chain IDs."

• "Get the latest block on BSC and summarize timestamp + tx count."

• "Fetch receipt for tx 0x... on Ethereum and tell me if it succeeded."

• "Get logs for this contract on Arbitrum between block X and Y."

• "Estimate gas for calling this method on Base using these params."

• "Run eth_getCode on chain 8453 for address 0x...."

• "Show my RouteMesh usage for the last 7 days broken down by chain."

• "What is my current RouteMesh balance and request count this month?"

Tools

• rpc_list_chains - discover and filter supported chains (via GET /chains on the API server)

• rpc_call - generic JSON-RPC escape hatch

• rpc_get_block - fetch by number/tag/hash

• rpc_get_transaction - fetch transaction by hash

• rpc_get_transaction_receipt - fetch receipt by hash

• rpc_get_logs - query logs with block/topic filters

• rpc_get_balance - native token balance for an address

• rpc_call_contract - read-only eth_call

• rpc_estimate_gas - gas estimation

• rpc_get_fee_data - gas price + EIP-1559 hints

• rpc_trace_transaction - trace/debug transaction best effort

• get_usage - customer usage summary and balance from the API server (requires management token)

• list_api_keys - list customer API keys (requires management token)

• create_api_key - create a new API key with allowed domains and routing strategy (requires management token)

• update_api_key - update an existing API key (requires management token)

Customer tools

When ROUTEMESH_MGMT_TOKEN is set, the server exposes customer-scoped tools that call the API server with the management token in the x-api-key header.

Create a management token in the RouteMesh dashboard with a route allowlist that includes:

• GET /usage

• GET /api-keys

• POST /api-keys

• PUT /api-keys/*

get_usage — usage summary and balance

get_usage fetches customer usage data from the API server (GET /usage).

Examples:

• Default (last 30 days, summary + balance): call get_usage with no parameters

• Custom window with chain breakdown: from=2026-06-01T00:00:00Z, to=2026-06-18T00:00:00Z, include=["summary","by_chain"]

• Hourly time series for one API key: include=["time_series"], granularity="hour", apiKeyId=42

• Top methods on a chain: include=["top_methods"], chainId="ethereum", limit=10

• Flat grouped rows: groupBy="api_key,chain", limit=50

list_api_keys — list API keys

list_api_keys calls GET /api-keys and returns an array of API key metadata (id, name, active, allowed_domains, routing_strategy, timestamps). The secret api_key value is never returned by this endpoint.

create_api_key — create a new API key

create_api_key calls POST /api-keys to provision a new key. The request requires:

Important: The response includes the secret api_key value, which is only shown once at creation. Store it securely — it cannot be retrieved again.

update_api_key — update an existing API key

update_api_key calls PUT /api-keys/:apiKey for partial updates:

At least one of name, active, or allowed_domains must be provided. The secret api_key value is never returned by this endpoint.

Prerequisites

• Node.js 20+

• RouteMesh API key (sign up)

• Customer management token with GET /usage, GET /api-keys, POST /api-keys, and PUT /api-keys/* in the route allowlist (optional, for customer tools)

Quick start

Install and build:

npm install
npm run build

Set API key for local dev:

cp .env.example .env

Run local build:

ROUTEMESH_API_KEY=your_key_here node dist/index.js

Run in dev mode:

ROUTEMESH_API_KEY=your_key_here npm run dev

Run published package:

ROUTEMESH_API_KEY=your_key_here npx -y @routemesh/mcp

Cursor MCP config

Add one of these to ~/.cursor/mcp.json.

Local build:

{
  "mcpServers": {
    "routemesh": {
      "command": "node",
      "args": ["/ABSOLUTE/PATH/TO/PROJECT/dist/index.js"],
      "env": {
        "ROUTEMESH_API_KEY": "replace-with-your-routemesh-key",
        "ROUTEMESH_MGMT_TOKEN": "replace-with-your-customer-mgmt-token"
      }
    }
  }
}

Published package via npx:

{
  "mcpServers": {
    "routemesh": {
      "command": "npx",
      "args": ["-y", "@routemesh/mcp"],
      "env": {
        "ROUTEMESH_API_KEY": "replace-with-your-routemesh-key",
        "ROUTEMESH_MGMT_TOKEN": "replace-with-your-customer-mgmt-token"
      }
    }
  }
}

Development commands

• npm run typecheck - static type checking

• npm run test - run tests once

• npm run test:watch - watch mode

• npm run build - compile to dist/

Release

npm run test
npm run build
npm version patch
npm publish --access public

Notes

• The server is read-only for on-chain RPC tools.

• get_usage reads billing/usage data from the API server; it does not use Atlas.

• Requests use ROUTEMESH_BASE_URL first, then ROUTEMESH_BACKUP_BASE_URL on retryable failures.

• rpc_list_chains reads chain data from GET /chains on the API server (ROUTEMESH_API_SERVER_URL).

References

• RouteMesh docs: https://routeme.sh/docs