bonk-mcp 서버는 LetsBonk 런치패드를 위한 Solana 블록체인 기능을 구현합니다.
토큰 출시: letsbonk.fun에서 토큰을 출시하세요
토큰 거래: letsbonk.fun에서 모든 토큰을 사고팔 수 있습니다.
Related MCP server: Solana MCP Server
bonk-mcp 서버는 Claude Desktop의 MCP 서버 구성에 추가하여 구성할 수 있습니다. 다음 정보를 제공해야 합니다.
bonk-mcp 디렉토리 경로
환경 변수:
KEYPAIR : Solana 키페어
RPC_URL : Solana RPC 엔드포인트(예: https://api.mainnet-beta.solana.com )
MacOS의 경우: ~/Library/Application\ Support/Claude/claude_desktop_config.json Windows의 경우: %APPDATA%/Claude/claude_desktop_config.json
지엑스피1
"mcpServers": {
"bonk-mcp": {
"command": "uvx",
"args": [
"bonk-mcp"
],
"env": {
"KEYPAIR": "<YOUR_SOLANA_KEYPAIR>",
"RPC_URL": "https://api.mainnet-beta.solana.com"
}
}
}배포를 위해 패키지를 준비하려면:
종속성 동기화 및 잠금 파일 업데이트:
uv sync패키지 배포 빌드:
uv build이렇게 하면 dist/ 디렉토리에 소스와 휠 배포판이 생성됩니다.
PyPI에 게시:
uv publish참고: 환경 변수나 명령 플래그를 통해 PyPI 자격 증명을 설정해야 합니다.
토큰: --token 또는 UV_PUBLISH_TOKEN
또는 사용자 이름/비밀번호: --username / UV_PUBLISH_USERNAME 및 --password / UV_PUBLISH_PASSWORD
MCP 서버는 stdio를 통해 실행되므로 디버깅이 어려울 수 있습니다. 최상의 디버깅 환경을 위해서는 MCP Inspector 사용을 강력히 권장합니다.
다음 명령을 사용하여 npm 통해 MCP Inspector를 시작할 수 있습니다.
npx @modelcontextprotocol/inspector uv --directory <PATH_TO_BONK_MCP_DIRECTORY>/bonk-mcp run bonk-mcpInspector를 실행하면 브라우저에서 접근하여 디버깅을 시작할 수 있는 URL이 표시됩니다.
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.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0launch-tokenScored across 1 tool
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.
Non-custodial Solana toolkit: rug-checks, swaps, portfolios, token minting, multisig, Arweave.
Plan a Solana token launch
Launch Solana coins from your AI. You approve each launch in your wallet and earn creator fees.
Full Solana DeFi coverage: launchpads, tokens, trades, and wallets, decoded at scale.
