Deploys, mints, transfers and trades are all real transactions, and the only thing separating a rehearsal from a costly error is which RPC URL is in the environment. The test-funds tool makes devnet genuinely usable, which is the right place to learn what the agent does with these tools before anything is at stake. On the read side, price, asset, domain and throughput lookups are useful on their own and carry none of that risk.
An MCP server built on the Ping Agent Kit that puts Solana operations behind a standard tool interface. It carries a wallet from a private key you supply and an RPC endpoint you choose, so an assistant can query the chain and execute transactions on whichever network you point it at.
- Wallet basics — `WALLET_ADDRESS` and `BALANCE`
- Token movement and creation — `TRANSFER`, `DEPLOY_TOKEN`, `MINT_NFT`
- Market operations — `TRADE` and `GET_PRICE`
- Chain lookups — `GET_ASSET` for a token or asset, `RESOLVE_DOMAIN` for Solana domain names, `GET_TPS` for current network throughput
- Test funds on request, which is what makes devnet work practical — `REQUEST_FUNDS`
A Solana wallet private key and an RPC URL for the network you intend to use — mainnet, testnet or devnet — supplied as `SOLANA_PRIVATE_KEY` and `RPC_URL`; `OPENAI_API_KEY` is optional. Node.js v16 or higher. The README's global install line names `ping-mcp`, which npm does not have; the documented alternative is to build from source with pnpm and point the client at `build/index.js`. The project's own guidance is worth following: use a dedicated wallet for agent operations, keep the key in environment variables rather than anywhere it will be read back, and exercise everything on devnet or testnet before pointing it at mainnet. MIT licensed.