Marrow runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 10 Aug 2026.
Shared memory for parallel AI coding agents. Local, free, with rooms and file claims.
What the code does
We read the source, 15 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
sel.innerHTML = projects.map(p => `<option value="${esc(p.project)}">${esc(p.name)}</option>`).join("")
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Marrow
same job, measured the same wayOne shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.
Shared debugging memory for AI coding agents
StremAI MCP: shared memory for AI coding agents. Connected agents can recall. OAuth + local stdio.
Local-first, cross-harness memory for AI coding agents.
One shared, durable memory for your AI coding agents — local-first, zero-dependency.
Local memory for coding agents. A rule with a runnable proof can refuse a wrong command.
Local-first persistent memory for AI coding agents.
Local-first shared memory and task coordination for AI coding agents. Go daemon plus headless CLI.
Marrow — questions
Answers built from our own checks of this server.