Mcp Broadcast
Let your coding agent submit already-signed raw transactions to supported chains through Crypto APIs without hand-wiring broadcast endpoints.
Overview
io.github.CryptoAPIs-io/mcp-broadcast is a Build-phase MCP server that broadcasts signed raw transactions to multiple blockchains through Crypto APIs.
What is this MCP server?
- Broadcasts signed raw transactions via Crypto APIs across multiple supported blockchains
- Stdio MCP package @cryptoapis-io/mcp-broadcast at server version 0.3.0
- Requires CRYPTOAPIS_API_KEY as the only documented secret env var
- Pairs with mcp-hd-wallet and mcp-contracts for end-to-end Web3 build flows
- MCP protocol server—not a local signer; you supply signed payloads off-agent or from your app
- Server schema version 0.3.0
- npm package @cryptoapis-io/mcp-broadcast with stdio transport
- 1 required secret environment variable: CRYPTOAPIS_API_KEY
What problem does it solve?
Shipping multi-chain send flows means juggling different broadcast endpoints and response formats instead of one agent-callable integration.
Who is it for?
Indie builders adding send, relay, or settlement paths to a crypto app who already sign transactions elsewhere and want hosted multi-chain broadcast.
Skip if: Builders who need local signing, key custody, or testnet-only offline tooling without a Crypto APIs subscription.
What do I get? / Deliverables
Your agent can submit signed raw transactions through Crypto APIs so you validate broadcast behavior while building without leaving the IDE.
- Agent-callable broadcast to supported chains via Crypto APIs
- Stdio MCP server wired into local agent config
- Repeatable send-path testing during backend or wallet feature work
Recommended MCP Servers
Journey fit
Transaction broadcast is an integration step while you wire wallet flows, backends, or agent tools—not a launch or growth tactic. It plugs a third-party blockchain RPC/broadcast API into the agent stack alongside contracts and wallet MCPs from the same vendor.
How it compares
Hosted broadcast MCP integration, not an in-repo signing skill or local node CLI.
Common Questions / FAQ
Who is mcp-broadcast for?
Solo and small-team developers wiring on-chain send or settlement into agents or backends and already using Crypto APIs for blockchain infrastructure.
When should I use mcp-broadcast?
Use it during Build when you have signed raw transactions ready and need to test or execute broadcast across supported networks via one API-backed MCP.
How do I add mcp-broadcast to my agent?
Register the npm stdio server @cryptoapis-io/mcp-broadcast in your MCP config, set CRYPTOAPIS_API_KEY, and point Claude Code, Cursor, or Codex at the server entry from the CryptoAPIs-io repo.