ContextDB Memory

io.github.mikhailbovtPublished by GitHub account mikhailbovtv0.6.0-alpha.3Updated Oct 24, 2026

Local-first durable AI memory with policy-bound recall and a typed project graph.

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local-first durable project memory for Codex: a bundled MCP adapter that recalls decisions, constraints, goals and milestones from a local ContextDB graph.

What you can do
  • Recall bounded, policy-checked project context at the start of substantive work
  • Capture decisions, constraints, preferences, goals, open loops and verified milestones as quarantined candidates
  • Organize memories in a typed project/topic/memory graph with multi-parent links and explicit successor revisions
  • Keep the model-facing surface read-only toward canonical memory, so it cannot promote, overwrite or delete it
  • Back up, restore, reset and uninstall local custody through guarded lifecycle scripts
When to use it
Worth adding when you want Codex to carry project history across tasks and sessions on your own machine, so settled decisions and open loops are not lost. It suits local, single-developer workflows rather than hosted or multi-user setups.
Requirements
Runs as a local process on Windows x86-64 or Linux x86-64 only (no macOS or ARM64). Needs an x64 Node.js 18+ on PATH; Linux also needs Python 3.10+ and glibc 2.35 or newer. Installed via the Codex plugin marketplace, a self-contained release ZIP, or source; the Codex CLI is required. No API key, account, Docker or remote service.
Before you install
Developer preview with unsigned executables; the plugin downloads and verifies a pinned core binary on first start, so review the bundled hooks when asked to trust them. It writes durable memory automatically and stores it locally; Linux file permissions are not encryption, so use disk encryption if at-rest protection matters. Uninstall purges data only with explicit flags and confirmation tokens, and removal is not secure erasure.

Installation

In SourceWeft

  1. Open ContextDB Memory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.6.0-alpha.3LatestSep 16, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

Other Memory integrations