Mem0 MCP (official)

https://github.com/mem0ai/mem0-mcp

Archived 2026-03-24 (read-only); README now points to Mem0's official cloud-hosted MCP server at mcp.mem0.ai/mcp. Mem0's managed cloud API exposed as MCP tools. Semantic search + CRUD on memories scoped by user / agent / session. Cloud-hosted MCP endpoint — no local infrastructure required.

Archived. repository archived (read-only) Source · Alternatives and migration notes →

Archived · Verified 2026-10-29 · fresh as of 2026-10-29 · 52 cited facts, 1 with a third-party source · 2 recorded changes · Suggest a correction

At a glance

Tier
T1
Created
2025-02 repo fix
Latest release
no releases fix
License
Apache-2.0 repo fix
Funding
not applicable — not commercial fix
Freshness
2026-10-29 fix
Layer
agent-infra repo fix
Licensing
open-core repo fix

Memory taxonomy

storage
vector
retrieval
similarity
persistence
long-term
update
extraction
unit
fact
governance
opaque
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 server that brings the Mem0 layer into any MCP-compatible agent — including Claude Code — without rewriting code.

Cons

Inherits Mem0's tradeoffs (extraction approach, opaque eviction); MCP surface adds one more network hop on every memory call.

Claims & capabilities

v0.2.1 (Dec 2025). PyPI: mem0-mcp-server .

Technical surface

API surface
MCP (stdio); add_coding_preference / search_coding_preferences / get_all_coding_preferences
Backend storage
hybrid
Deployment
superseded — use Mem0's hosted MCP endpoint (mcp.mem0.ai/mcp) or the mem0-mcp-server PyPI package
Embedding model
multiple supported
Multi-tenancy
namespace
MCP
native (first-party)
A2A
not supported
OpenTelemetry
searched not found

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 (51 cited facts, 1 third-party)

Each fact links to the page it came from; the badge says who published it (how to read sources).

What changed

Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)

  1. 2026-10-22
    • Deployment “cloud API (managed by Mem0); MCP local install pointing to Mem0 cloud” → “superseded — use Mem0's hosted MCP endpoint (mcp.mem0.ai/mcp) or the mem0-mcp-server PyPI package” source
    #195
  2. 2026-05-16
    • Lifecycle first recorded as “archived”
    #56

Related systems

References (3)

  • Anthropic Claude (foundation models) depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • Mem0 builds on — Mem0's managed cloud API exposed as MCP tools.
  • Model Context Protocol (MCP spec) depends on at runtime — MCP server that brings the Mem0 layer into any MCP-compatible agent — including Claude Code — without rewriting code.