Bonk

Provides Solana-based token launching and trading capabilities for LetsBonk launchpad via MCP.

other

0

GitHub Stars

other

Language

5 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "mcp-mirror-bjoernbonk_letsbonk_mcp_server": {
      "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"
      }
    }
  }
}

The bonk-mcp server adds Solana blockchain capabilities to the LetsBonk launchpad, enabling token launches and token trading on letsbonk.fun. This MCP server runs locally and communicates with a Solana RPC endpoint using your Solana keypair for authentication and signing. It is designed to be integrated with an MCP client through the MCP protocol, allowing you to manage token-related actions from your launcher UI.

How to use

You will connect an MCP client to the bonk-mcp server to perform token-related actions on LetsBonk. With this server you can initiate token launches and handle trades directly from your client interface. Start the MCP server in stdio mode and provide it with your Solana keypair and RPC endpoint. Your MCP client will relay requests such as launching a new token or trading existing tokens to the bonk-mcp server, which will execute them on the Solana network.

How to install

Prerequisites you need before setup: a modern operating system (macOS or Windows), a Solana keypair, and access to a Solana RPC endpoint.

Install Claude Desktop on your computer. This will enable you to manage MCP servers and their configurations.
Add bonk-mcp to your MCP servers configuration in Claude Desktop using one of the predefined configurations below.
Start Claude Desktop and ensure the bonk-mcp server is running. You will need your Solana KEYPAIR and the RPC URL you intend to use.

Configuration examples

"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"
    }
  }
}

Notes on published configurations

If you prefer a published configuration, use the following setup. This uses the uvx runtime to start the bonk-mcp server and passes the required environment variables.

"mcpServers": {
  "bonk-mcp": {
    "command": "uvx",
    "args": [
      "bonk-mcp"
    ],
    "env": {
      "KEYPAIR": "<YOUR_SOLANA_KEYPAIR>",
      "RPC_URL": "https://api.mainnet-beta.solana.com"
    }
  }
}

Troubleshooting and tips

If you encounter issues, verify that your Solana keypair is correctly configured and that the RPC endpoint is reachable. Check that Claude Desktop recognizes the bonk-mcp as a running MCP server and that the environment variables are correctly loaded. If debugging is difficult, consider using the MCP Inspector to connect to the stdio process for live debugging.

Security and best practices

Keep your Solana keypair secure and do not commit it to any code or configuration files. Use a dedicated keypair for development and restrict access to the machine running Claude Desktop. Regularly rotate keys and monitor RPC endpoints for unusual activity.

Miscellaneous notes

The bonk-mcp server focuses on token launching and trading capabilities within the LetsBonk ecosystem. Ensure you have the correct permissions and enough SOL in your wallet to cover any required transactions and rent exemptions on the Solana network.