Already inside Claude Code, Gemini CLI, or Aider? Paste one of these prompts and let the agent set it up for you:
Claude Code:
Install m3-memory for persistent memory. Run: pip install m3-memory
Then add {"mcpServers":{"memory":{"command":"mcp-memory"}}} to my
~/.claude/settings.json under "mcpServers". Make sure Ollama is running
with nomic-embed-text. Then use /mcp to verify the memory server loaded.
Gemini CLI:
Install m3-memory for persistent memory. Run: pip install m3-memory
Then add {"mcpServers":{"memory":{"command":"mcp-memory"}}} to my
~/.gemini/settings.json under "mcpServers". Make sure Ollama is running
with nomic-embed-text.
Aider / Any MCP agent:
Install m3-memory for persistent memory. Run: pip install m3-memory
Then add {"mcpServers":{"memory":{"command":"mcp-memory"}}} to the
MCP config file for this agent. Make sure Ollama is running with
nomic-embed-text.
After install, test it:
Write a memory: "M3 Memory installed successfully on [today's date]"
Then search for: "M3 install"
The Problem
Every new session, your AI agent has amnesia. It forgets your project structure, your preferences, the decisions you made together yesterday. You paste the same context. You re-explain the same architecture. You correct the same mistakes.
When facts change — a port number, a dependency version — there's no mechanism to update what the agent "knows." Contradictions accumulate silently until something breaks.
With M3 Memory
Your agents remember. Architecture decisions, server configs, debugging history, your preferences — all searchable, all persistent across sessions and devices.
When facts change, M3 detects the contradiction, updates the record, and preserves the full history. No stale data. No manual cleanup. You just talk to your agent, and it knows what it should know.
The Moment It Clicks
Session
You say
Agent response
Session 1
"Our API server runs on port 8080."
Stored.
Session 2 (3 days later)
"We moved the API to port 9000."
Contradiction detected. Updated. History preserved.
Session 3 (a week later)
"What port is the API on?"
Without M3: "I don't have that information. Could you tell me?"
With M3: "Port 9000. (Updated from 8080 — change recorded March 12th.)"
No prompts. No manual logic. Automatic contradiction resolution with full history.
Who This Is For
For you if...
Not for you if...
You use Claude Code, Gemini CLI, Aider, or any MCP agent
You're building LangChain/CrewAI pipelines — see Mem0
You want memory that survives across sessions + devices
You prefer local-first: no cloud, no API costs, works offline
You only need short-term chat context in a single session
You care about privacy and data ownership
Use Cases
Coding agents
Remember architecture decisions, configs, and debugging steps across sessions
Personal assistants
Persist user preferences, goals, and history long-term
Dev workflows
Track environment changes, server configs, and fixes automatically
Multi-device setups
Write a memory on your MacBook, pick it up on your Windows desktop — same knowledge graph, synced locally
Features
Hybrid Search
Three-stage pipeline: FTS5 keyword matching, semantic vector similarity, and MMR diversity re-ranking. Better recall than vector-only search, especially for technical content with exact names and versions.
Automatic Contradiction Detection
Write conflicting information and M3 detects it automatically. The outdated memory is superseded via bitemporal versioning, a supersedes relationship is recorded, and the full history is preserved.
Bitemporal History
Query as_of="2026-01-15" to see exactly what your agent believed on any past date. Every change is tracked with both the time the fact was true and the time it was recorded.
Knowledge Graph
Related facts are linked on write when cosine similarity exceeds 0.7. Eight relationship types (related, supports, contradicts, extends, supersedes, references, consolidates, message). Traverse up to 3 hops with memory_graph.
Cross-Device Sync
Bi-directional delta sync across SQLite, PostgreSQL, and ChromaDB. Write on your MacBook, continue on your Windows desktop. No cloud intermediary.
GDPR Built-In
gdpr_forget (Article 17 — Right to Erasure) and gdpr_export (Article 20 — Data Portability) as native MCP tools.
Fully Local + Private
Local embeddings via Ollama, LM Studio, or any OpenAI-compatible endpoint. Zero cloud calls. Zero API costs. Works completely offline.
Self-Maintaining
Automatic decay, expiry purging, orphan pruning, deduplication, and retention enforcement. Old memories consolidate into LLM-generated summaries.
Core Tools
Start with three — memory_write, memory_search, and memory_update — that covers 90% of daily use. The rest is there when you need it.
Tool
What it does
memory_write
Store a memory — facts, decisions, preferences, configs, observations
memory_search
Retrieve relevant memories using hybrid search
memory_suggest
Same as search, with full score breakdown (vector, BM25, MMR)
Your AI should remember. Your data should stay yours.
M3 Memory: the foundation for agents that don't forget.
Release History
Version
Changes
Urgency
Date
v2026.6.1.0
Faster, more resilient, more efficient and more robust while maintaining backward compatibility. FIPS 140-3 ready. Local first, cloud capable memory engine.
High
6/1/2026
v2026.5.30.0
## Entity coalescing v2 (reversible apply/unapply) + catalog registration + CLI exit-code fix ### Added - **Entity-coalescing v2 — reversible overlay apply/unapply** (`files_entity_coalesce_apply` / `files_entity_coalesce_unapply` MCP tools; `entity-coalesce-apply` / `entity-coalesce-unapply` CLI). Materializes reviewed/auto-merge candidates as a reversible `same_as` + shared-`cluster_id` overlay — members are never deleted, the canonical view is a read-time projection, a deterministic represe
High
5/30/2026
v2026.5.21.0
## v2026.5.21.0 — green-CI maintenance release First release on fully-green CI (Lint, Type Check, Security, and Tests on ubuntu/macos/windows all passing). ### Fixes - **F821 undefined-name errors (30)** — the Phase 7+8 modularization left dangling symbol references in `memory/write.py`, `search.py`, `enrich.py`; restored the missing imports and re-exports. - **Mypy type errors (64)** — resolved across `bin/`: missing `memory_core` re-exports, `m3_core_rs` typing, exception-base annotations, h
## Highlights - **GitHub Actions Node-24 upgrade.** Pins every workflow action to its latest Node-24-compatible release-tag SHA so CI keeps working past GitHub's Node 20 removal on 2026-09-16. | action | from | to | | --- | --- | --- | | `actions/checkout` | v4 | **v6.0.2** | | `actions/setup-python` | v5 | **v6.2.0** | | `actions/upload-artifact` | v4 | **v7.0.1** | | `actions/download-artifact` | v4 | **v8.0.1** | - **New banner art** at `docs/M3-banner.jpg`. ## Migration notes Major-vers
High
5/7/2026
v2026.5.1.1
## Highlights This release rolls up roughly five weeks of ingest-pipeline work plus a documentation, hygiene, and security pass. - **Tool count: 66 → 72.** Six new MCP tools: `entity_search`, `entity_get`, `extract_pending`, `enrich_pending`, `memory_search_routed`, `memory_write_from_file`. See [`docs/MCP_TOOLS.md`](https://github.com/skynetcmd/m3-memory/blob/main/docs/MCP_TOOLS.md). - **`bin/m3_enrich.py` CLI** — first-class user-facing enrichment over the Observer/Reflector pipeline. Durabl
High
5/1/2026
v2026.4.24.12
## Two pain points caught testing the plugin on Windows ### Plugin commands now self-resolve Caught when `/m3:doctor` ran on Windows: `pip install --user m3-memory` puts `mcp-memory.exe` at `%APPDATA%\Python\Python<NN>\Scripts`, which is **not** on Windows PATH by default. The plugin command had Claude spelunking through 8 fallback paths before finding `python -m m3_memory.cli` works. `/m3:doctor`, `/m3:status`, and `/m3:install` now explicitly list the resolver chain in their command bodies:
High
4/25/2026
v2026.4.20
## Fixes - Resolve SQLite deadlock in `memory_consolidate` via connection reuse in `memory_link_impl` - Resolve database contention and sync hangs on large DBs (migration timeout bump, SAVEPOINT-wrapped pg_sync, VACUUM skip for >500MB DBs, WAL contention fix in `record_history`) ## Features - `memory_search` gains `recency_bias` (float) and `adaptive_k` (bool) params - `conversation_search` auto-pairs user turns with adjacent assistant replies (0.85x score) - `precedes` / `follows` added to `VA
High
4/17/2026
v2026.4.19
Fix PyPI rendering: absolute URLs for all links and images, markdown banner fallback, incorporate doc edits.
Docs-only release: Unicode emoji rendering fix for PyPI page. All markdown files now use Unicode emoji characters instead of GitHub `:shortcode:` syntax, which PyPI's renderer doesn't support.
High
4/16/2026
v2026.4.16
## What's new since v2026.4.8 - **46 MCP tools** (was 25) — added agent registry, handoffs, task trees, notifications, scoped memory - **89% on LongMemEval-S** (445/500) — full writeup with methodology and caveats in `benchmarks/longmemeval/README.md` - **Multi-agent orchestration** — coordinate multiple agents on shared local memory with built-in handoffs, inbox, and task assignment - **Conversation grouping** — `conversation_id` on write/search/update for session-aware retrieval - **Refresh l
High
4/16/2026
v2026.4.6
## What's New M3 Memory is a local-first agentic memory layer for MCP agents — 25 tools, hybrid search (FTS5 + vector + MMR), contradiction detection, cross-device sync, GDPR-ready, 100% local. ## Install ```bash pip install m3-memory ``` Or clone for development: ```bash git clone https://github.com/skynetcmd/m3-memory.git cd m3-memory pip install -r requirements.txt ``` ## Highlights - **25 MCP tools** — write, search, link, graph, verify, sync, export, and more - **Hybrid search** — FT
High
4/10/2026
v1.0.03
 Intelligent Agentic Memory Most agent memory systems solve one problem well — vector search, or persistence, or multi-tenancy. M3 Memory solves all of them in a single, tested, local-first package that runs on your hardware without sending a byte to the cloud. *Here's how it actually gets used.* You're working on your MacBook at a coffee shop, asking Claude to debug a deployment issue. It remembers
