Minimal, fast, and extensible MCP servers for interactions with JSON-RPC blockchain nodes. Support EVM and Solana blockchains.
🍒 Extra feature: a separate MCP server with tools for pump.fun bonding curve calculations and analysis.
git clone https://github.com/chainstacklabs/rpc-nodes-mcp.git
cd rpc-nodes-mcp2. Install dependencies with uv
| Mode | Command |
|---|---|
| Base | uv pip install -r pyproject.toml |
| Dev | uv pip install -r pyproject.toml -e '.[dev]' |
| Test | uv pip install -r pyproject.toml -e '.[test]' |
Default Chainstack endpoints are already provided, but if you'd like to use different ones, please add them to .env. The complete list of environment variables:
ARBITRUM_RPC_URL=
BASE_RPC_URL=
BINANCE_SMART_CHAIN_RPC_URL=
ETHEREUM_RPC_URL=
SONIC_RPC_URL=
SOLANA_RPC_URL=
OPENAI_API_KEY=
Note: OPENAI_API_KEY is only required for tests with scripts/run_mcp_client_example.py.
npx @modelcontextprotocol/inspector uv run main_evm.pyFor more details, visit Model Context Inspector.
A client example that interacts with the MCP server (requires OPENAI_API_KEY environment variable):
uv run scripts/run_mcp_client_example.pyTool for auto-generating MCP interfaces and implementations (only tools currently) based on OpenAPI spec (see Chainstack open-source docs):
uv run scripts/generate_mcp_tools.py scripts/openapi_specs/ethereum.json scripts/generated evmNote: auto-generated tools require further improvements, see here.
EVM chains
Solana
Pump Fun
The mcp.json file contains MCP server configurations. For VS Code users, place this file in the .vscode folder within your project directory. GitHub Copilot in Agent Mode will automatically discover and launch the configured servers.
The claude_desktop_config.json file contains MCP server configurations. For Claude Desktop users, place this file in the Claude Desktop data folder. Claude Desktop will automatically discover and launch the configured servers.
uv location errors: specify the full path to uv in the mcp.json file. To get the full path, run where uv command.
environment variables: double check you created .env file in the MCP servers folder and required endpoints.
