Docs · For teams
For teams
For teams evaluating how MCP-compatible apps and agents can read Solana data, explain transactions and review simulation output.
01
Designing a connection
Data, transport and authority
01 · Structured reads
Map public Solana data to tools your client can inspect.
Reference scopeAccounts, balances, tokens, signatures, transactions, network context and simulation results
02 · Clear authority
Use public chain identifiers without connecting a wallet.
Safety boundaryPublic data access and transaction authorization have different credentials and review requirements
02
Good to know
Provider selection
Choose a server and RPC provider with suitable authentication, limits, availability and data policies.
Solana-native
Inputs and outputs use Solana addresses, signatures, lamports, slots and RPC semantics.
Tool permissions
Check which tools a server actually exposes and what every call reads, sends or changes.
Explore the client connection model and configuration examples.
Explore clients →