A memory MCP server for Claude

MCP is how Claude Desktop and other clients talk to outside tools. This guide gives Claude memory that persists between conversations, runs entirely on your machine, and can answer why it believes what it believes, not just what.

Start the server

First run prints a project id and an API key, and serves a dashboard on the same port where you can watch memories arrive.

Wire it into Claude Desktop

Add this to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\) and restart the app:

omem-mcp speaks MCP over stdio and starts with nothing else configured. Claude gets remember, recall and why tools, plus the reasoning verbs.

What makes this memory different

The model proposes memories; a belief revision engine decides what is actually believed. When two remembered facts contradict each other, both survive, flagged, with sides. Ask the why tool about anything and you get the evidence chain: who said it, when, what contradicts it. Retract a fact and everything concluded from it is withdrawn in the same request. Nothing is silently overwritten because a newer message arrived.

Everything stays local: SQLite on your disk, zero runtime dependencies, and the server provably makes no outbound connections. The air-gap test in CI fails the build if any code path so much as looks up an external hostname.

Where to go next

The quickstart covers the same server from the SDK side, and the Python guide shows the belief-tracking surface the MCP tools sit on.