OMEM MCP server

OMEM

The system of record for what an AI agent believed and did. Append-only, with the evidence under every belief, both sides of every contradiction kept, and a named human behind every risky action. So when an agent acts and someone asks "why did it do that", you answer with a record instead of an investigation.

OMEM sits where a memory layer sits and does a different job. Instead of dumping text into a vector store and hoping for the best, it tracks what each agent believes over time, keeps the evidence under every belief, and handles contradictions explicitly, so an agent can reason about what it knows, when it learned it, and why it holds.

And it does not start from nothing. Installs that choose to pool what they work out about people in general, as counts that name nobody, and a young install borrows that intuition on day one instead of spending six months earning it. What you contribute is counts; what you get back is everyone else's. A borrowed pattern is born weaker than one you learned yourself, and still yields the moment a person's own evidence disagrees, so the general never overrides the individual.

The bank is empty today. No installation has contributed yet, which means the first ones decide what it learns, and it is worth knowing that a corpus of regularities about people can carry the biases of whoever filled it. The mining rule was rebuilt so that a pattern has to beat the base rate rather than ride it (Working Paper No. 1); whether the contributing population is representative is a separate question and an open one.

It runs locally with no external services and no dependencies to install.

pip install omem-infrastructure && omem-server

Or deploy a private server in one click:

The blueprint provisions one small service with a persistent disk, password auth on (the first signup is the operator account), and a generated master key. Fly.io works too: fly launch --copy-config with the included fly.toml.

Docs: infrastructure.omem-cloud.com · Quickstart · Security · Contributing

Shipping agents to clients? The audit trail and the approval gate are the

point: what a client's security review asks for,

and a small number of hands-on design-partner pilots are open.

Want to see the whole pattern run before reading another word?

refund-desk is the

reference integration: a support agent that moves money, with receipts.

One file, runs in a minute, asserts every claim it makes.

That is scripts/demo_reasoning.py, abridged. Every line is an asserted behaviour that runs in CI, so this picture cannot quietly stop being true.

Shortened. The full README is on GitHub.