Connection & Access
Understand how an AI client connects to a tool server, and how service credentials differ from the keys that authorize a Solana transaction.
Connecting a client
Transport, endpoint and permissions
An MCP client needs a server address and a supported transport. The server describes its tools and may require authentication. Use the client guide and configuration reference to understand the connection. Examples on this site describe the format and require a service you choose to operate or trust.
Access and authority
Public data and private credentials
Solana RPC can return public balances, accounts and transaction history without a wallet signature. A provider may still require an API key and apply its own limits. That service credential authorizes API access. A wallet signature separately authorizes the exact transaction message. Keep seed phrases, secret keys and service credentials out of prompts and public configuration.