The bonk-mcp server enables Solana blockchain functionality for the LetsBonk launchpad. With this server, you can:
Launch new meme tokens on Solana through the Raydium launchpad, providing details like name, symbol, description, and image URL
Buy and sell tokens on the letsbonk.fun platform
Configure and integrate the server with Claude Desktop for development or production use
Implements Solana blockchain functionality for token launching and trading on the LetsBonk launchpad, allowing users to launch and trade any token on the platform.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@bonk-mcp MCP Server launch a new token called MoonCat with 1 billion supply"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
The bonk-mcp server implements Solana blockchain functionality for the LetsBonk launchpad.
Token launching: launch any token on letsbonk.fun
Token trading: buy/sell any token on letsbonk.fun
Related MCP server: Solana MCP Server
The bonk-mcp server can be configured in Claude Desktop by adding it to the MCP servers configuration. You'll need to provide:
Path to the bonk-mcp directory
Environment variables:
KEYPAIR: Your Solana keypair
RPC_URL: Solana RPC endpoint (e.g., https://api.mainnet-beta.solana.com)
On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
"mcpServers": {
"bonk-mcp": {
"command": "uv",
"args": [
"--directory",
"<PATH_TO_BONK_MCP_DIRECTORY>/bonk-mcp",
"run",
"bonk-mcp"
],
"env": {
"KEYPAIR": "<YOUR_SOLANA_KEYPAIR>",
"RPC_URL": "https://api.mainnet-beta.solana.com"
}
}
}"mcpServers": {
"bonk-mcp": {
"command": "uvx",
"args": [
"bonk-mcp"
],
"env": {
"KEYPAIR": "<YOUR_SOLANA_KEYPAIR>",
"RPC_URL": "https://api.mainnet-beta.solana.com"
}
}
}To prepare the package for distribution:
Sync dependencies and update lockfile:
uv syncBuild package distributions:
uv buildThis will create source and wheel distributions in the dist/ directory.
Publish to PyPI:
uv publishNote: You'll need to set PyPI credentials via environment variables or command flags:
Token: --token or UV_PUBLISH_TOKEN
Or username/password: --username/UV_PUBLISH_USERNAME and --password/UV_PUBLISH_PASSWORD
Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.
You can launch the MCP Inspector via npm with this command:
npx @modelcontextprotocol/inspector uv --directory <PATH_TO_BONK_MCP_DIRECTORY>/bonk-mcp run bonk-mcpUpon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
Launch a new meme token on Solana using Raydium launchpad
| Name | Required | Description | Default |
|---|---|---|---|
| description | Yes | Token description | |
| image_url | Yes | Image URL to use for token | |
| name | Yes | Token name | |
| symbol | Yes | Token symbol/ticker | |
| telegram | No | Telegram group URL (optional) | |
| No | Twitter handle/URL (optional) | ||
| website | No | Website URL (optional) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the action ('Launch') which implies a write/mutation operation, but fails to disclose critical behavioral traits such as required permissions, cost implications, irreversible effects, rate limits, or what the response looks like. This leaves significant gaps for an agent to understand the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded with the essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given this is a complex write operation (token launch) with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like permissions, costs, or response format, nor does it provide usage context. The 100% schema coverage helps with parameters, but overall context for safe and effective use is lacking.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description provides no parameter-specific information beyond what's already in the input schema, which has 100% coverage with clear descriptions for all 7 parameters. The baseline score of 3 reflects adequate schema documentation, but the description adds no additional semantic context about parameter usage or relationships.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Launch') and target resource ('new meme token on Solana using Raydium launchpad'), providing specific verb+resource. However, since there are no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, preventing a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It simply states what the tool does without context about appropriate scenarios or limitations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
With only one tool, there is no possibility of confusion or overlap between tools. The single tool has a clear and distinct purpose focused on launching meme tokens on Solana.
A single tool inherently has perfect naming consistency as there are no other tools to compare against. The name 'launch-token' follows a clear verb-noun pattern.
One tool is too few for a server with a domain like launching tokens, as it lacks essential operations like checking token status, managing launches, or handling transactions. This severely limits agent functionality.
The tool surface is severely incomplete; it only provides a launch function without supporting operations like querying token details, updating launches, or deleting/canceling tokens. This will cause frequent agent failures in real-world scenarios.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Non-custodial Solana toolkit: rug-checks, swaps, portfolios, token minting, multisig, Arweave.
Full Solana DeFi coverage: launchpads, tokens, trades, and wallets, decoded at scale.
Solana MCP for wallets, trades, markets, PnL, transfers, onchain data, signable swaps and API tools.
Solana tools over MCP: Jupiter swaps, SPL tokens, Metaplex NFTs, SNS domains, network stats.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/bjoernbonk/letsbonk_mcp_server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
