Model Context Protocol
Beacons surfaces as MCP tools any agent can call.
The bcn-mcp server exposes every Beacons operation as a Model Context Protocol tool. Claude, Anthropic Agent SDK, OpenAI agents, custom Forge agents — anything MCP-fluent can list fleets, enroll peers, query audit, and order SIMs without a wrapper.
Available tools
beacons.fleet.list— list fleets the session can seebeacons.fleet.create— create a fleet from a governance manifestbeacons.peer.enroll— enroll a peer (the composite verdict runs)beacons.peer.revoke— revoke a peer with a reasonbeacons.policy.recompute— force recomputationbeacons.audit.tail— stream audit eventsbeacons.audit.verify— verify a chain root against Sigilbeacons.cellular.order— order SIMs from any wired providerbeacons.cellular.usage— usage report for a SIM or fleetbeacons.transport.negotiate— switch a peer's transport
Scope inheritance
The MCP server binds to the same Arsenal capability your CLI uses. An agent calling beacons.fleet.create can only create a fleet if its ACT scopes the operation. Stolen tool calls cannot escalate beyond the bounded capability.
Install
# Claude Desktop / Code claude mcp add beacons -- bcn mcp serve # Other MCP hosts bcn mcp serve --transport stdio bcn mcp serve --transport http --port 4870