Cognee MCP

https://github.com/topoteretes/cognee

"Cognify" extracts entities and relationships into a structured graph. Saves interaction patterns as coding rules; uses both vector and graph DBs. Bundled in Cognee v0.3.5+.

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
2023-08 repo fix
Latest release
v1.6.5 (2026-10-16) registry 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 repo fix
Deployment locus
hybrid repo fix
Platform vs product
platform repo fix
Maturity
beta registry fix
SDK languages
python, rust, typescript repo fix
Protocols
mcp-server vendor 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

MCP server that brings Cognee's ECL pipeline into any MCP-compatible agent.

Cons

Setup more involved than embedded SDK; inherits Cognee's tradeoffs.

Claims & capabilities

Benchmarks claim superiority over Mem0, LightRAG, Graphiti on multi-hop QA.

Technical surface

API surface
MCP (stdio + SSE); cognify/search/codify tool suite
Backend storage
hybrid (vector + graph)
Deployment
self-hosted (local vector + graph DB); cloud option exists (topoteretes managed)
Embedding model
multiple supported
Multi-tenancy
namespace
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 “v1.0.8 2026-05-06” → “v1.6.5 (2026-10-16)” source
    • Pricing “free / open source (Apache-2.0) for self-hosted; cloud tier pricing not published” → “OSS (Apache-2.0) self-hosted; Cognee Cloud managed service (pricing not on README); some production components (Postgres graph store) are licensed products” source
    #195

Related systems

References (3)