pump.fun Solana Data — Claude Code MCP server: on-chain token data
Read-only MCP server for pump.fun and Solana: token search, bonding curves, trades, holders, SNS names, 3D snapshots. No API key, RPC URL or wallet.
claude mcp add --env PUMPFUN_MCP_URL=<PUMPFUN_MCP_URL> --transport stdio pumpfun-mcp -- npx -y @three-ws/pumpfun-mcpWhat pump.fun Solana Data does
Ask your client what is moving on pump.fun and it picks the tool itself: token lookup, curve reserves and how close a coin is to graduating, recent trades, top holders, .sol resolution. Swap quoting stops at the number, and the vanity mint tool hands back a keypair for you to use. Nothing in the set signs or sends a transaction.
The client spawns the package with npx and speaks stdio JSON-RPC. Solana RPC and pump.fun API traffic is made on the three.ws backend, which is why no key, endpoint or wallet shows up in your config. Setting it up in Claude Code takes one terminal line.
Six tools need a pump.fun indexer pointed to by PUMPFUN_BOT_URL: search_tokens, get_trending_tokens, get_new_tokens, get_graduated_tokens, get_king_of_the_hill, get_creator_profile. The hosted three.ws/api/pump-fun-mcp endpoint runs without one, so it drops those six from tools/list rather than erroring. pumpfun_bot_status reports which mode you are on. Without an indexer, get_token_details returns SPL account fields and leaves name, symbol and uri as null.
What it helps with
- look up a token by ticker or mint address
- check how far a coin is from graduating the curve
- see who holds a coin and how it has traded
- resolve a
.solname to a wallet address - quote a swap without sending anything
Example prompts for the agent
- What is trending on pump.fun right now?
- Pull the bonding curve for
<mint>and tell me how close it is to graduating - Resolve
bonfida.solto a wallet address
How to install pump.fun Solana Data
Platform CLI
claude mcp add --env PUMPFUN_MCP_URL=<PUMPFUN_MCP_URL> --transport stdio pumpfun-mcp -- npx -y @three-ws/pumpfun-mcpReplace <…> with your own values
Platform CLI
codex mcp add pumpfun-mcp --env PUMPFUN_MCP_URL=<PUMPFUN_MCP_URL> -- npx -y @three-ws/pumpfun-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"pumpfun-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/pumpfun-mcp"
],
"env": {
"PUMPFUN_MCP_URL": "<PUMPFUN_MCP_URL>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"pumpfun-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@three-ws/pumpfun-mcp"
],
"env": {
"PUMPFUN_MCP_URL": "<PUMPFUN_MCP_URL>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e PUMPFUN_MCP_URL=<PUMPFUN_MCP_URL> pumpfun-mcp npx -y @three-ws/pumpfun-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about pump.fun Solana Data
How do I install pump.fun Solana Data in Claude Code?
Run claude mcp add pumpfun-solana-mcp -- npx -y @three-ws/pumpfun-mcp. The tools are available in that session, no separate install step.
What does pump.fun Solana Data actually do?
It gives the agent pump.fun and Solana data: token search, bonding-curve reserves, trades, holders, SNS names, swap quotes and 3D token snapshots. Every tool is read-only.
Do I need an API key or an RPC URL?
No. The server calls the three.ws backend server-side, so the client config carries no key, no RPC endpoint and no wallet.
