beeper-mcp

What is beeper-mcp?

A backend service for executing beeper transactions on Binance Smart Chain (BSC). It provides tools for interacting with the BSC blockchain, including balance checking, balance transfers, token transfers, token swaps in Pancakeswap, and beeper reward claims. It is intended for developers and users who need programmatic access to BSC operations using the Model Context Protocol.

How to use beeper-mcp?

Clone the repository, set up a .env file with BEEPER_CHAIN, BEEPER_ACCOUNT, BEEPER_SECRET_KEY, and optionally BEEPER_TARGET_TOKEN, then run uv run src/beeper_mcp/server.py over stdio or with --transport=sse on a configurable port (default 8000). Configure it in Claude, Windsurf, Cursor, or Cline using the MCP server JSON block with the same environment variables.

Key features of beeper-mcp

• Get BNB and token balances from any address
• Transfer BNB and tokens to a recipient
• Swap tokens via Pancakeswap
• Fetch token prices in BNB
• Buy and sell tokens using BNB
• Claim beeper token rewards
• Manage default wallet and token addresses

Use cases of beeper-mcp

• Check BNB and token balances of a wallet address
• Send BNB or tokens to another address programmatically
• Execute token swaps on Pancakeswap within an automated workflow
• Claim accumulated beeper rewards for a given token
• Buy or sell tokens directly from a wallet balance

FAQ from beeper-mcp

What environment variables are required?

BEEPER_CHAIN (bsc or bsc-testnet), BEEPER_ACCOUNT (wallet address), and BEEPER_SECRET_KEY (private key) are required. BEEPER_TARGET_TOKEN (default token address) is optional.

What blockchain does beeper-mcp support?

It supports both BSC mainnet and BSC testnet, selected via the BEEPER_CHAIN environment variable.

What units are amounts specified in?

All amounts are in native units, e.g., BNB for the native coin and the token's smallest unit for tokens.

Do I need BNB for gas fees?

Yes, the wallet must have sufficient BNB to pay gas fees for all transactions.

What transport options are available?

The service can be run over stdio (default) or over SSE (Server-Sent Events) using the --transport=sse flag, with a configurable port (default 8000).