OpenPump MCP Server

Trade pump.fun tokens, manage Solana wallets, run market making bots, snipe new tokens, and monitor positions via MCP.

Setup

1. Get Your API Key

1. 1. Sign up at openpump.io
2. Go to Dashboard > API Keys
3. Create a new key (starts with op_sk_live_)

2. Set the Environment Variable

CODEBLOCK0

3. Add MCP Server

Claude Code (HTTP transport -- no local process):

CODEBLOCK1

Claude Desktop / any MCP client (stdio via npx):

CODEBLOCK2

HTTP transport (remote, no local process):

CODEBLOCK3

Available Tools (57)

Token Creation (2)

Tool	Description
INLINECODE1	Launch a new token on pump.fun with name, symbol, description, and image
INLINECODE2

Atomically create a token AND coordinate multi-wallet buys via Jito bundles |

Trading (7)

Tool	Description
INLINECODE3	Buy a pump.fun token with SOL (single wallet). amountSol is a decimal SOL string (e.g. "0.1")
INLINECODE6

Sell a token position back to SOL. Use tokenAmount: "all" for entire balance | | bundle-buy | Multi-wallet buy of an existing token via Jito bundles | | bundle-sell | Multi-wallet sell packed into Jito bundles (bonding curve tokens only) | | get-token-quote | Price quote for buy or sell without executing. solAmount in lamports string for buys | | estimate-bundle-cost | Preview total SOL required for a bundle launch before executing | | claim-creator-fees | Claim accumulated pump.fun creator fees for a wallet address |

Transfers (2)

Tool	Description
INLINECODE14	Send SOL to any Solana address. amountSol is decimal SOL string. 10 SOL cap per call. Supports INLINECODE16
INLINECODE17

Send SPL tokens to any Solana address. tokenAmount in raw base units or "all" |

Wallet Management (5)

Tool	Description
INLINECODE20	Create a new HD-derived custodial wallet with optional label
INLINECODE21

Create 2-50 wallets in one action with auto-numbered labels | | get-aggregate-balance | Sum SOL across all user wallets | | get-wallet-deposit-address | Get deposit address and funding instructions for a wallet | | get-wallet-transactions | Paginated transfer history (buy/sell/transfer) for a wallet |

Market Making (13)

Tool	Description
INLINECODE25	Create a wallet pool with N wallets grouped under a label (2-50 wallets)
INLINECODE26

List all wallet pools for the user | | mm-pool-status | Aggregate status: per-wallet SOL and token balances, totals | | mm-fund-pool | Distribute SOL from source wallet to all pool wallets. Supports multi-hop obfuscation (hops 0-3) | | mm-consolidate-pool | Sweep all funds from pool wallets back to a single target wallet | | mm-start-session | Start autonomous market making on a token with configurable strategy | | mm-stop-session | Stop a running session. Positions are NOT auto-liquidated | | mm-pause-session | Pause a session (retains position and config) | | mm-resume-session | Resume a paused session from where it left off | | mm-session-status | Detailed session stats: config, live data, recent trades | | mm-list-sessions | List all sessions, optionally filter by status | | mm-update-strategy | Hot-update strategy params on a running/paused session | | mm-get-pnl | P&L report: WAC cost basis, realized/unrealized P&L, slippage-adjusted sell simulation, ROI% |

Sniping (7)

Tool	Description
INLINECODE38	Create a monitor that auto-buys new tokens matching criteria (ticker pattern, market cap, risk filters)
INLINECODE39

Stop a snipe monitor permanently | | snipe-pause | Pause a snipe monitor (resume later) | | snipe-resume | Resume a paused snipe monitor | | snipe-update | Update criteria on an active or paused monitor | | snipe-status | Detailed status including criteria, buy count, state | | snipe-list | List all snipe monitors, optionally filter by status |

Stop Loss (4)

Tool	Description
INLINECODE45	Create a stop-loss monitor. Auto-sells when market cap drops below trigger
INLINECODE46

Remove a stop-loss monitor | | stop-loss-list | List all stop-loss monitors | | stop-loss-status | Detailed status of a specific stop-loss |

Vanity Addresses (4)

Tool	Description
INLINECODE49	Estimate credits for a vanity pattern before ordering
INLINECODE50

