Solana MCP Server: Connect Solana RPC to Claude
What is the ERPC Solana MCP Server?
The ERPC Solana RPC MCP Server lets Claude access read-only Solana RPC methods through natural-language requests.
With the ERPC Solana RPC MCP Server, you can ask questions like wallet checks, transaction investigation, and network health monitoring, and Claude can call the required Solana RPC tools for you.
The tools are read-only Solana RPC methods and a check of your RPC token balance;
sendTransaction and requestAirdrop are not included.Setup
Step 0 - Sign in to ERPC with Google
Sign in to the ERPC Web Dashboard with Google: choose
Google under Login with. Your ERPC account also needs an RPC key, which you can see in the RPC keys tab of the dashboard. Tool calls are sent with this RPC key, and the Solana RPC tools use your RPC tokens. Before the one-time €5 verification fee is paid, or while no tokens remain, results from the Solana RPC tools start with Request failed (HTTP 401) and say that the RPC key was not accepted, even after your Google account is linked. If you get this result, check your key in the RPC keys tab of the dashboard, pay the verification fee in the dashboard if you have not already, and check your RPC token balance with the tool that shows it.An IP allowlist on your RPC key does not apply to calls from this MCP server, so you do not need to remove it; it still applies to RPC requests that use the key directly. However, the Solana RPC tools do not accept a paused, revoked or expired key.
To link Google to your ERPC account, sign in to the dashboard with a Google account that uses the same email address as your ERPC account. The MCP server then uses the ERPC account that your Google account is linked to.
- ERPC Web Dashboard: ERPC Web Dashboard
Use the same Google account later when you authorize in Claude.
Step 1 - Add the MCP server in Claude Connectors
In Claude, open
Settings -> Connectors -> Add custom connector and set this server URL:endpoint
Step 2 - Authorize with the same Google account
After adding the connector, start the connection. The
Connect to ERPC screen appears first; select Continue with Google and choose the same Google account you used in Step 0.The connection expires 30 days after you authorize, or sooner once it goes unused for 7 days. Authorize again with the same Google account to reconnect.
Step 3 - Verify with simple prompts
After connection is complete, run simple prompts to verify tool calls.
- Balance check (getBalance)
- Cluster health / epoch info (getHealth, getEpochInfo, getSlot)
- Block info (getBlockHeight, getLatestBlockhash)
Reference Videos
Use Cases Demo (Wallet, Transaction, Network Health)
3 Use Cases
Use Case 1 - Wallet Balance Check
Prompt:
Tool called:
getBalanceUse this when you want to monitor wallets, verify transfers, or check holdings quickly.
Use Case 2 - Transaction Investigation
Prompt:
Tool called:
getTransactionYou can inspect instructions, signers, fees, and status, then get a natural-language explanation of what happened.
Use Case 3 - Network Health Monitoring
Prompt:
Tools called:
getEpochInfo, getSlot, getHealthThis is useful for validator operation, RPC operation, and trading system monitoring.
Why It's Useful
When getting started on Solana, building the right RPC query for each goal can take time.
With MCP, you describe what you want in natural language and Claude can map it to the right Solana RPC method for you. This lowers the barrier for both quick checks and deeper chain analysis.
Get Started
- Sign in to the ERPC Web Dashboard with Google and check that your account has an RPC key.
- Add the MCP server URL in Claude Connectors.
- Authorize with the same Google account.
- Start with
getBalance,getTransaction, and network health prompts.
- MCP Server: https://mcp-solana-rpc-api.erpc.global/mcp
- ERPC Web Dashboard: ERPC Web Dashboard