Medium
4/7/2026
Dependencies & License Audit
Loading dependencies...
Similar Packages
zotero-mcp-lite🚀 Run a high-performance MCP server for Zotero, enabling customizable workflows without cloud dependency or API keys.main@2026-06-01
sqltools_mcp🔌 Access multiple databases seamlessly with SQLTools MCP, a versatile service supporting MySQL, PostgreSQL, SQL Server, DM8, and SQLite without multiple servers.main@2026-06-07
claude-code-configClaude Code skills, architectural principles, and alternative approaches for AI-assisted developmentmain@2026-06-06
antigravity-awesome-skills🌌 Explore 255+ essential skills for AI coding assistants like Claude Code and GitHub Copilot to enhance your development workflow.main@2026-06-05
mcp-videoVideo editing MCP server for AI agents. 83 tools, 858 tests collected, 3 interfaces. Works with Claude Code, Cursor, and any MCP client. Local, fast, free.v1.5.1
More in MCP Servers
PlanExeCreate a plan from a description in minutes
automagik-genieSelf-evolving AI agent orchestration framework with Model Context Protocol support
agentroveYour own Claude Code UI, sandbox, in-browser VS Code, terminal, multi-provider support (Anthropic, OpenAI, GitHub Copilot, OpenRouter), custom skills, and MCP servers.
ProxmoxMCP-PlusEnhanced Proxmox MCP server with advanced virtualization management and full OpenAPI integration.