Order a vanity wallet or mint address (prefix, suffix, or contains) | | list-vanity-jobs | List vanity mining jobs (newest first) | | get-vanity-job | Check status of a specific vanity job. Wallet auto-added on completion |

Spam Launch (3)

Tool	Description
INLINECODE53	Create multiple tokens in rapid succession from one wallet (1-100)
INLINECODE54

Estimate total SOL and credits for a spam launch | | cancel-spam-launch | Cancel a running spam launch job |

Information (9)

Tool	Description
INLINECODE56	Bonding curve state: price, market cap, graduation status
INLINECODE57

Rich analytics: volume, buy/sell counts, risk metrics (snipers, bundlers, insiders) | | list-my-tokens | All tokens launched by the authenticated user | | get-token-holdings | Which wallets hold a specific token. Omit mint to see ALL holdings | | get-wallet-balance | Live SOL + token balances for a single wallet | | list-wallets | All wallets with public keys, labels, derivation index | | get-creator-fees | Check accumulated pump.fun creator fees. Omit address to check all wallets | | get-jito-tip-levels | Current Jito MEV tip amounts per priority level (refreshed every 20s) |

Job Management (2)

Tool	Description
INLINECODE64	Check status of async operations. Poll every 2s until "completed" or "failed"
INLINECODE65

Cancel a running async job |

Workflows

1. Launch a Token

CODEBLOCK4

2. Bundle Launch (Create + Multi-Wallet Buy)

CODEBLOCK5

3. Buy and Sell Flow

CODEBLOCK6

4. Market Making

CODEBLOCK7

5. Sniping New Tokens

CODEBLOCK8

6. Stop Loss Protection

CODEBLOCK9

7. Check Portfolio

CODEBLOCK10

8. Claim Creator Fees

CODEBLOCK11

9. Transfer SOL Out

CODEBLOCK12

10. Vanity Address

CODEBLOCK13

Safety Guardrails

All trading actions require explicit user confirmation before execution.

1. 1. Always check balances first. Run get-wallet-balance or get-aggregate-balance before any trade or transfer.

1. 2. Use quotes before trading. Call get-token-quote to preview expected output and price impact.

1. 3. Confirm large trades explicitly. Bundle operations, MM sessions, and snipe monitors all require confirm: true. Review parameters first.

1. 4. Verify addresses on transfers. Double-check destination addresses. Transfers are irreversible on Solana.

1. 5. Use dryRun for transfers. Both transfer-sol and transfer-token support dryRun: true.

1. 6. Check risk metrics. Use get-token-market-info to check sniper count, bundler activity, and insider percentage before buying.

1. 7. Set stop-losses. Use stop-loss-set to protect positions from sudden drops.

1. 8. Bundle slippage. bundle-launch packs multiple wallets per TX. Use 2500+ bps slippage (25%) for bundles, not the default 500 bps.

1. 9. MM drawdown. Market making sessions have a maxDrawdownPercent circuit breaker (default 15%). Session auto-stops if losses exceed this.

1. 10. Transfer cap. transfer-sol has a 10 SOL cap per call. Split larger amounts into multiple calls.

1. 11. Monitor async ops. After create-token, bundle-launch, or spam-launch, poll every 2 seconds. Jobs expire after 10 minutes.

Key Concepts

• - SOL amounts: amountSol params accept decimal SOL strings ("0.1" = 0.1 SOL). NOT lamports.
• Lamports: Some params (get-token-quote solAmount, mm-start-session amountRange) use lamports as integer strings (1 SOL = 1,000,000,000).
• Token base units: Token amounts use raw base units. Use the exact "amount" string from get-token-holdings.
• Custodial wallets: HD-derived, managed by the platform. Cannot import external keys.
• Bonding curve: pump.fun tokens trade on a bonding curve until graduation to PumpSwap. bundle-sell only works on bonding curve tokens.
• Jito bundles: Atomic, same-block execution. First bundle is guaranteed atomic; overflow wallets go into subsequent bundles.
• Wallet pools: Groups of wallets for market making. Multi-hop funding breaks on-chain clustering.

Links

• - Website: openpump.io
• npm: @openpump/mcp