solana-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOLANA_RPC_URL | No | RPC endpoint for balance lookups. The public endpoint is rate-limited - use your own (Helius, QuickNode, Triton, ...) for anything beyond light use. | https://api.mainnet-beta.solana.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sol_priceA | Get the current price of SOL in USD. |
| get_wallet_balanceA | Get the native SOL balance of a Solana wallet address (mainnet). |
| get_token_balancesA | List the non-zero SPL token balances held by a Solana wallet address. |
| get_recent_transactionsA | List the most recent transactions for a Solana wallet address, newest first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct data type: price, native balance, token balances, and transaction history. There is no overlap in purpose, making tool selection unambiguous.
All tool names follow a consistent get_ prefix with snake_case, clearly indicating read-only operations. The pattern is uniform across the entire set.
With 4 tools, the server is tightly scoped for its purpose of providing Solana blockchain data lookups. Each tool covers a distinct useful query without unnecessary bloat.
The set covers core Solana data retrieval needs: price, native balance, token balances, and transactions. Minor gaps like transaction details or token metadata are not covered, but the essential surface is present.