Memoir MCP server

Memoir

Portable, project-scoped memory and session handoffs for coding agents.

Memoir keeps decisions, rationale, goals, and next actions in readable local files. An MCP server lets an agent save and retrieve that context. Optional local, Git, and cloud backups move it between machines.

The reliability changes are described in the remediation record. Review the upgrade and recovery guide before upgrading clients that share encrypted backups.

Continue between Codex and Cursor on this computer

Memoir includes a separate, project-only handoff. It carries answered questions, decisions, next actions and receipts from checks actually run through Memoir. It does not import personal memory or transcripts.

The project handoff, browser view and recovery commands below require version 3.16.0 or later:

npm install -g memoir-cli@3.16.0
cd /path/to/your/project
memoir work setup
memoir work resume
memoir work view

For source development, install dependencies and replace memoir with node bin/memoir.js from the Memoir checkout.

Open this same folder and branch in Codex or Cursor and say “Continue this project.” The managed instructions use the project MCP connection, or the included CLI fallback when the connection is unavailable. Existing settings and approval policies are preserved. Agent adherence is still required; ordinary terminal checks are not captured automatically.

The project view opens in your browser on this computer. Search saved answers, see why a check needs repeating, correct a decision, or remove it from the next handoff. Removed records can be restored; earlier versions stay in local history. Keep the view's terminal open while using it, and press Ctrl+C to stop. You can also ask your agent “Open my Memoir project view.” See the local view validation for actual browser tests and the limits of the fresh-session continuity results. Subsequent debugging fixes and recovery tests cover slow saves, interrupted responses and configuration preservation.

Checks run through memoir work check using the client's normal terminal permissions. The MCP memory connection deliberately cannot execute commands. See the adversarial audit and remaining trust limits.

The project ledger stays in ignored .memoir/ files. This workflow does not sync those files through GitHub or bridge different checkouts. See the setup and everyday guide for commands, corrections, privacy boundaries and when a check needs to run again. The feature runs locally even when installed from npm; publishing the package does not upload your project ledger.

Project handoffs now have automatic local recovery snapshots. Run memoir work doctor to check them, or memoir work backup --output /path/to/backup.memoir for an encrypted copy outside the project. Recovery previews changes before applying them and preserves the original file. See backup and recovery.

Existing memory and backup workflow

Node.js 18 or later can run the CLI. For production use, choose a maintained LTS release (Node 22 or 24); Node 18/20 remain compatibility-test targets. See the Node release policy.

npm install -g memoir-cli
cd /path/to/project
memoir setup --tool claude,codex,cursor
memoir goal "Finish the account recovery flow"
memoir note "Use single-use recovery codes" --why "Prevent replay"
memoir next "Test expired recovery codes"
memoir recall "recovery codes"
memoir resume

setup preserves existing settings, writes a project MCP entry, and starts the Memoir server to check its tools. Restart the client and accept its project trust/MCP prompt. Server startup does not prove that a particular client version has accepted its configuration.

Shortened. The full README is on GitHub.