Memento is a local-first, open-source MCP middleware that gives your AI agents (Cursor, Claude Desktop, Trae, etc.) persistent memory, proactive goal enforcement, and autonomous intelligence — all running on a zero-cost SQLite temporal graph with Reciprocal Rank Fusion (RRF) retrieval.
No cloud databases. No API calls for storage. Everything stays on your machine.
Architecture
Temporal Graph Memory (RRF)
Built on SQLite FTS5 (full-text search) and cosine similarity (vector embeddings). Fuses keyword matches and semantic meaning via Reciprocal Rank Fusion. WAL-mode enabled for concurrency.
Tri-State Goal Enforcer
Keep your AI aligned with project objectives at three escalation levels:
- Level 1 — Context Injection: Automatically injects active goals into every search result. Active by default.
- Level 2 — Strict Mentor: Forces the AI to submit code/plans for goal alignment evaluation via LLM.
- Level 3 — Daemon Push: File-watcher monitors your workspace and proactively flags goal drift.
Active Coercion (Code Immune System)
Deterministic regex/tree-sitter rules that block anti-patterns at commit time and in the IDE. 100% deterministic — zero LLM hallucination risk during enforcement.
Autonomous Agent
Background cognitive loop with four levels:
- off: No background behavior (default).
- passive: Observe health and patterns every 5 min. No modifications.
- active: Consolidate memories, extract KG, warm caches, detect anomalies every 2 min.
- autonomous: All of the above plus dream synthesis, goal drift detection, task generation, health reports every 1 min.
Workspace Isolation
Each project gets its own .memento/ directory with an isolated SQLite database. No context bleeding between projects. Configure via MEMENTO_DIR or per-project .cursor/mcp.json.
Session Continuity
- Auto-checkpoints every 25 tool calls with full L1 working memory snapshot.
- Auto-resume restores goals and context from the previous session.
- LLM-agnostic handoff prompts for session transfer between agents.
Project Memory Graph
Semantic entity-relationship graph on top of the Knowledge Graph. Track files, components, decisions, and their dependencies. Impact analysis shows what breaks when you change something.
Unified Tool API (v0.3.x)
Memento exposes 14 action-based tools via MCP. Each tool uses an action parameter instead of separate tools per operation:
| Tool | Actions | Purpose |
|---|---|---|
memento |
(main router) | Primary proactive memory interface |
memento_project |
set_state, get_state, delete_state, set_goals, list_goals, summary |
Vision, milestones, blockers, goals |
memento_session |
begin, resume, handoff, status, list |
Session lifecycle and handoff |
memento_graph |
add_entity, add_relation, query, impact, summary |
Project Memory Graph |
memento_search |
basic, advanced, explain |
FTS, vNext pipeline, routing trace |
memento_remember |
add, consolidate, share, evaluate, hit |
Memory write operations |
memento_configure |
enforcement, coercion, daemon, autonomy, consolidation_scheduler, kg_scheduler, dependency_tracker, superpowers, access |
All configuration |
memento_cognitive |
dream, align, warnings, tasks |
Cognitive engine operations |
memento_health |
status, health, memory, kg, quality, relevance, cache, explain |
Diagnostics |
memento_coercion |
list_presets, apply_preset, list_rules, add_rule, remove_rule, install_hooks |
Active Coercion management |
memento_kg |
extract, health, cross_workspace_stats |
Knowledge Graph operations |
memento_notifications |
configure, list, dismiss |
Proactive notifications |
memento_audit_dependencies |
(standalone) | Dependency audit |
memento_migrate_workspace_memories |
(standalone) | Workspace memory migration |
Quick Start
Install
pip install memento-mcp
Or run without installing:
uvx memento-mcp
Configure (Cursor / Claude Desktop / Trae)
Add to your global mcp.json (e.g. ~/.cursor/mcp.json):
{
"mcpServers": {
"memento": {
"command": "memento-mcp",
"env": {
"OPENAI_API_KEY": "your-api-key",
"OPENAI_BASE_URL": "https://api.openai.com/v1",
"MEM0_MODEL": "openai/gpt-4o-mini"
}
}
}
}
For per-project workspace isolation, add to .cursor/mcp.json in your project root:
{
"mcpServers": {
"memento": {
"command": "memento-mcp",
"env": {
"OPENAI_API_KEY": "your-api-key",
"OPENAI_BASE_URL": "https://api.openai.com/v1",
"MEM0_MODEL": "openai/gpt-4o-mini",
"MEMENTO_DIR": "${workspaceFolder}"
}
}
}
}
Add .cursor/ to your .gitignore to avoid committing API keys.
Verify
memento-mcp --help
memento --help
Running without OpenAI (offline / testing)
Set MEMENTO_EMBEDDING_BACKEND=none to disable embeddings. Memento falls back to FTS5-only search — no API key needed.
MEMENTO_EMBEDDING_BACKEND=none memento-mcp
Environment Variables
| Variable | Default | Description |
|---|---|---|
OPENAI_API_KEY |
— | Required for OpenAI embeddings and cognitive features |
OPENAI_BASE_URL |
https://api.openai.com/v1 |
OpenAI-compatible endpoint (e.g. OpenRouter) |
MEM0_MODEL |
openai/gpt-4o-mini |
LLM model for cognitive features |
MEM0_EMBEDDING_MODEL |
text-embedding-3-small |
Embeddings model |
MEMENTO_EMBEDDING_BACKEND |
auto-detect | local (fastembed), openai, or none |
MEMENTO_DIR |
cwd | Workspace root for .memento/ state |
MEMENTO_UI |
0 |
Enable local web UI (1/true) |
MEMENTO_UI_PORT |
8089 |
Local UI port |
MEMENTO_UI_AUTH_TOKEN |
— | Auth token for local web UI |
MEMENTO_RULE_CONFIRMATION |
true |
Require confirmation before applying coercion rules |
MEMENTO_PROACTIVE_INJECT |
1 |
Inject relevant memories on every tool call (0 to disable) |
MEMENTO_PROACTIVE_TOP_K |
3 |
Number of memories to inject proactively |
MEMENTO_DECAY_SEMANTIC |
0.005 |
Decay λ for semantic memories (~200d half-life) |
MEMENTO_DECAY_EPISODIC |
0.02 |
Decay λ for episodic memories (~50d half-life) |
MEMENTO_DECAY_WORKING |
0.05 |
Decay λ for working memories (~14d half-life) |
MEMENTO_WRITE_SEARCH_TRACE |
0 |
Write last_search.json trace on every search (1 to enable) |
MEMENTO_HANDOFF_AUTO_CHECKPOINT_EVERY_N_EVENTS |
25 |
Auto-checkpoint frequency |
MEMENTO_SHARED_KG_PATH |
— | Path to a shared KG SQLite file (federation — multiple workspaces share one graph) |
MEMENTO_FEDERATION_SOCKET |
— | Unix socket path for push notifications between agents (replaces 30s WAL polling) |
CLI Usage
Memento works from the terminal too:
# Auto-capture git context as a memory
memento capture --auto
# Save a free-form note
memento capture --text "Resolved auth timeout by increasing JWT expiry"
# Search memories
memento search "how did I fix the promise bug"
# Show workspace status
memento status
How Proactivity Works
Memento operates at two levels:
Always-on (zero configuration)
- Goal awareness: Every tool call is checked against active goals. If work drifts, a warning is appended.
- Auto-resume: L1 working memory (goals, context) restores from the previous session's checkpoint.
- Auto-checkpoint: Every 25 events, a full session snapshot is saved with project state and handoff prompt.
- Session diff: Each checkpoint computes the delta from the previous session (goals changed, files touched).
Activatable (via memento_configure)
- L2 enforcement: Goal alignment checks via LLM on explicit request.
- L3 daemon: File-watcher with proactive goal drift notifications.
- Autonomous agent: Background consolidation, KG extraction, dream synthesis, task generation.
- Active coercion: Deterministic code pattern enforcement.
- Consolidation/KG schedulers: Background deduplication and knowledge extraction.
Example activation sequence:
memento_project(action="set_goals", goals=["Implement auth flow", "Refactor DB layer"])
memento_configure(action="enforcement", level="level2", enabled=true)
memento_configure(action="consolidation_scheduler", enabled=true, interval_minutes=30)
memento_configure(action="autonomy", level="active")
License
Memento is released under the GNU Affero General Public License v3.0 (AGPL-3.0). If you modify Memento and offer it as a network service, you must release your modified source code under the same license.
See LICENSE for details.
Metadata
Release files for memento-mcp 1.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| memento_mcp-1.2.1.tar.gz | 459.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| memento_mcp-1.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 662.0 kB
Release files / memento_mcp-1.2.1.tar.gz
| Download URL | memento_mcp-1.2.1.tar.gz |
|---|---|
| Size | 459.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f21e75f278134bb79f663e47a63cf785a945f3790f8aea5ac72517ecce6aa99f
|
|
BLAKE2b-256 checksum How to use checksums |
53ace653297b91745e05dea244d2aaa55ae59724a35992542b5fa1ba4b29f126
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.
Transparency logRelease files / memento_mcp-1.2.1-py3-none-any.whl
| Download URL | memento_mcp-1.2.1-py3-none-any.whl |
|---|---|
| Size | 202.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1607d2bb5c2e7bc5f5a6c5f41bf9c0899225157914cee00bd6425502a8ffa425
|
|
BLAKE2b-256 checksum How to use checksums |
6a06b19c7a8c4a08f74f75b505eca08c9262670266edc93cbcadbbd65da45691
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.
Transparency logSecurity for memento-mcp 1.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for memento_mcp-1.2.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.