GET_ASSETLABSCO SUMMARY
The network you configure decides what a mistake costs.
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.
What it is
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.
What you get
- Wallet basics —
WALLET_ADDRESSandBALANCE - Token movement and creation —
TRANSFER,DEPLOY_TOKEN,MINT_NFT - Market operations —
TRADEandGET_PRICE - Chain lookups —
GET_ASSETfor a token or asset,RESOLVE_DOMAINfor Solana domain names,GET_TPSfor current network throughput - Test funds on request, which is what makes devnet work practical —
REQUEST_FUNDS
Requirements
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.
Setup effort
Build from source — git clone https://github.com/PingAIFun/ping-mcp.git
USE CASES
01
Checking a wallet from the assistant window
Read the address and balance without opening a wallet app.
02
Trying agent-driven transactions safely
Point the RPC URL at devnet, request test funds, and let the agent transfer and trade with nothing real at stake.
03
Launching a token or an NFT from a conversation
Deploy the token or mint the NFT through the tools rather than assembling the transaction by hand.
04
Looking something up onchain
Resolve a Solana domain, fetch asset details or price, or check current network throughput before acting.
11 tools
Listed in project docs. Your client may show a different list.
DEPLOY_TOKENGET_PRICEWALLET_ADDRESSBALANCETRANSFERMINT_NFTTRADEREQUEST_FUNDSRESOLVE_DOMAINGET_TPSBEFORE YOU INSTALL
What to know first
Tools you get
11 tools named in the project's documentation.
Requires
- Node.js
- SOLANA_PRIVATE_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/PingAIFun/ping-mcp.git
cd ping-mcp
pnpm install
pnpm run buildMCP Clients
Claude Desktop — local build
CLAUDE DESKTOP — LOCAL BUILD · JSON
{
"mcpServers": {
"solana-mcp": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PING_MCP>/build/index.js"
],
"env": {
"RPC_URL": "<YOUR_RPC_URL>",
"SOLANA_PRIVATE_KEY": "<YOUR_SOLANA_PRIVATE_KEY>",
"OPENAI_API_KEY": "<YOUR_OPENAI_API_KEY>"
},
"disabled": false,
"autoApprove": []
}
}
}
