ops-brain runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 30 Oct 2026.
Self-hosted team bus for AI agents: cross-machine handoffs, check-in, and shared gotchas.
What the code does
We read the source, 3 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
as_pg() { if [ "$(id -u)" = 0 ]; then runuser -u postgres -- "$@"; else "$@"; fi; }
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.
SELECT COALESCE(f.id, v.id) AS id,
COALESCE(1.0 / (60 + f.rank), 0) + COALESCE(1.0 / (60 + v.rank), 0) AS score
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found things in this code
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch ops-brain and you get told the day something new turns up.
Alternatives to ops-brain
same job, measured the same wayTasks, comments, shared memory and handoffs for teams of people and AI agents, over MCP.
One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.
Persistent memory for AI agents: one brain shared across Claude, Cursor, Codex and more.
Shared MCP memory for AI agents: knowledge base, skills, todos and agent-to-agent handoffs.
One shared project for a team's coding agents: decisions, a task board and handoffs.
Self-hosted MCP server: a case file for every task, shared across sessions, agents and people.
Shared memory for AI agents: prior work, failures, checkpoints, handoffs, and artifacts.
Shared memory for teams that work with AI agents: meetings, email and calendar in one brain.
ops-brain — questions
Answers built from our own checks of this server.