@three-ws/pumpfun-mcp

Free, read-only pump.fun + Solana MCP server — token discovery, on-chain analysis, and live 3D snapshots. No API keys.

Install · Quick start · Tools · Configuration · three.ws

A free, read-only Model Context Protocol server for pump.fun and Solana. It gives Claude — or any MCP client — live token discovery, on-chain bonding-curve and holder analysis, creator fee-claim tracking, Solana Name Service resolution, KOL signals, read-only swap quotes, and shareable live 3D token snapshots. Every Solana RPC and pump.fun API call runs server-side on the canonical three.ws backend, so the data is live and on-chain while the client stays zero-config: no API keys, no RPC URL, no wallet.

Install

Claude Code (one-liner)

claude mcp add pumpfun -- npx -y @three-ws/pumpfun-mcp

Claude Desktop / Cursor / any MCP client

Add to your MCP config (claude_desktop_config.json, .cursor/mcp.json, .mcp.json, etc.):

{
	"mcpServers": {
		"pumpfun": {
			"command": "npx",
			"args": ["-y", "@three-ws/pumpfun-mcp"]
		}
	}
}

Restart the client and the pump.fun tools appear. No install step required.

Run directly

npx -y @three-ws/pumpfun-mcp
# or install globally and run the bin
npm i -g @three-ws/pumpfun-mcp && pumpfun-mcp

Quick start

The server speaks stdio JSON-RPC — your MCP client spawns it via the npx command above. Once configured, ask your client natural-language questions and it picks the right tool:

"What's trending on pump.fun right now?"        → get_trending_tokens
"Show the bonding curve for <mint>"             → get_bonding_curve
"Who are the top holders of <mint>?"            → get_token_holders
"Resolve bonfida.sol"                           → sns_resolve
"Build a 3D snapshot for <mint>"                → pumpfun_token_3d

Tools

All tools are read-only — nothing signs or sends a transaction. pumpfun_quote_swap only quotes; pumpfun_vanity_mint returns a keypair for you to use yourself.

Six tools are indexer-gated. search_tokens, get_trending_tokens, get_new_tokens, get_graduated_tokens, get_king_of_the_hill, and get_creator_profile need a pump.fun indexer (PUMPFUN_BOT_URL). The hosted endpoint at three.ws/api/pump-fun-mcp has none configured, so it filters those six out of tools/list and they will not appear when you connect to it; set the env var on your own deployment and they return with no code change. Everything else, including get_token_trades, works off on-chain data with no indexer. Call pumpfun_bot_status to see which side you are on. Note that without the indexer get_token_details returns SPL account facts only (name, symbol, and uri come back null).

The hosted endpoint also serves three tools the table below does not list: get_coin_intel, get_oracle_conviction, and pumpfun_upload_metadata.

The live tool list is fetched from the backend at startup; a bundled copy ships as an offline fallback so a fresh install always advertises a correct surface.

Inspect the tools

npx -y @modelcontextprotocol/inspector npx @three-ws/pumpfun-mcp

Examples

Runnable examples live in examples/:

node examples/list-tools.mjs     # every tool the backend currently serves, with schemas
node examples/token-report.mjs   # live on-chain report for one mint

Both spawn this server over stdio and read live Solana mainnet data. Every tool here is free and read-only. See examples/README.md for expected output, including why the advertised tool count depends on whether the backend has an indexer configured.

Configuration

No configuration is required. One optional override exists:

How it works

This package is a small stdio ↔ HTTP bridge. It forwards MCP tools/call requests to the canonical three.ws pump.fun JSON-RPC backend, which performs the actual Solana RPC reads and pump.fun API queries. That keeps one authoritative implementation, ships no secrets to clients, and means the tool surface stays current automatically.

pumpfun_token_3d is a native tool: it runs in-process, orchestrating several backend reads (metadata + bonding curve + holders) and resolving the token logo from its on-chain metadata URI, then returns a deep-link into the three.ws 3D viewer. It needs no extra keys and adds no new backend dependency.

Errors

Failures surface as MCP tool errors (isError: true) with the real cause — never a silent empty result:

pumpfun_token_3d degrades gracefully: if only some of its three source reads succeed it still returns a snapshot, marking the missing parts (no holder data available, no bonding-curve data available) — it errors only when all three fail.

Requirements

• Node.js >= 20 (from engines).
• No API keys, RPC URL, or wallet. Outbound HTTPS to the three.ws backend (or your PUMPFUN_MCP_URL).

Related

• @three-ws/mcp-server — the paid, x402-settled three.ws MCP (text→3D mesh, avatars, pose seeds, ERC-8004 reputation, and a paid pump_snapshot).

Links

• Homepage: https://three.ws
• Changelog: https://three.ws/changelog
• Issues: https://github.com/nirholas/three.ws/issues
• License: Apache-2.0. See LICENSE.

_{Part of the three.ws SDK suite — 3D AI agents, on-chain identity, and agent payments.
Website · Changelog · GitHub}