Solana tool referenceRead · Understand · Simulate · Connect

How it works

Explore how an AI client can work with Solana data through a tool interface. Read accounts, balances and transactions, understand instructions, and review simulation results. This page explains the request flow and integration design. The website provides reference material for configuring a separately deployed MCP service.

ConnectionYour configured MCP service
NetworkSolana mainnet-beta
ReadsPublic identifiers, no signature
MCP in one paragraph

MCP, the Model Context Protocol, is an open protocol for connecting AI clients to tools. A client that supports it, such as Claude, Claude Code, ChatGPT, Cursor, VS Code or Devin Desktop, can be pointed at an MCP server and will then see that server's tools, with a description of what each one does and what it needs. When you ask for something, the AI decides which tool fits, calls it, and uses the answer in its reply. The examples here describe a Solana tool interface. A service advertises its own tools and limits, and a client must discover that actual tool list after connecting.

01

The path of a request

What happens after you ask a question in your AI client.

Your AI clientClaude, Claude Code, ChatGPT,Cursor, VS Code, Devin Desktopyou ask in plain words MCP serviceConfigured by the clientDiscover the advertised toolsvalidate tool inputs SolanaRPC nodeSolana explorerSolana mainnet-beta Your walletseparate signing authority 1 tool call 2 RPC request 3 data 4 result review separately
Fig. 1Read requests follow steps 1 to 4 using public chain identifiers. Simulation takes transaction bytes and reports execution details at the selected state. Signing and broadcasting require a separately authorized application flow.
01 · You ask

You type a request in your AI client in plain words, for example “why did my last deposit fail?”.

Your AI client
02 · A tool is picked

The client discovers the service's advertised schemas. It can select solana_get_transaction with a signature, then inspect available instructions and logs to explain a failure.

MCP tool call
03 · The service reads

A configured service validates the request, calls the selected Solana RPC and returns structured data with its network and commitment context.

Solana RPC
04 · Back to you

The AI uses the returned records in its answer. Logs, errors and missing data should stay visible so the explanation can be checked against the transaction.

Your AI client
02

Twelve groups of tools

Reference schemas and designs, with protocol context.

Group 01Reference

Read and simulate

Nine reference schemas describe Solana account, token, transaction and network data, plus transaction simulation. They explain RPC inputs and outputs for a separately configured service.

solana_get_balance
solana_get_token_balances
solana_get_account_info
solana_get_signatures
solana_get_transaction
solana_get_signature_status
solana_get_token_supply
solana_network_status
solana_simulate_transaction

Group 02Reference

Understand

Read the structure of a transaction and compare its intended effects with the available chain data. Simulation, decoding and log inspection answer different questions and carry different limits.

solana_simulate_transaction
solana_decode_transaction
solana_trace_call

Group 03Design

Build

A development workflow starts with reviewed Rust or Anchor source, reports compiler diagnostics, estimates transaction costs and verifies deployed binaries. These schemas outline a developer integration.

solana_scaffold
solana_program_build
solana_estimate_fees
solana_deploy
solana_verify

Group 04Design

Act

Transaction preparation, signing, submission and confirmation are separate steps. This design reference makes the required authorities, network and expected account changes explicit at each step.

solana_prepare_transaction
solana_prepare_batch
solana_send_signed
solana_wait
solana_key_status
solana_agent_wallet

Group 05Design

Agents

Agent integrations need explicit identity, service discovery, payment authorization and event processing. The examples describe application designs and avoid assuming a single Solana agent registry or reputation standard.

solana_agent_register
solana_agent_lookup
solana_agent_feedback
solana_agent_pay
solana_agent_job
solana_watch
solana_react
solana_index

Group 06Mechanics

Drift perps

Drift perpetuals use Solana accounts, oracle prices, margin and funding. Liquidity can come from its decentralized orderbook, just-in-time makers and AMM. The reference separates market data from order execution.

