mnemo
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mnemowhat's the current project status and any active constraints?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Mnemo
Mnemo is an open-source, local-first context runtime for coding agents. It keeps project facts, decisions, constraints, tasks, failed approaches and Git-aware checkpoints outside any individual model, then compiles only the relevant context for the next session.
The model can change. The project memory remains.
Why Mnemo
Coding sessions are temporary, but project decisions are not. Mnemo provides a small continuity layer shared by Codex, Claude Code, Gemini CLI and any MCP-compatible client:
developer → Mnemo → relevant context → coding agent → checkpoint → MnemoMnemo is not an IDE, hosted service or coding agent. The core works offline and stores data inside the project.
Related MCP server: projectmem
Requirements
Node.js 22 or newer
Git is recommended, but not required
At least one supported agent CLI for
ctx <agent>
Install
During development:
pnpm install
pnpm build
npm linkAfter publication:
npm install -g mnemo-context-runtimeQuick start
cd my-project
ctx init
ctx task "Implement authorization" "Add server-side role checks"
ctx decide "Identity key" "Use immutable provider subject, never email"
ctx constrain "Authorization boundary" "Every object access is checked server-side"
ctx checkpoint "Authorization foundation"
ctx codexRunning ctx without an agent opens a selector containing the installed agent CLIs.
For the complete command sequence in Portuguese, see
GUIA_DE_USO.md.
Commands
Command | Purpose |
| Create |
| Select an installed agent and inject compiled context |
| Start one agent with the current context |
| Record a durable fact |
| Record an active decision |
| Record a critical constraint |
| Record the current or next task |
| Record a failed approach and resolution |
| Snapshot Git state and project continuity |
| Print the token-budgeted context package |
| Retrieve memory related to a decision or topic |
| Show active memory and checkpoint state |
| Diagnose runtime and agent availability |
| Serve project memory using MCP over stdio |
Use ctx <command> --help for command-specific options.
Storage
Mnemo creates:
.context/
├── config.json
├── context.db
├── state.json
└── logs/.context/ should not be committed. Project configuration stays local, and SQLite uses WAL mode, foreign keys and prepared statements.
Security model
All text is sanitized before persistence. Built-in rules redact common API keys, bearer credentials, JWTs, private keys and password-like assignments. .contextignore documents files that must not enter repository analysis.
Sanitization is defense in depth, not a reason to paste credentials into Mnemo. Never deliberately record secrets.
MCP setup
Any MCP client that supports local stdio servers can launch:
{
"mcpServers": {
"mnemo": {
"command": "ctx",
"args": ["mcp"]
}
}
}Available tools include project_state, project_context, memory_search, memory_get, report_memory and memory_checkpoint.
Design principles
Git owns code history; Mnemo owns continuity and rationale.
Active decisions supersede old decisions instead of silently rewriting history.
Context cost grows with changes, not the full conversation history.
Local rules and deterministic inspection come before optional model inference.
An agent receives a minimal package first and retrieves more context on demand.
Development
pnpm typecheck
pnpm test
pnpm buildSee PROJETO.md for the product definition and IMPLEMENTATION.md for release status.
Benchmark
The first controlled handoff experiment is documented in
benchmarks/devtrace-saas/RESULTS.md.
It observed an 18% reduction in uncached-input-plus-output tokens with equivalent
typecheck/test outcomes. This is an initial paired run, not yet a statistically
reliable performance claim; the protocol requires at least five repetitions.
License
Apache License 2.0.
This server cannot be deployed
Maintenance
Related MCP Connectors
Persistent memory, hybrid search and a goal graph for AI agents, over stdio or remote HTTP.
Shared memory for coding agents. Stop re-explaining your codebase every session.
Project memory, semantic code search, and grounded agent context.
Project memory for coding agents: requirements, decisions, code graph and delivery telemetry.
Related MCP Servers
- AlicenseAqualityAmaintenanceHosted memory for coding agents, exposing commit_mem, recall, and status over stdio. Each write carries provenance, contradictions surface as inspectable state changes, and a bad run can be rolled back from a snapshot.11530 PyPI1Business Source 1.1
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to persist project memory across sessions by compiling decisions, progress, and pitfalls into git-linked, evidence-backed entries. It lets clients add, query, inject, scan for stale, check assertions on, and compute ROI of those memories over stdio.367 npmMIT
- AlicenseNot gradedqualityAmaintenanceExposes repo-native, self-verifying memory to coding agents over stdio MCP, letting them recall ranked past decisions, record new claims with verifiable receipts, and check the health and stats of stored memory. Keeps agent context honest by surfacing memories whose evidence no longer holds.7 npmMIT
- AlicenseNot gradedqualityAmaintenanceServes a unified local memory bank over a stdio MCP server, exposing five tools and one resource so any MCP-capable harness can list, search, and read memories imported from Claude Code, Codex, Cursor, Kimi Code, and ZCode. It gives agents a single read-only view of user preferences, feedback, project state, and reference material stored as plain Markdown files.MIT