OSS Minymaton (event-driven MCP message bus for AI agents, bundled SQLite) A new open-source project called minymaton provides a durable MCP message bus that lets coding agents including Copilot CLI, Claude Code, Codex, agy and Grok coordinate across sessions and machines through a shared inbox. Messages commit to bundled SQLite storage before publish returns, each subscription keeps its own progress across server restarts, and unacknowledged batches stay pending until the recipient acknowledges handling them; the public server runs as one SQLite-backed process with a loopback-only listener, and a single message must fit in a 16 KiB receive result. The project positions itself against Agent2Agent (A2A) by plugging into existing coding sessions via an MCP endpoint rather than requiring a per-agent service, though waking an idle session still needs minymaton-wait and a harness that reports background-command completion. A shared inbox for coding agents, across sessions and machines. Try it live 24h private channel https://cp.scritty.dev/minymaton-try/ | crates.io https://crates.io/crates/minymaton | Quick start quick-start | Mobile app mobile-app-android--ios | Deployment guide https://github.com/immutlex-dev/minymaton/blob/main/deploy/README.md You're the message bus between your coding agents. One changes an API, another is updating its callers, and a third is running tests on another machine. You copy the warnings, relay the failures and bring each session up to speed. Keeping them coordinated becomes a job of its own: monitoring progress, playing telephone between models and catching everyone up as the work changes. minymaton lets the agents you already use coordinate through a durable MCP message bus. Connect Copilot CLI, Claude Code, Codex, agy or Grok which-clients-work to the same server. Agents can broadcast to a stream or address one recipient, across machines and operating systems, without sharing a checkout or running a server for each agent. A handoff can look like this: php Claude - agents: "Auth now requires tenant id. Update callers before merging." Codex - Claude: "Updating callers. Send the regression test when it's ready." CI - agents: "Linux and Windows builds passed." Messages commit to durable storage before publish returns bundled SQLite in the public distribution . Each subscription keeps its own progress across server restarts, and a batch stays pending until its recipient acknowledges handling it. Pending messages reach the model through tool results or refreshed tool descriptions; a parked receive wakes on a committed message, without polling. The floor. The public server is one SQLite-backed process with a loopback-only listener remote access needs an SSH tunnel or authenticated HTTPS proxy . Tool-list delivery needs refresh support; Codex needs a fresh resumed turn, and Muse doesn't refresh it still wakes through minymaton-wait . Waking an idle session needs minymaton-wait and a harness that reports background-command completion; MCP alone cannot do it. Interactive Codex doesn't report it, so Codex waits inside an open turn. One message must fit in a 16 KiB receive result. Four native clients coordinate one reporting job. Codex wins the claim; all four run sqlite3 and duckdb , matching 12 rows / 36,000 total cents . minymaton-sqlite-duckdb-brian-omni.mp4 Agent2Agent A2A https://a2a-protocol.org/latest/specification/ standardizes communication between agent services: capability discovery, conversations, delegated tasks and artifacts. Connecting those services to an existing coding session still needs an A2A integration or bridge. minymaton's advantage here is the path into the coding agents you already run. Add an MCP endpoint to each client. The bus supplies the inbox, subscription progress, acknowledgments and delivery path into supported sessions. | What you need | minymaton | A2A | |---|---|---| | Connect existing coding sessions | MCP tools and the qualified client paths below; no per-agent service | An A2A-capable service or integration that connects the protocol to each session | | Send updates to a group or one agent | Streams, broadcast and direct addressing, with independent subscription progress | Messages between clients and remote agents; group routing belongs in the integration | | Keep unread messages across restarts | Bundled SQLite, explicit ACK-after-handling and redelivery of unacknowledged batches | Task retrieval and history; unread inbox persistence and handling acknowledgments depend on the implementation | | Reach a busy or idle model | Tool results or refreshed descriptions; background waiter for supported idle harnesses | Streaming or webhook updates reach the A2A client; feeding them into a coding session needs integration | | Discover capabilities, delegate tasks and exchange artifacts | Coordination policy stays in the agents; no Agent Cards or task lifecycle API | Standard Agent Cards, task states and artifact exchange | A2A already supports streaming and asynchronous push notifications https://a2a-protocol.org/latest/topics/streaming-and-async/ ; it does not require polling. Choose minymaton for a ready-made coordination bus between existing MCP coding clients. Choose A2A for interoperable agent services with capability discovery and task lifecycles. The two can coexist, but this server does not implement A2A. Four base tools: stream , subscription , publish , receive . One standalone native Rust waiter minymaton-wait , built for 6 targets and one portable Python 3 stdlib waiter tools/minymaton-wait.py bridge a parked receive to background-job completion. Task boards, squads, file reservations and review workflows stay outside the bus; optional tool-list delivery adds the batch tools described below. A standalone Android and iOS app mobile/ + crates/minymaton-mobile-core lets you monitor streams, inspect live rosters and dispatch replies or nudges over HTTPS from a phone without SSH tunnels. Clients share an HTTP contract, not a filesystem or CPU architecture. Linux, macOS and Windows agents x86 64 and aarch64 can use the same server simultaneously. Durable storage lives on the server behind the QueueStore and QueueReader traits in minymaton-core : the open-source AGPL-3.0-only distribution ships the single-node bundled SQLite WAL backend Store + Reader , and Queue::with backend accepts any other backend that implements those traits. MCP clients need no shared checkout or local database. Parking additionally uses a qualified minymaton-wait binary matching the client's OS and CPU architecture or tools/minymaton-wait.py with Python 3 and explicit endpoint/credential configuration --url / MINYMATON URL / --config . Remote access uses SSH tunnels or an authenticated HTTPS reverse proxy to the loopback listener; see deploy/README.md https://github.com/immutlex-dev/minymaton/blob/main/deploy/README.md . No harness-specific hooks or SDK. MCP clients can join the data/ACK plane over HTTP. Inter-turn wakeups additionally require a harness that reports native background-command completion; MCP alone cannot wake an idle model. Handling and re-parking remain agent-owned. The helper makes one sessionless request, with no polling or automatic retry loop; Rust commit/ownership watch channels, cancellation-safe wait guards and transactional ownership checks drive delivery. The build's typed HIR policy rejects internal timed waits and readiness polling. These projects overlap with different parts of the problem. Some already offer remote HTTP, event-driven waits or durable cursors. Tool counts follow their linked inventories AgentChatBus's count comes from its TypeScript definitions , not a capability ranking. | Project | MCP tools | Runtime and delivery tradeoff | |---|---|---| | MCP Agent Mail Rust https://github.com/Dicklesworthstone/mcp agent mail rust | 45 | HTTP or stdio; Git-backed archive plus SQLite, durable recipient inbox cursors and message acknowledgments. Includes contacts, file reservations and build slots. Remote clients do not need their own mailbox database. | | Concord https://github.com/Get-Concord-AI/concord-mcp | 5 | Repository-local .concord/ SQLite workspace or a global store . Live prompt/reply delivery uses per-harness adapters; hook-only integrations leave durable pull messages. Its small surface manages work state rather than a stream/batch bus. | | agent-bus https://github.com/MustaphaSteph/agent-bus | 65 | Local SQLite or a remote Cloudflare MCP deployment. Skills-plus-MCP setup and optional listener-hook plugins; includes tasks, workspaces and workflow controls. Hooks are not required for every configuration. | | Let Them Talk https://github.com/Dekelelz/let-them-talk | 65 | Local Node.js broker and shared .agent-bridge/ project runtime, CLI-specific setup and operator dashboard. Includes planning, sessions, voting and review workflows. | | agentwisper https://github.com/jhqian/agentwisper | 26 | Central SQLite broker over Streamable HTTP. message wait uses an event, with a default 30-second timeout; squad/team management and timed RPC are part of its API. | | agent-mailbox-mcp https://github.com/lleontor705/agent-mailbox-mcp | 21 | Stdio by default, with HTTP/A2A mode providing task SSE and webhook delivery. Includes task delegation, resource leases and dead-letter handling; an inbox read or A2A stream is a different contract from a parked, acknowledged batch receive. | | AgentChatBus https://github.com/Killea/AgentChatBus | 35 https://github.com/Killea/AgentChatBus/blob/HEAD/agentchatbus-ts/src/adapters/mcp/tools.ts | HTTP/SSE backend with VS Code/Cursor integration. msg wait exposes timeout ms ; the surface also covers thread lifecycle, templates, reactions and agent heartbeats. | The point: one durable queue, explicit ACK-after-handling and receive ownership, plus a native background waiter that needs neither a shared filesystem nor harness-specific hooks, at the cost of distributing a matching executable. The parked lifecycle park-deliver-handle-re-park spells out its terminal outcomes and wakeup limits. Before building or hosting your own server, you can mint a free, strictly isolated 24-hour capability channel on the public sandbox: - Browser console: https://cp.scritty.dev/minymaton-try/ https://cp.scritty.dev/minymaton-try/ — one-click channel minting, copy-paste harness snippets Copilot CLI, Claude Code, Codex, curl , and live browser-to-MCP round-trip verification. - Background wakeup helpers: the portal's helper downloads https://cp.scritty.dev/minymaton-try/ helpers include native Linux, macOS, and Windows builds for both x64 and ARM64, plus the portable Python 3.10+ helper. Install on the OS running the agent WSL uses Linux , set MINYMATON TOKEN privately in its environment, and run exactly one helper per subscription handle using the harness's background-command tool. Handle the delivered batch, ACK, then explicitly re-arm; do not park with a foreground MCP wait. - Terminal one-liner: Returns a JSON lease with your isolated stream curl -sS -X POST https://cp.scritty.dev/minymaton-try/mint ch-