Raydium Launchlab MCP

What kukapay/raydium-launchlab-mcp MCP server does

The kukapay/raydium-launchlab-mcp MCP server exposes Raydium LaunchLab token operations to an AI agent through three tools: mint_token, buy_token, and sell_token. It is intended for Solana wallets and LaunchLab pools, so it fits workflows that need an agent to create a token or trade an existing LaunchLab token.

mint_token creates a bonding-curve-based token and accepts a name, symbol, logo path, decimal count, fundraising target, total supply, and the percentage of supply offered for fundraising. The tool can either create the token without buying or make an initial purchase as part of creation. buy_token spends SOL on tokens in a LaunchLab pool, while sell_token sells tokens back to that pool.

How it works

For token creation, the server uploads the supplied image and token metadata to IPFS through Pinata, then uses the configured Solana connection and wallet to perform the LaunchLab operation. Buy and sell requests identify the token with its mint address and specify the input amount. Each trading operation also accepts a slippage value; the documented default is 0.01, representing 1 percent.

The wallet must have enough SOL to cover the relevant transactions. The server returns mint information and transaction signatures for successful creation, purchases, and sales according to the README examples. The server does not describe market data, portfolio tracking, token discovery, or general Solana account management features.

Setup and configuration

The project requires Node.js 18 or newer. The documented setup is to clone the repository and run npm install in the project directory. An MCP client then starts the server with Node and the repository’s index.js file.

Configuration uses four environment variables:

• RPC_URL: Solana RPC endpoint used for blockchain requests.
• PRIVATE_KEY: Solana wallet private key represented as an integer array.
• PINATA_JWT: Pinata credential for IPFS uploads.
• PINATA_GATEWAY: Pinata gateway configuration used with uploaded content.

A Solana wallet with sufficient SOL and a Pinata account are prerequisites. The README does not provide a prebuilt package command or hosted endpoint, so deployment is based on the cloned source tree.

Tools and capabilities

• mint_token: Creates a LaunchLab token with configurable metadata and tokenomics parameters. The documented inputs include name, symbol, image path, decimals, fundraising target, total supply, total sell percentage, create-only mode, initial buy amount, and slippage.
• buy_token: Buys tokens using SOL. It requires a token mint address, a positive SOL amount, and optional slippage.
• sell_token: Sells tokens to a LaunchLab pool. It requires a token mint address, a positive token amount, and optional slippage.
• IPFS metadata handling: Sends token images and metadata to Pinata during token creation.

Limitations and notes

The kukapay/raydium-launchlab-mcp MCP server requires access to a funded Solana wallet and exposes operations that can submit blockchain transactions. Review amounts, mint addresses, and slippage before allowing an agent to call the trading tools.

The README documents image input as a filesystem path, but it does not specify supported image formats or size limits. It also does not identify specific MCP clients as officially supported. Pinata credentials are required for token creation because the project uses Pinata for IPFS storage. Trading tools still depend on a working Solana RPC endpoint and wallet configuration.