Bonker speaks MCP, so you can point an AI agent at the launchpad and let it do the tedious part. Connect it once:
claude mcp add --transport http bonker https://bonker.wtf/api/mcp
Any MCP client works — the raw config is a one-liner:
{
"mcpServers": {
"bonker": { "type": "http", "url": "https://bonker.wtf/api/mcp" }
}
}What your agent gets
| prepare_launch | Validates a launch and hands back unsigned deployToken calldata plus a preview of exactly what ships |
| upload_image | Stores a token image and returns a permanent bonker.wtf URL |
| launch_token | Turns a prepared launch into wallet-submit instructions |
| get_launch_status | prepared → awaiting_signature → submitted → confirmed → indexed, or failed |
| resolve_token | Finds a token by address, tx hash, ticker, or launch id |
| get_new_tokens | Recent launches, paginated |
| inspect_creator_rewards | A wallet’s LP fee shares and claimable WETH |
Letting an agent launch for you
By default the agent prepares a launch and you sign it. If you would rather it deploy on its own, generate an API key in your account and give it to your MCP client:
{
"mcpServers": {
"bonker": {
"type": "http",
"url": "https://bonker.wtf/api/mcp",
"headers": { "Authorization": "Bearer bnk_mcp_…" }
}
}
}To generate one you need a connected wallet plus any two of X, Telegram, or Farcaster linked to it. Bonker pays the gas for these launches, so the bar exists to keep that from being farmed — a wallet on its own is free to create and proves nothing.
- You don't pass a wallet address at all — the key already knows which wallet is yours
- The token is always credited to your wallet — the key is bound to it, and a launch prepared for a different address is refused rather than quietly redirected
- One launch per wallet per day
- Up to 5 keys at a time; revoke any of them whenever you like
- The key is shown once and stored only as a hash — if you lose it, revoke it and make another
Splitting the fees with someone
LP fees don't have to all go to one wallet. Pass rewardRecipients to prepare_launch and split them however you like — the classic move is keeping 95% and throwing 5% to whoever hyped your coin into existence:
"rewardRecipients": [
{ "address": "0xYou…", "bps": 9500 },
{ "address": "0xHypeman…", "bps": 500 }
]bps is basis points — 10000 is 100%, 500 is 5% — and they must add up to exactly 10000. Up to 8 wallets. This is written on-chain when the token deploys and is permanent, so check the preview before you sign.
Two extra rules apply when you let the agent deploy with your API key, because Bonker is paying the gas for that one:
- Your wallet keeps at least 50%. Split the rest however you want.
- Leave out
admin. Everyone controls their own slot, so a cut you hand out is a cut you can't quietly take back later. That's the point — your hypeman can see it's real.
Neither applies when you sign the transaction yourself. prepare_launch tells you which mode a split works in before you commit to anything.
It cannot spend your money
The server holds no keys and signs nothing. prepare_launch hands back an unsigned transaction — your wallet is the only thing that can broadcast it. No Bonker tool ever asks for a private key or a seed phrase, so if anything claiming to be Bonker does, it isn't.
It also won't tell you a launch worked before the chain agrees. get_launch_status re-reads the receipt on every call: submitted only means a hash exists, confirmed means the token is live, and indexed means it's showing up here too. If Base is unreachable it says so rather than guessing.
Details
- Base mainnet only (chain 8453) — there is no testnet deployment
- Read tools and launch preparation are public, no key needed
- 60 requests per minute, and 30 image uploads per minute
- Health check: /api/mcp/health