mcp-memory-service (doobidoo)

https://github.com/doobidoo/mcp-memory-service

SQLite-Vec default, Cloudflare hybrid for production. Typed edges (causes, fixes, contradicts). Autonomous consolidation compresses old memories. SSE real-time notifications + D3.js visualisation dashboard. Agent-pipeline focused (LangGraph, CrewAI, AutoGen).

Active · Verified 2026-10-22 · fresh as of 2026-10-22 · 46 cited facts, 1 with a third-party source · 1 recorded change · Suggest a correction

At a glance

Tier
T2
Created
2024-12 repo fix
Latest release
v11.15.0 (2026-10-03) repo fix
License
Apache-2.0 repo fix
Funding
not applicable — not commercial fix
Freshness
2026-10-22 fix
Layer
agent-infra repo fix
Licensing
open-source vendor fix
Deployment locus
local repo fix
Platform vs product
platform repo fix
Maturity
ga registry fix
SDK languages
python, rest repo fix
Protocols
mcp-server repo fix

Memory taxonomy

storage
graph
retrieval
graph-traversal
persistence
long-term
update
extraction
unit
fact
governance
inspectable
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

OSS MCP memory server with vector + KV backends; flexible deployment options.

Cons

Author-maintained; documentation uneven; not actively heavily adopted.

Claims & capabilities

Self-compresses aging memories to address context-window pressure.

Technical surface

API surface
searched not found
Backend storage
searched not found
Deployment
Local/self-hosted — SQLite-vec local; Cloudflare, Hybrid or Milvus backends; no managed cloud
Embedding model
searched not found
Multi-tenancy
searched not found
MCP
native (first-party)
A2A
not supported
OpenTelemetry
no

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 (45 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
    • Latest release “v10.49.4 2026-05-05” → “v11.15.0 (2026-10-03)” source
    • Deployment “local — SQLite-Vec default; Cloudflare hybrid for production; no managed cloud” → “Local/self-hosted — SQLite-vec local; Cloudflare, Hybrid or Milvus backends; no managed cloud” source
    #195

Related systems

References (5)