OpenMemory MCP
Mem0's MCP memory layer for coding agents (Claude, Cursor, VS Code, Windsurf, Codex etc.). As of Oct 2026 it is a hosted service: the MCP server runs at mcp.mem0.ai, needs a Mem0 Platform account (browser sign-in or API key, npx mcp-add installer), and memories live in the Mem0 account, not on the user's machine. The earlier local Docker OpenMemory server (openmemory/ folder) is no longer in the mem0ai/mem0 repo; self-hosting now means the general Mem0 open-source server.
Active · Verified 2026-10-29 · fresh as of 2026-10-29 · 38 cited facts, 2 with a third-party source · 2 recorded changes · Suggest a correction
At a glance
- Type
- Mem0-hosted MCP memory server (cross-tool memory) vendor fix
- Tier
- T2
- Section
- Claude Code memory mechanisms
- Latest release
- not applicable — not OSS fix
- License
- Apache-2.0 (mem0 monorepo) repo fix
- GitHub
- mem0ai/mem0 — ~67.3k stars (openmemory/ subdirectory removed from main by Oct 2026; MCP server is hosted) repo fix
- Pricing
- not applicable — not commercial fix
- Funding
- not applicable — not commercial fix
- Freshness
- 2026-10-29 fix
- Layer
- agent-infra repo fix
- Licensing
- open-source repo fix
- Developer activity
- OpenRank 25.56 (12-mo avg 24.36) · 193 participants — 2026-09 third-party fix
Memory taxonomy
- storage
- vector
- retrieval
- similarity
- persistence
- long-term
- update
- extraction
- unit
- fact
- governance
- user-controllable
- conflict
- llm-arbitrate
When to use
Optimised for: Claude-Code-native + MCP-portable memory
Anti-fit: not for non-Claude-Code clients (some are MCP-portable)
Pros & cons
Pros
MCP exposure of the OpenMemory protocol — cross-tool memory portability vision in MCP form.
Cons
Protocol still emerging; ecosystem support thin outside Mem0.
Claims & capabilities
Cross-tool memory passport: write in Claude Desktop, read in Cursor.
Technical surface
- API surface
- MCP (stdio); local server bridges to Mem0 add/search/list/delete
- Backend storage
- hybrid
- Deployment
- not applicable — not a deployable product
- Embedding model
- multiple supported
- Multi-tenancy
- namespace
- MCP
- native (first-party)
- A2A
- not supported
- OpenTelemetry
- no
Alternatives to OpenMemory MCP → live options ranked by shared design, licence, hosting and MCP support
Similar systems
Other claude code memory mechanisms in the catalog, ranked by inbound references.
- Official MCP Memory server T1
Knowledge-graph-based persistent memory MCP server — the canonical reference implementation. npx -y @modelcontextprotocol/server-memory ; configurable via MEMORY_FILE_PATH .
- Claude Code auto-memory T1
Persistent file-based memory at ~/.claude/projects/<project>/memory/ with a MEMORY.md index plus typed memory files (user / feedback / project / reference). Loaded into context across sessions.
- claude-brain T2
Claude Code plugin packaging of Memvid (see Dedicated memory layers). Wraps the Memvid .mv2 single-file store as a slash-command-installable plugin so per-project memory becomes a git-committable file inside the repo.
- Claude-CursorMemoryMCP T2
FastAPI server. RBAC + API-key auth, encryption, backup/recovery, embedding pipeline with deduplication. Only server in this list with role-based access control over pgvector.
- claude-mem T1
Hooks into Claude Code's session lifecycle; compresses tool outputs into ~500-token observations via Claude's agent SDK. SQLite + FTS5 with optional Chroma vector. "Endless Mode" compresses in-flight to extend session length. Captures what the agent did , not just what the user typed.
- claude-supermemory T2
Wraps Supermemory cloud API. Team memory shared across project members, separate from personal memories. Auto-capture on session end; per-repo config.
Sources (37 cited facts, 2 third-party)
Each fact links to the page it came from; the badge says who published it (how to read sources).
- What it is Mem0-hosted MCP memory server (cross-tool memory) vendor
- What it does & what's distinct Mem0's MCP memory layer for coding agents (Claude, Cursor, VS Code, Windsurf, Codex etc.… vendor
- Claims / benefits Cross-tool memory passport: write in Claude Desktop, read in Cursor. vendor
- Modalities text vendor
- Created 2025-03 (Mem0 launched OpenMemory in early 2025; Docker Compose self-host) vendor
- License Apache-2.0 (mem0 monorepo) repo
- GitHub mem0ai/mem0 — ~67.3k stars (openmemory/ subdirectory removed from main by Oct 2026; MCP … repo
- Founders / pedigree Mem0 (YC S24; Taranjeet Singh & Deshraj Yadav) vendor
- Memory volume / scale no scale claim — local Postgres + Qdrant vendor
- API surface MCP (stdio); local server bridges to Mem0 add/search/list/delete vendor
- Backend storage hybrid repo
- Multi-tenancy namespace repo
- Embedding model multiple supported repo
- Tombstoning hard-delete supported vendor
- Schema evolution schema with migration vendor
- Namespace primitives per-tenant vendor
- Contradiction handling LLM resolves and overwrites vendor
- Forgetting policy user-controlled forget vendor
- MCP support native (first-party) repo
- A2A support not supported vendor
- OTel no vendor
- Webhooks / events no vendor
- Import / export JSON local store repo
- Validated verticals coding agents only - Claude Code users (horizontal SWE) vendor
- Time to running <10min (plugin / MCP install) vendor
- Anti-fit not for non-Claude-Code clients (some are MCP-portable) vendor
- Optimised for Claude-Code-native + MCP-portable memory vendor
- Adjacent infrastructure requires Claude Code or MCP client; BYO storage vendor
- Pros MCP exposure of the OpenMemory protocol — cross-tool memory portability vision in MCP fo… vendor
- Cons Protocol still emerging; ecosystem support thin outside Mem0. vendor
- Project & sources mem0.ai/openmemory vendor
- adoption-accelerator yc-s24 third-party
- architecture-deployment-locus cloud vendor
- licensing-bucket open-source repo
- positioning-platform-vs-product product vendor
- taxonomy-three-layer-rollup agent-infra repo
- developer-activity-opendigger {"activity":442.12,"as_of":"2026-09","openrank_12mo":24.36,"openrank_current":25.56,"par… third-party
What changed
Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)
Related systems
References (4)
- Anthropic Claude (foundation models) depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
- Mem0 builds on — Local-first self-hosted Mem0 variant. Shared memory layer bridges Claude Desktop, Cursor, and Windsurf in one session.
- Model Context Protocol (MCP spec) depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
- Qdrant builds on — Local Postgres + Qdrant cross-tool memory