Batching a payout into one transaction is the whole value: one gas cost, one hash, and no loop for an agent to get half-right. The token path also covers the parts people forget — decimals, allowance, and the approval when the allowance is short. The setup to weigh is the shape of the credential: a private key sits in the client config, and everything that key can spend is in scope.
An MCP server with two tools for paying many addresses at once on BNB Smart Chain. One sends native BNB, the other a BEP20 token; both take a list of receivers and a matching list of amounts and put them through one transaction.
- Send BNB to many addresses in a single transaction — `receivers` and `amounts` go in, the total is summed for you, amounts are converted to wei and gas is estimated — the `distributeNative` tool
- Send a BEP20 token to many addresses — add `tokenAddress`, and the server queries the token's decimals, checks the allowance and approves the contract when it needs to — the `distributeToken` tool
- A transaction hash back on success, so the send can be checked on-chain
Node.js version 18 or higher, `pnpm` for dependencies, and access to a BSC RPC endpoint such as `https://bsc-dataseed.binance.org/`. Clone the repository and point the client's `command` at `node` with `/path/to/bsc-multisend-mcp/index.js`. The wallet's private key goes in the client config as `PRIVATE_KEY`, and that wallet needs BNB for gas plus whatever it is distributing — that key signs every transfer this server makes.