ContextDB Memory runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 26 Aug 2026.
Local-first durable AI memory with policy-bound recall and a typed project graph.
What the code does
We read the source, 12 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.
setup = subprocess.run(
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 ContextDB Memory
same job, measured the same wayDurable user/project memory for MCP clients: recall context and remember selected facts.
Local-first memory engine for AI-agent teams: team/project ACL, recall, and federated sync.
Local-first project memory with legacy MCP and 2026 discovery compatibility.
Local deterministic project memory for AI agents with context packs, gates and checkpoints.
Local-first memory system for AI agents with hybrid search and graph reasoning
Local-first knowledge engine for AI agents: memory, graph, and recall over MCP.
Durable causal memory for AI agents — semantic recall, causal lineage, and skills. Local-first.
Role-aware Agent memory with cross-session recall, durable writes, and multi-Agent project scope.
ContextDB Memory — questions
Answers built from our own checks of this server.