Navigation
PumpFun-MCP: Industrial Precision & Energy Efficiency - MCP Implementation

PumpFun-MCP: Industrial Precision & Energy Efficiency

PumpFun-MCP: Engineered for unmatched industrial reliability, blending cutting-edge precision with energy-smart efficiency. The ultimate solution for demanding fluid systems.

Developer Tools
4.2(190 reviews)
285 saves
133 comments

Ranked in the top 4% of all AI tools in its category

About PumpFun-MCP

What is PumpFun-MCP: Industrial Precision & Energy Efficiency?

PumpFun-MCP is a specialized Model Context Protocol (MCP) server designed to bridge AI assistants with the Pump.fun platform on the Solana blockchain. Its core purpose is to enable seamless creation, buying, and selling of tokens through industrial-grade precision and optimized energy efficiency. By integrating with AI tools like Claude, this server streamlines token lifecycle management while maintaining strict security standards.

Key differentiators include:

  • Direct Solana blockchain interaction via Helius RPC
  • Automated keypair management for multiple accounts
  • Parameterized transaction controls (slippage, account selection)

How to Use PumpFun-MCP: Industrial Precision & Energy Efficiency?

Configuration Steps

  1. Install dependencies and configure your Helius RPC URL
  2. Add your Solana private key to the .env file
  3. Generate keypairs using node convert-key.js
  4. Run the server: node build/index.js

Core Workflow Example

To create a token:

    
      create-token "MyToken" "MTK" "A sample token" 0.001 --image ./token.png
    
  

Buying/Selling follows similar patterns with address-based lookups:

    
      buy-token 3q2j...a1z 0.05 --account "trading-wallet"
    
  

PumpFun-MCP Features

Key Features of PumpFun-MCP: Industrial Precision & Energy Efficiency?

Transaction Precision

Granular control over:

  • Slippage tolerance (default 1%)
  • Atomic buy/sell execution
  • Multi-account management

Energy Optimization

Engineered for:

  • Batch transaction processing
  • Lazy image file handling
  • Reduced RPC query overhead

Security Framework

Includes:

  • Encrypted key storage workflows
  • Account balance validation checks
  • RPC URL whitelisting

Use Cases of PumpFun-MCP: Industrial Precision & Energy Efficiency?

Automated Market Making

Deploy bots for:

  • Dynamic token pricing
  • Arbitrage opportunities
  • Liquidity provision

Institutional Asset Management

Supports:

  • Multi-signature workflows
  • Compliance reporting via transaction logs
  • Portfolio diversification strategies

Development Testing

Facilitates:

  • Rapid token prototyping
  • Mock transaction simulations
  • API integration testing

PumpFun-MCP FAQ

FAQ from PumpFun-MCP: Industrial Precision & Energy Efficiency?

Security Best Practices

Q: How to secure the .keys folder?
A: Use encrypted volumes and restrict permissions to user-only access. Never store keys in version control.

Performance Tuning

Q: How to optimize RPC costs?
A: Implement caching for static token metadata and use get-account-balance sparingly.

Customization Options

Q: Can I add custom account types?
A: Yes, by modifying .keys folder permissions and updating accountName parameters in transactions.

Error Handling

Q: What if a transaction fails?
A: Check solana logs for transaction hashes. Use slippageBasisPoints adjustments for price deviations.

Content

pumpfun-mcp

A Model Context Protocol (MCP) server for interacting with the Pump.fun platform on Solana. This server enables AI assistants to create, buy, and sell tokens on the Pump.fun platform.

Pump.fun MCP Demo

Usage

https://github.com/user-attachments/assets/0b0f1f6f-6ea6-4ca8-92a8-b4cc895814e4

To use this server with Claude or other MCP-compatible AI assistants, add the following configuration to your MCP client:

If you're on MacOS and want to run this in Claude Desktop, in your ~/Library/Application \Support/Claude/claude_desktop_config.json file, write the following:

{
  "mcpServers": {
    "pumpfun": {
      "command": "node",
      "args": ["/Users/noahsolomon/Desktop/pumpfun-mcp/build/index.js"], // note this should be YOUR absolute path to index.js, not mine.
      "env": {
        "HELIUS_RPC_URL": "https://your-helius-rpc-url.com"
      }
    }
  }
}

