ContextDB Memory MCP server

Automatic project continuity for Codex, backed by a local ContextDB memory graph.

Install · See it grow · Operate safely

Codex can understand a repository brilliantly and still wake up in the next task with the emotional continuity of a goldfish. ContextDB Memory gives it a durable, local project history: the decisions already made, constraints that still matter, goals in flight, verified milestones, and open loops waiting for somebody to stop pretending they do not exist.

The plugin recalls relevant context at the start of substantive work and checkpoints significant state as the task evolves. It does this through a bundled, listener-free MCP adapter; the database, runtime, keys, and mutable memory remain on your own Windows or Linux computer.

Release status: 0.6.0-alpha.3 Developer Preview for Windows x86-64 and Linux x86-64.

Both local profiles include automatic hooks, a typed candidate graph, platform-specific custody,

recovery and uninstall controls, and independently verifiable release bundles. Executables are

unsigned, macOS and ARM64 are not supported, and this is not a hosted ContextDB service.

The Linux ELF uses an Ubuntu 22.04 / glibc 2.35 baseline; other glibc-based

x86-64 distributions require glibc 2.35 or newer and are not individually certified.

What it remembers

Short-lived chatter, guesses, copied logs, secrets, and “maybe someday” noise should not become durable memory. The active Codex model decides whether a change is significant; the host contract constrains how it may be written.

How the memory grows

flowchart LR
    S[Session starts] --> R[Bounded candidate recall]
    R --> W[Codex works with current files]
    W --> C{Durable change?}
    C -- no --> W
    C -- yes --> Q[Quarantined candidate]
    Q --> G[Project / topic / memory DAG]
    G --> R
    Q -. explicit successor .-> Q2[New revision]

Shortened. The full README is on GitHub.