Murmur MCP server
Commit Oct 21, 2026Enables end-to-end encrypted agent-to-agent messaging for AI coding agents like Claude Code and Codex across different machines and organizations.
Also known as alexfrmn/murmur
- Stars
- 21
- Tools
- 14
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Oct 21, 2026
- License
- MIT
What is Murmur MCP?
Murmur enables end-to-end encrypted agent-to-agent messaging for AI coding agents like Claude Code and Codex across different machines and organizations. It exposes 14 tools, such as murmur_request, murmur_send, murmur_inbox.
Summary generated from the project's README
About Murmur MCP server
Enabling end-to-end encrypted communication between AI agents is what Murmur does for developers using tools like Claude Code and Codex. It functions as a secure multi-agent communication bus that allows different agents to collaborate across different machines, organizations, and countries without a central orchestrator or human relay. The system uses NATS for transport and XChaCha20-Poly1305 for encryption to ensure privacy during peer-to-peer interactions.
Users can deploy Murmur via a desktop application for Mac and Windows or through a portable CLI and runtime for macOS, Linux, and Windows. The setup requires Node.js 22.13.0 or newer and utilizes a SQLite outbox for message handling. Developers can manage their connections using the murmur command-line interface, which includes tools for configuring clients and managing identities. This setup allows for autonomous workflows such as code reviews and architectural decisions to occur directly between different AI models.
What you can do with it
- 1Autonomous code reviewsHand off a task to an AI client to perform code reviews between agents without human intervention.
- 2Secure peer-to-peer messagingEstablish a direct, encrypted communication channel between two AI agents using NATS.
Written from the project's README. Every use case is checked against a quote from it.
Murmur MCP tools 14
Detected from the READMEmurmur_requestmurmur_sendmurmur_inboxmurmur_peerssend_messagelist_conversationssearch_messageschannel_createchannel_listchannel_memberschannel_evaluate_addressingchannel_presence
Show all 14 toolsShow fewer tools
channel_presence_heartbeatchannel_presence_leave
Configuration
DATA_DIRMURMUR_STORE_PATH
Automated checks
Ran Nov 13, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablealexfrmn/murmur is public and reachablegithub.com/alexfrmn/murmur ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-21github.com/alexfrmn/murmur ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model14 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubWhy "Murmur"?
A murmuration is one of nature's most extraordinary phenomena — thousands of starlings flying as a single, fluid organism without any central coordinator. Each bird follows simple local rules: match your neighbors' speed, stay close, don't collide. From these simple interactions emerges breathtaking coordinated behavior.
Murmur applies the same principle to AI agents. No central orchestrator. No human relay. Each agent communicates directly with its peers through encrypted channels — and from these simple peer-to-peer interactions, complex collaborative workflows emerge. Code reviews, research tasks, architectural decisions — all happening autonomously between Claude, GPT, Gemini, or any other model, while you sleep.
Review prerelease v2.12.1
2.12.1 is available as a GitHub review prerelease; stable and Latest remain 2.12.0. The new release separates Claude Chat, the Code tab and Codex during connection, adds an existing-installation guide and prompt, supplies MCP usage instructions, and corrects Windows upgrade order and clipboard feedback. It detects Code inside Claude.app, supports a dedicated folder with one shared wake reader, keeps verified Homebrew Node paths stable, and removes machine diagnostics from personal unread counts. The Mac app adds a read-only personal inbox, optional count-only notifications and actionable pairing errors. It also includes the post-2.12.0 fixes already on main, including per-contact diagnostics and clearer installer errors. See CHANGELOG and the package versions, upgrade steps and release checks.
The prerelease assets come from reviewed source dcfe8ccb6bf237998c2f39e1ddb9df951ce2e1f1 with required CI checks passed. A live Mac Claude Code round-trip passed with a temporary inbox-specific permission rule and authorization for one synthetic reply; automatic replies with default permissions are not established. Windows live installer/upgrade GUI acceptance and reboot remain unverified. Mac notifications and successful quarantined first-open also remain unverified; the observed first-open was blocked by Gatekeeper.
Use the native or portable artifacts for prerelease review. The thirteen candidate npm versions remain unpublished; attached tarballs are review artifacts. The stable install commands below intentionally select the available 2.12.0.
Already using Murmur? Read the upgrade checklist and what changed, or the short Russian guide for Mac and Windows. Keep your existing Identity. A green connection indicator is not proof that your usual assistant can read and return a message.
Optional TLS and per-user broker credentials
are also available in the candidate, with an explicit guarded migration command.
Existing remote nats:// profiles remain compatible. An explicit tls:// endpoint
requires certificate validation and cannot fall back to plaintext; upgrading does
not migrate the shared broker or rotate credentials.
Install
Using the app on Mac or Windows? The step-by-step guide with every screen and system warning is on the website: murmurconnect.com/#install (по-русски). Below is the path for the CLI and source.
@murmurv2/cli@2.12.0 is published on
npmjs. Install the prebuilt CLI with:
npm install --global @murmurv2/cli@2.12.0
murmur version --json
The same release is available as GitHub release
assets. @murmurv2/*
packages published before the 2.12.0 release (28 Sep 2026) are frozen and lack the current delivery fixes. The npm CLI needs Node.js 22.13.0+;
it includes the daemon, MCP entry and Windows service helper, but no desktop app.
On Windows PowerShell use npm.cmd and murmur.cmd if policy blocks the shims.
Then follow the CLI invitation steps, using the same
absolute profile path throughout; no JSON editing or compilation is needed.
Choose the v2.12.0 asset for the way you run Murmur. All assets require an
external Node.js 22.13.0 or newer with working unflagged node:sqlite. Download
them from the v2.12.0 release page:
| Asset | Choose it for | Start here |
|---|---|---|
Murmur-2.12.0-windows-x64-setup.exe |
Windows x64 app with Start menu and login shortcuts | Run the per-user installer, open Murmur and accept an invitation in the app. Service installation requests Windows elevation separately. |
Murmur-Mac-2.12.0-universal.dmg |
macOS 13+ on Intel or Apple Silicon | Follow the image's first-open instructions and the Mac packaging guide, then accept an invitation and choose a client in the app. |
Murmur-Windows-2.12.0-x64.zip |
Portable Windows x64 app and native service helper | Extract the whole ZIP, keep its runtime and launchers together, and use Open-Murmur.cmd. Follow the bundled README for an existing service. |
murmur-runtime-2.12.0.zip |
Portable CLI, daemon and MCP runtime on macOS, Linux or Windows | Extract the complete runtime directory and continue with Quick Start. Git, npm and a build are not needed on the receiving machine. |
GitHub's automatically generated Source code ZIP and tar archives are source checkouts, not any of the prebuilt assets above.
Source path: build the pinned v2.12.0 tag. You need Git and Node.js 22.13.0+.
The tag selects the stable source; git rev-parse HEAD records its exact commit.
git clone https://github.com/alexfrmn/murmur.git
cd murmur
git checkout --detach v2.12.0
git rev-parse HEAD
On macOS/Linux, run npm ci then npm run build. On Windows PowerShell, run
npm.cmd ci then npm.cmd run build as separate lines. npm.cmd avoids the
npm.ps1 execution-policy error on a default Windows installation. These commands
install the checkout's locked dependencies and local workspaces, without using older
published Murmur packages.
Murmur does not update an existing installation automatically. In particular, a
Windows service owns paths into its installed bundle: keep the old tray open,
choose Service → Stop → Remove, then quit the tray and run setup. If the tray
is already closed, reopen it or uninstall the service through the old CLI. Install
the service from the new bundle, retain the same absolute profile
path and service name, and do not run init or join again. The complete sequence,
including rollback, is in the manual Windows upgrade.
Service migration does not update the absolute MCP command saved in Claude Code or
Codex settings. Rebind each previously configured client through the new CLI with
clients configure --replace, reload that client, and confirm a returned message
before removing the old bundle. The maintained guide includes this step; the
original 2.10.0 ZIP's bundled instructions omit it.
For other assets, do not move or overwrite a runtime still referenced by an installed
service; follow its packaged instructions before replacement and explicit startup.
The CLI update action only opens the release page.
Continue with Quick Start in the same checkout or extracted runtime. Do not clone a second copy.
Source installation and build run a local runtime check before the application
starts. In a source checkout only, npm run check:runtime (npm.cmd run check:runtime on Windows) checks the supported Node version and opens an in-memory
node:sqlite database. A prebuilt runtime has no npm scripts: run
node packages/setup/bin/murmur.mjs version --json from its runtime directory.
Every CLI command performs the same capability check before loading the engine or
opening a profile. A disabled or unavailable SQLite module produces an actionable
error. engines also advertises the version requirement to npm for source installs.
Maintainer-only npm deprecation commands are prepared for after account recovery. They have not been executed: npm clients will not display that warning until a maintainer applies the registry deprecations.
What's New in v2.12
-
Development source: select one installation explicitly (#168).
init/join --selectorinstallation select --data-dir ABSOLUTEregisters a private identity-bound choice shared by CLI, MCP and daemon. Missing selection no longer creates a working-directory.datastore. Explicit multi-profile overrides and existing service/client pins remain; see selection and legacy migration. This is not in v2.12.0. -
Set up a connection without a terminal. On Windows and Mac, paste an Invitation or a Reply from your messenger into the app; it picks the
MURMUR:line out of the surrounding text, keeps a backup of the Invitation next to the profile and, on the Mac, keeps the Identity you selected through recovery. A Service left by a pilot or an earlier version is replaced from the tray with one administrator consent. -
Claude Code listens for eight hours, as documented. The Stop hook entry now carries its own
timeout; an entry written by 2.11.0 or earlier listened for ten minutes and is updated with--replaceor by reconnecting the assistant in the app. -
A lost server link is no longer silent. Every failed reconnect attempt is counted and logged once a minute,
murmur statusshowsbroker.disconnectedAtandbroker.reconnectAttempts, and a daemon whose connection closed for good exits with code 3 so the service manager restarts it and shows the failure. See docs/broker-link.md. -
Registry and site.
server.jsonfor the MCP registry andmcpNameon@murmurv2/cli; murmurconnect.com has step-by-step install pages for Mac and Windows, a Russian page and guides on Claude Code and Codex across machines, wake-up and comparison, each also in Russian under/ru/.
v2.11
- Set up a connection in the app. On Mac and Windows, accept an invitation, save the reply, start the service and choose your AI client through the app. Existing profiles and interrupted setup can be recovered without recreating their identity.
- A Windows installer and a prebuilt CLI. The per-user
setup.exeinstalls the app and its shortcuts. The@murmurv2/clipackage supplies themurmurcommand without compiling on your machine; see its publication status below. - Clearer connection and wake status. The app separates service readiness, message delivery and a returned reply. Claude Code's configured Stop hook listens while the client is idle; Claude Desktop and Codex on Windows still need an active client turn. See known limitations.
v2.10
- Three stable release assets. Choose
murmur-runtime-2.10.0.zipfor the portable CLI, daemon and MCP runtime,Murmur-Windows-2.10.0-x64.zipfor the Windows x64 companion, orMurmur-Mac-2.10.0-universal.dmgfor macOS on Intel or Apple Silicon. Node.js 22.13.0 or newer remains an external prerequisite for every asset. - Updates remain manual. Murmur can open the stable release page after an explicit click. It does not download, install, replace or restart the runtime, native app, service or profile.
v2.9
- Exactly-once wake delivery. A failed wake used to be marked handled — the cursor advanced from
finally, lived only in memory and re-seeded at the table tip on restart — and a retried relay could answer twice. Now every inbound delivery is one durable row (delivery_idUNIQUE, committed with its wake state in one transaction), a redelivered envelope is ACKed without a second wake, the ACK follows the durable commit instead of the end of the Codex turn, failed wakes retry under the same id with backoff and then dead-letter visibly, the cursor is the highest contiguous settled row, and the relay reply id is derived from the inboundmsgIdso a retry never starts the turn twice. Design by @alexanderyswork in #96. (v2.9.0) - Codex turn outcome is read, not assumed.
turn.status/turn.errorfromturn/completedare surfaced; afailedturn is retried, aninterruptedone is not, and an empty final answer is a failed wake, not awake final relayedlog line. (v2.9.0) - Lanes instead of one line. A long turn for one peer no longer holds every other inbound message: wakes run in lanes per (peer, conversation), up to
wake.concurrencyat once (default 4), ordered within a lane. (v2.9.0) - Codex threads per conversation, remembered across restarts. Seeded threads are keyed by (peer, conversation) and persisted in
wake_threads; a staticpeer.threadIdstays an explicit pin. (v2.9.0) - The cold-start watcher stands down while a session is alive.
codex-murmur-coldstart-watch.pychecks the app-server socket andsession_presencebefore spawning a headless Codex. (v2.9.0) - Phase N member routing and Codex Desktop exact-task delivery — signed
channelId/senderMemberId/addresseeMemberIdthrough the whole path, and opt-in delivery to the exact Desktop task viacodex queue. By @fedoseevstanislav. (v2.9.0)
v2.8
- Cold-start drain — what arrived while nothing was listening. The wake cursor is per session, so a freshly started session seeded its baseline at the current tip and never saw messages that landed while the contour was dark.
wake-drain-claude.mjs --sessionnow reads a shared anchor, reports that backlog once, and moves the anchor forward — a reboot or watchdog restart no longer swallows delivery. (v2.8.0) - A rejection the receiver never logged, and one it treated as poison. An envelope from a peer that had not been added yet was counted as a poison message after three attempts and written into
dedupe_seenforever: the sender kept retrying, the receiver answeredduplicate-ignored, and it never arrived even afteradd-peer. Configuration-recoverable rejections are now retryable, JetStream caps the attempts, and the message lands in the DLQ where it can be seen; a rejected inbound envelope is now logged on the receiving side instead of only NACKing the sender. (v2.8.1) - The sender's half of an ACK storm. Three loops on the publishing side that the receiver-side 2.8.1 fixes did not touch — measured live on a shared broker at ~4.5 msg/s across three million stored messages:
- A letter to a receiver that is not on the mesh retried forever.
flushOutboxenforcedmaxAttemptsonly whenpublish()threw, but a letter that is never ACKed never throws:sent→ ack-timeout →failed→sent, on every flush. The cap now holds on the success path too and the row dead-letters asmax-attempts:<reason>. - A delivered message was undone by a timeout on its own ACK.
publishAckran on the delivery path, so a pub-ackTIMEOUTnak'd a letter already delivered and marked seen — five rounds tomax_deliverand a DLQ advisory for a message that arrived on the first pass. Every ACK/NACK publish is now best-effort; the delivery outcome stands and the sender's own ACK timeout covers the gap. - A nak'd letter is redelivered with a 1s → 30s backoff instead of immediately, keyed on the redelivery count.
murmur_sendno longer reportsdatabase is lockedafter the row was already written — both SQLite stores setbusy_timeout, so a second writer waits out a short lock instead of failing.- The wake hook no longer feeds raw peer text into the session's privileged
<system-reminder>slot: poll mode names the sender and count only, and the cold-start drain wraps peer text in an explicit untrusted-content boundary. Reported by Kirill Oleinichenko. (v2.8.2)
- A letter to a receiver that is not on the mesh retried forever.
v2.7
- A failed message could retry forever and never settle.
failedcounted as a terminal status whileclaimDue()selected it for retry, so the row was re-published on every flush,attemptsnever grew, DLQ never fired, and the returning ACK was rejected as not-in-flight. The v2.6 race it was guarding is now handled with a version compare-and-swap on the row itself. - The inbox silently dropped delivered messages.
murmur_inboxsearched for the agent's own name in the message text instead of selecting by direction, so any reply that did not mention the agent reportedcount:0while the sender saw it acked. No error on either side — the worst possible shape for autonomous agents. - Murmur now installs and wakes on Windows. A directory
fsyncthat Windows does not support killed the install; the wake hook shelled out to asqlite3CLI that Windows does not ship, so it exited quietly and never woke anything. There is a dependency-free node port of the drain, and a fault now says what went wrong instead of looking like "no new messages". - One message wakes every live session, not just the first one to notice. Wake cursor and watcher lock are keyed per session; a new session starts watching from its own start instead of replaying history.
- Credit where due. The three cross-host defects were found and reported — two with pull requests — by @lichtpfad, testing Mac ↔ Windows over a local NATS broker.
v2.6
- Signed-ACK hardening. Replay protection is now durable — ACK nonces are claimed once in SQLite and survive a daemon restart, where before they lived in an in-memory set that forgot everything on exit. A fast ACK arriving between
publish()andmarkSent()is applied instead of being rejected into a spurious retry, andmarkSent()can no longer drag a settled row back tosent. - Two unguarded ACK paths closed. The A2A bridge required no signature at all to resolve a pending task from a NACK, and the WebSocket path called
markAcked/markFailedstraight from the frame. Both now perform the same verification as the NATS path. - Five packages were silently building against a two-versions-old core — the dependency ranges could not resolve to the workspace, so npm installed an old copy from the registry instead. Their green tests meant less than they appeared to.
v2.5
- Signed and bound delivery acknowledgements. ACK correlation rejects unsigned frames in every mode.
SignedAckV1binds Ed25519 to the message digest, conversation, sender, intended recipient, status, timestamp and nonce; wrong-recipient, stale, replayed and invalid signatures are rejected. LegacyackSecurity.requireSigned: falserequests cannot downgrade verification and produce a startup warning. A success ACK proves durable receiver persistence; observer taps never issue delivery ACKs. See rollout requirements. - Local state is no longer world-readable. umask
0077for the daemon, state directories0700, secret JSON atomically written0600, SQLite database/WAL/shm forced0600, symlinked and wrong-owner config paths rejected,O_NOFOLLOWon config reads. Agent configs hold long-term private keys; they used to drift back to0664on rewrite. - Dashboard hardening. Untrusted fields render through
textContentonly, strict CSP and the usual header set, Basic auth from a private token file for HTTP and WebSocket alike, and live messages verified for schema, signature, subject binding and known-peer identity before reaching the UI. Fails closed without a token file. - Codex wake fixes. Seeded threads keep
thread.pathand carrypeer.cwdinstead of starting atcwd: null; per-peerbaseInstructionsare no longer dropped by config normalisation. - Credit where due. This release is substantially external work — a security audit by @fedoseevstanislav and wake/delivery analysis by @alexanderyswork.
Murmur MCP questions
What tools does Murmur MCP provide?
It exposes 14 tools, including murmur_request, murmur_send, murmur_inbox, murmur_peers, send_message.