mwe-mcp — Memory Wiki Engine MCP server

mwe-mcp — the Memory Wiki Engine

Every AI agent you use, remembering into one shared Markdown wiki. Every fact in it governed individually: who it's about, who said it, who may read it, and when it stops being true.

▸ Open the public demo · demo.contea.casa

One household's shared memory: three people, three assistants, 203 turns of conversation from 2 March to 18 July 2026, rebuilt by the engine and then frozen. Enter as Bob, Alice or Zoe with one click, on any page, and see what each of them may read. It is read-only: nothing you do changes it, nothing you click calls a model, and no agent can be attached to it. The guided tour walks eight pages of it.

Why · The demo · The tour · The idea, in one page · Quickstart · Where it fits · How it works · Docs

Why this exists

Ask most agent frameworks where their memory lives and the honest answer is "in a vector index somewhere." That works until you want to do something human with it: open it, fix a wrong fact, understand why the agent believes what it believes. Or the hard one, let more than one person share a memory without everyone seeing everything.

A blob of embeddings has no answer to who is this fact about, who told us, who's allowed to read it, and is it still true?

mwe-mcp answers all four. The memory is a folder of Markdown pages you can open and read. Underneath, every fact on those pages is indexed and governed one by one, and the rules are enforced by the engine in code, not by asking a model nicely.

Same page, two readers, two answers

A family runs one shared memory. Every assistant they talk to writes into it and recalls from it: the voice assistant in the kitchen, a bot on Telegram, Claude Code on a laptop. Alice and Bob are on the team. Zoe is family, but not on the team.

Alice: "Bob changed jobs, he's at AcmeCorp now."

Assistant: "Noted in Bob's profile."

The engine resolves "Bob", decides the fact is about Bob so it lands on his page, keeps Alice as the one who reported it, and scopes it to group:team. Later, two different people ask:

Bob: "What do you know about my current job?"

Assistant: "You're at AcmeCorp (noted by Alice on May 17)."

Zoe: "Do you know where Bob works?"

Assistant: "I don't have anything I can share about that."

Same page, same fact, two answers. Zoe isn't on the team, so the span is removed before it ever reaches her agent. No error, no "access denied", just invisible.

Here is the page itself. Each governed span is wrapped in a marker that carries only a stable key, so the prose stays clean and everything sensitive about the fact (subject, sender, audience, validity) lives in the engine's index:

Alice is going through a busy stretch at work. See [[alice/acmecorp]].

She weighs {{f=0196c4b1-…}}72 kg{{/}} as of May 10, and
{{f=0196c4b2-…}}just cut her hair{{/}}.

Alice sees that verbatim. Anyone who isn't Alice sees the protected span collapse:

She weighs [redacted] as of May 10, and just cut her hair.

Shortened. The full README is on GitHub.