Beeper MCP

What intentos-labs/beeper-mcp MCP server does

The intentos-labs/beeper-mcp MCP server connects an MCP client to transaction operations on Binance Smart Chain. It supports both BSC mainnet and BSC testnet, with the active network selected through configuration. The service works with a configured wallet account and private key, and can optionally use a default token address.

Supported workflows include reading BNB and token balances, sending BNB or tokens, retrieving token prices in BNB, swapping tokens through PancakeSwap, buying tokens with BNB, selling tokens for BNB, and claiming Beeper token rewards. Transaction responses include status information and transaction hashes according to the project notes.

How it works

The server exposes MCP tools that an agent can call in a chat-based client. Wallet and token settings can be read or updated through tools for the default wallet and default token address. Balance tools accept an address, while transfer and trading tools accept recipient, token, and amount parameters as appropriate.

Amounts are expressed in native units such as BNB or the relevant token. Token and wallet addresses must be supplied in the expected format. Transactions require enough BNB to cover network gas fees. The service can run over stdio for local MCP client integration or over SSE, with SSE using port 8000 by default unless another port is supplied.

Setup and configuration

The intentos-labs/beeper-mcp MCP server requires Python 3.10 or newer, access to BSC mainnet or testnet, and a wallet account with its private key. Configuration can be placed in a .env file at the project root or supplied through the MCP client's environment configuration.

Required settings are:

• BEEPER_CHAIN: bsc or bsc-testnet
• BEEPER_ACCOUNT: the wallet address
• BEEPER_SECRET_KEY: the wallet's private key

BEEPER_TARGET_TOKEN is optional and sets the default token address. After cloning the repository, the documented stdio command is uv run src/beeper_mcp/server.py. SSE can be started with uv run src/beeper_mcp/server.py --port 8008 --transport=sse, or another selected port.

The README lists Claude Desktop, Windsurf, Cursor, and Cline as client configuration targets. The example configuration runs the server with uv, points it at the local project directory, and passes the wallet settings as environment variables.

Tools and capabilities

The intentos-labs/beeper-mcp MCP server lists these tool groups:

• Wallet and token management: read the default wallet, read the default token, and change the default token address.
• Balances: retrieve BNB or a specified token balance for an address.
• Transfers: send BNB or a specified token to a recipient, with a documented default amount of 0.01.
• Trading: swap tokens, get a token's price in BNB, buy with BNB, or sell for BNB.
• Rewards: claim rewards for a token.

The trading and transfer tools use decimal amount parameters where applicable. The exact result type varies by operation, with transfers and trading actions returning response objects.

Limitations and notes

This server is limited to the BSC networks and operations described in its tool list. It does not remove the need for a funded wallet, valid addresses, or gas funds. Supplying a private key gives the service transaction-signing capability, so the key should be handled through protected configuration. The README does not state a software license or provide a packaged installation command; setup is described from a cloned source checkout using uv.