rpc-nodes

This MCP server exposes a minimal, fast interface to multiple blockchain RPC nodes via the Model Context Protocol. It supports both EVM-compatible chains and Solana, enabling clients to route JSON-RPC calls to the appropriate backend RPC URL through a single MCP endpoint. The server is designed to be extended with tooling generated from OpenAPI specs, which can produce MCP interfaces and implementations for different chains. You can also leverage the accompanying client example to test interactions against the MCP server, provided you supply an OpenAI API key if you wish to run the example. To start using it, run the server via the uv runtime and point your calls to the rpc-nodes MCP endpoint; the server will forward requests to the configured RPC URLs and return responses according to MCP contracts.

Prerequisites:

• Python 3.8+ and pip (or a Python environment managed by uv)
• uv runtime (uvx is the Python/uv companion; here we run the server via uv)
• Git for cloning the repository

1. Clone the repository

git clone https://github.com/chainstacklabs/rpc-nodes-mcp.git
cd rpc-nodes-mcp

2. Install dependencies

• Install uv (Astral UV) per their documentation if not already installed:

# Example (adjust per your OS):
pip install uv

3. Install Python dependencies for the MCP server

pip install -r pyproject.toml

4. Configure environment variables (see .env guidance in the README). Create a .env with the following sample variables:

ARBITRUM_RPC_URL=
BASE_RPC_URL=
BINANCE_SMART_CHAIN_RPC_URL=
ETHEREUM_RPC_URL=
SONIC_RPC_URL=
SOLANA_RPC_URL=
OPENAI_API_KEY=

5. Start the MCP server

uv run main_evm.py

Notes:

• If you are using a different uv installation path, ensure the path to uv is accessible in your environment or specify the full path in the mcp_config if required.
• The server can also be launched via npx inspector as shown in the README, depending on your toolchain.

Environment variables define the RPC endpoints for each supported chain. Ensure you have the correct endpoints and that network access is allowed from your runtime environment. OPENAI_API_KEY is only required for the example/MCP client tests. If you encounter uv location errors, provide the full path to uv in your runtime or adjust your PATH accordingly. When adapting configuration for VS Code or Claude Desktop, place the mcp.json with the correct server name and command in the appropriate directories. If you modify endpoints, keep the defaults as a fallback to avoid breaking existing tests.