Pump.fun MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRIVATE_KEY | No | Your base58-encoded private key for using an existing Solana wallet (optional) | |
| HELIUS_RPC_URL | Yes | Your Helius RPC URL for Solana blockchain access |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-token-infoC | Get information about a Pump.fun token |
| create-tokenC | Create a new Pump.fun token |
| buy-tokenC | Buy a Pump.fun token |
| sell-tokenC | Sell a Pump.fun token |
| list-accountsB | List all accounts in the keys folder |
| get-account-balanceC | Get the SOL and token balances for an account |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: buying, selling, and creating tokens are separate actions, while getting token info, account balances, and listing accounts are distinct read operations. The descriptions make it unambiguous which tool to use for each task.
The naming follows a consistent verb-noun pattern with hyphens (e.g., buy-token, create-token, get-token-info), except for 'list-accounts' which uses 'list' instead of 'get' like the other read operations. This minor deviation prevents a perfect score but maintains overall readability.
With 6 tools, this server is well-scoped for interacting with Pump.fun tokens and accounts. Each tool serves a clear purpose (e.g., core token lifecycle operations and account management), and none feel redundant or missing given the domain.
The toolset covers the essential token lifecycle (create, buy, sell, get info) and account management (balance, list), but lacks update or delete operations for tokens or accounts, which might be minor gaps depending on the platform's capabilities. Overall, it supports core workflows effectively.