Solana MCP Server
# Solana MCP Server
A Model-Context-Protocol server for interacting with the Solana blockchain. This server provides simple RPC endpoints for common Solana operations.
## Features
- Get current slot number
- Check account balances
- Get detailed account information
- Display keypair information
- Transfer SOL between accounts
## Quickstart
clone and install dependencies:
```bash
git clone https://github.com/yourusername/solana-mcp-server.git
cd solana-mcp-server
npm install
```
build the tool
```bash
npm run build
```
add the tool to your claude_desktop_config.json
```
"solana-rpc": {
"command": "node",
"args": [
"/PATH/TO/solana-mcp-server/build/index.js"
]
}
```
## Usage
Ask Claude:
- whats the latest slot on solana?
- whats the balance of 62QXuWZ3WT6ws1ZFxJobVDVXn6bEsiYpLo5yG612U6u3?
- Here's my test key [REPLACE WITH SECRET KEY]. let's transfer 0.001 SOL to [REPLACE WITH PUBLIC ADDRESS]
## Security Note
Only use this with a test wallet with a small amount of funds.
## RPC Endpoint
The server connects to Solana's mainnet at `https://api.mainnet-beta.solana.com`. To use a different network (like devnet or testnet), modify the `SOLANA_RPC` constant in `src/index.ts`.
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: getAccountInfo retrieves detailed account data, getBalance focuses on balance only, getKeypairInfo handles keypair details, getSlot provides blockchain slot information, and transfer performs SOL transactions. There is no overlap or ambiguity in their functions.
All tool names follow a consistent verb_noun pattern using camelCase (e.g., getAccountInfo, getBalance, transfer). The naming is uniform and predictable across all five tools.
With 5 tools, the count is well-scoped for a Solana server, covering essential operations like querying accounts, balances, keypairs, slots, and transfers. It feels slightly thin but reasonable for basic blockchain interactions.
The tools cover key read operations (getAccountInfo, getBalance, getSlot) and a basic write operation (transfer), but there are notable gaps such as missing transaction history, program interactions, or token operations that are common in Solana workflows. Agents can work around this for simple tasks.