beeper-mcp

Name: beeper-mcp
Author: unibaseio

@unibaseio

リポジトリ

beeper-mcp について

A backend service for executing beeper transactions on Binance Smart Chain

基本情報

カテゴリ

その他

ランタイム

python

トランスポート

stdio

公開者

unibaseio

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "beeper-mcp-unibaseio": {
      "command": "uv",
      "args": [
        "run",
        "src/beeper_mcp/server.py"
      ]
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is beeper-mcp?

beeper-mcp is a backend service that executes beeper transactions on Binance Smart Chain (BSC). It provides a set of MCP tools for interacting with the BSC blockchain, including balance checking, transfers, token swaps on PancakeSwap, and beeper reward claims. It is built for developers using MCP-compatible clients (Claude, Windsurf, Cursor, Cline).

How to use beeper-mcp?

Clone the repository, set required environment variables (MEMBASE_CHAIN, MEMBASE_ACCOUNT, MEMBASE_SECRET_KEY, and optionally MEMBASE_TARGET_TOKEN), then run the server over stdio with uv run src/beeper_mcp/server.py or over SSE on port 8000 (configurable with --port). Configure the server in your MCP client by providing the command, arguments, and environment variables as shown in the README.

Key features of beeper-mcp

Get BNB and token balances
Transfer BNB and tokens
Swap tokens in PancakeSwap
Get token prices in BNB
Buy and sell tokens
Claim beeper token rewards
Manage default wallet and token addresses

Use cases of beeper-mcp

Check wallet or token balances before transactions
Execute token swaps on PancakeSwap
Transfer native BNB or tokens to other addresses
Claim accumulated beeper rewards
Automate trading operations via an MCP client

FAQ from beeper-mcp

What are the runtime requirements?

Python >=3.10, access to a BSC network (mainnet or testnet), and a wallet account with its private key.

How do I configure the server?

Set the environment variables MEMBASE_CHAIN, MEMBASE_ACCOUNT, MEMBASE_SECRET_KEY, and optionally MEMBASE_TARGET_TOKEN either in a .env file or directly in the MCP client configuration.