Solana MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getSlotC | Get the current slot |
| getBalanceC | Get balance for a Solana address |
| getKeypairInfoC | Get information about a keypair from its secret key |
| getAccountInfoB | Get detailed account information for a Solana address |
| transferC | Transfer SOL from your keypair to another address |
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 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.