solana_perps_markets
solana_perps_market
solana_perps_account
solana_perps_funding
solana_perps_candles
solana_perps_risk
solana_perps_plan
solana_perps_scan
solana_perps_backtest
solana_perps_agent
solana_perps_submit

Group 07Design

Privacy and data

Solana account activity is publicly observable. Privacy designs must specify the additional protocol, threat model and metadata exposure. Local preparation alone does not conceal an on-chain sender, recipient or amount.

solana_private_pool
solana_private_deposit
solana_private_withdraw
solana_private_invoice
solana_private_risk
solana_private_disclose
solana_private_session

Group 08Mechanics

Jupiter Swap

Jupiter aggregates token-swap liquidity on Solana. Quotes describe routes, amounts, fees and execution constraints, while transaction instructions support a separate wallet-signing flow. Liquidity positions belong to the underlying DEX.

solana_jupiter_tokens
solana_jupiter_quote
solana_jupiter_swap
solana_jupiter_swap_instructions
solana_jupiter_route
solana_jupiter_price
solana_jupiter_order_status
solana_jupiter_transaction_review

Group 09Mechanics

Raydium LaunchLab

LaunchLab is Raydium's token-launch product. Tokens trade along configured bonding curves before eligible launches graduate into Raydium liquidity pools. Launch parameters, fees and migration rules belong to that protocol.

solana_raydium_pools
solana_raydium_quote
solana_raydium_swap
solana_raydium_launchlab

Group 10Mechanics

Wormhole

Wormhole supports cross-chain messaging and token-transfer integrations, including Solana. A transfer spans source and destination chains with separate finality, verification and redemption steps. Routing support depends on the chosen product.

solana_wormhole_route
solana_wormhole_transfer

Group 11Mechanics

Kamino

Kamino provides Solana lending markets and vault strategies. Review reserve utilization, collateral risk, borrow positions and strategy parameters. Yields vary with market activity, fees and the selected product.

solana_kamino_markets
solana_kamino_obligation
solana_kamino_vaults
solana_kamino_deposit
solana_kamino_withdraw

Group 12Mechanics

Pyth price data

Oracle prices need a feed identifier, publish time, exponent and confidence interval. Pyth provides price-update products for Solana, each with its own verification, freshness and access requirements.

solana_pyth_price

The catalogue separates RPC references, application designs and protocol mechanics. Tool names are illustrative schemas. A connected service determines which calls are actually available.

Explore tool references →
03

Review a transaction

Understand the message, signers and simulation before using a separate wallet application.

Transaction review example
Input unsigned transaction bytes Review fee payer and required signers program IDs and account roles instructions and token amounts signature and priority fees RPC simulation logs, errors and compute use Check cluster, commitment and blockhash expiry Wallet explicit signing in a separate application Result signature status and finalized account changes
Review

Inspect the actual message

Decode the transaction bytes and inspect the fee payer, signers, program IDs and token changes. A readable preview should be tied to that message before any wallet authorizes it.

Design

Define delegated authority

A smart-wallet design can define spending caps, program scope and expiry. These limits depend on the selected program and its enforcement. Review revocation and fee funding as part of the authority model.

Capper transaction and per day
Scopeallowed programs and functions
Expirywhen the key stops working
Design

Compare state and outcome

Simulation is an observation at a point in time. Recheck the network, blockhash and relevant account state before submission, then inspect confirmation and execution errors afterward.

04

Connect with clear context

Read, understand and simulate on the intended cluster.

Network 01

Solana

Accounts, balances, instructions and simulation form the core Solana reference. Select the cluster and commitment explicitly.

Endpoints

A configured service

An MCP client needs a service URL and transport settings. Its discovered tool list determines the available operations and network scope.

Portable

Discover the schema

Check each tool's input schema, permissions, error format and data source. Similar names can still have different service limits.

Oracle context

Pyth price data

Review feed IDs, publication times and confidence intervals. Oracle freshness and verification depend on the selected Pyth product.