Bsc Multisend MCP Server

An MCP server that enables agents to perform bulk BNB and BEP20 token transfers on BSC.

Local serverstdio

What is the Bsc Multisend MCP MCP server?

Most developer tooling work still happens through a UI a human drives. Bsc Multisend MCP MCP server moves it into the conversation instead. An MCP server that enables agents to perform bulk BNB and BEP20 token transfers on BSC.

The short version

  • distributeNative Tool — Sends BNB to multiple addresses in a single transaction
  • receivers: Array of BSC addresses to receive BNB
  • amounts: Array of BNB amounts (e.g., 0.1 BNB) to send, automatically summed for the total
  • Automatically converts amounts to wei and handles gas estimation
  • distributeToken Tool — Sends BEP20 tokens to multiple addresses
  • tokenAddress: Address of the BEP20 token contract

The tools it exposes

The server publishes 2 tools. What each one is for:

  • distributeNative — Example Prompt: I want to send 0.1 BNB to 0xRecipient1 and 0.2 BNB to 0xRecipient2 on BSC. Expected Response: BNB distribution successful. Tx Hash
  • distributeToken — Example Prompt: Send tokens to the following addresses on BSC using the token contract at 0xTokenAddress: - 0xRecipient1: 100.5 tokens -

What it needs from you

Configuration is passed through the environment: PRIVATE_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js: Version 18 or higher. - pnpm: For installing dependencies. - BNB Smart Chain Wallet: A wallet with sufficient BNB for gas and tokens for distribution. - BSC RPC Endpoint: Access to a BSC node (e.g., https://bsc-dataseed.binance.org/).

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Bsc Multisend MCP's toolset — distributeNative, distributeToken — is a fair guide to whether it matches your workflow. It is maintained by kukapay; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
distributeNativeExample Prompt: I want to send 0.1 BNB to 0xRecipient1 and 0.2 BNB to 0xRecipient2 on BSC. Expected Response: BNB distribution successful. Tx Hash: 0x...
distributeTokenExample Prompt: Send tokens to the following addresses on BSC using the token contract at 0xTokenAddress: - 0xRecipient1: 100.5 tokens - 0xRecipient2: 200 tokens - 0xRecipient3: 50.75 tokens - 0xRecipient4: 150 tokens -

How to install the Bsc Multisend MCP MCP server

{
       "mcpServers": {
           "BSC MultiSend": {
               "command": "node",
               "args": [ "/path/to/bsc-multisend-mcp/index.js" ],
               "env": { "PRIVATE_KEY": "your-private-key" }               
           }
       }
    }

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js: Version 18 or higher. - pnpm: For installing dependencies. - BNB Smart Chain Wallet: A wallet with sufficient BNB for gas and tokens for distribution. - BSC RPC Endpoint: Access to a BSC node (e.g., https://bsc-dataseed.binance.org/).
VariableDescriptionRequired
PRIVATE_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Bsc Multisend MCP to distributeNative.
  • Use Bsc Multisend MCP to distributeToken.

Frequently asked questions

It connects Bsc Multisend MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (distributeNative, distributeToken) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Bsc Multisend MCP directly.