Replace https://your-helius-rpc-url.com with your Helius RPC URL.

Installation

  1. Clone this repository:

    git clone https://github.com/noahgsolomon/pumpfun-mcp.git

cd pumpfun-mcp
  1. Install dependencies:

    npm install

  2. Create a .env file with your Solana RPC URL:

    HELIUS_RPC_URL=https://your-helius-rpc-url.com

You can get a free RPC URL from Helius.

To use an existing Solana wallet, add your private key to the .env file:

    PRIVATE_KEY=your-base58-encoded-private-key

Then run the conversion script to create a keypair file:

    node convert-key.js

This will create a default.json file in the .keys folder with your keypair.

  1. Build the project:

    npm run build

  2. Run the MCP server:

    node build/index.js

Components

Tools

  • get-token-info

    • Get information about a Pump.fun token
    • Input parameters:
      • tokenAddress (string, required): The token's mint address
  • create-token

    • Create a new Pump.fun token
    • Input parameters:
      • name (string, required): Token name
      • symbol (string, required): Token symbol
      • description (string, required): Token description
      • imageUrl (string, optional): Path to local image file
      • initialBuyAmount (number, required): Initial buy amount in SOL (min 0.0001)
      • accountName (string, optional): Name of the account to use (defaults to "default")
  • buy-token

    • Buy a Pump.fun token
    • Input parameters:
      • tokenAddress (string, required): The token's mint address
      • buyAmount (number, required): Amount to buy in SOL (min 0.0001)
      • accountName (string, optional): Name of the account to use (defaults to "default")
      • slippageBasisPoints (number, optional): Slippage tolerance in basis points (defaults to 100)
  • sell-token

    • Sell a Pump.fun token
    • Input parameters:
      • tokenAddress (string, required): The token's mint address
      • sellAmount (number, required): Amount of tokens to sell (use 0 to sell all)
      • accountName (string, optional): Name of the account to use (defaults to "default")
      • slippageBasisPoints (number, optional): Slippage tolerance in basis points (defaults to 100)
  • list-accounts

    • List all accounts in the keys folder
    • No input parameters required
  • get-account-balance

    • Get the SOL and token balances for an account
    • Input parameters:
      • accountName (string, optional): Name of the account to check (defaults to "default")
      • tokenAddress (string, optional): Token address to check balance for

Account Management

The MCP automatically creates and manages Solana keypairs in the .keys folder. Each keypair is stored as a JSON file with the account name as the filename.

When creating a token, the mint keypair is also saved in the .keys folder with the prefix mint-.

To use the MCP with your own account, you need to:

  1. Add your private key to the .env file and run node convert-key.js
  2. Have sufficient SOL in that wallet

Standalone Scripts

The project includes several standalone scripts that can be run directly:

  • Get Token Info : node build/get-token-info.js <token_address>
  • Create Token : node build/create-token.js <name> <symbol> <description> <initial_buy_amount> [account_name] [image_url]
  • Buy Token : node build/buy-token.js <token_address> <buy_amount_sol> [account_name] [slippage_basis_points]
  • Sell Token : node build/sell-token.js <token_address> <sell_amount> [account_name] [slippage_basis_points]
  • List Accounts : node build/list-accounts.js
  • Get Account Balance : node build/get-token-balance.js <account_name> [token_address]

Important Notes

  • Security : The keypairs are stored unencrypted in the .keys folder. Make sure to secure this folder appropriately.
  • Fees : All transactions on Solana require SOL for transaction fees. Make sure your accounts have enough SOL.
  • Slippage : The default slippage tolerance is 1% (100 basis points). You can adjust this for each transaction.
  • Images : When creating tokens with images, you must provide a local file path to the image. Remote URLs are not supported.

Development

Project Structure

  • src/index.ts: Main MCP server entry point
  • src/get-token-info.ts: Token information retrieval
  • src/create-token.ts: Token creation functionality
  • src/buy-token.ts: Token buying functionality
  • src/sell-token.ts: Token selling functionality
  • src/list-accounts.ts: Account listing functionality
  • src/get-token-balance.ts: Account balance checking
  • src/utils.ts: Shared utility functions
  • convert-key.js: Utility to convert a base58 private key to a keypair JSON file

Building

npm run build

Related MCP Servers & Clients