Catalog Systems Claude Code memory mechanisms mcp-knowledge-graph

mcp-knowledge-graph

https://github.com/shaneholloman/mcp-knowledge-graph

KG-based local fork of @modelcontextprotocol/server-memory . Avoids ephemeral npx installs; supports named databases for topic scoping; user-controlled memory path. Drop-in for teams that want the official KG model without npx churn.

Active · Verified 2026-10-22 · fresh as of 2026-10-22 · 42 cited facts, 0 with a third-party source · Suggest a correction

At a glance

Type
Stable local fork of official MCP memory repo fix
Tier
T2
Section
Claude Code memory mechanisms
Created
2024-12 repo fix
Latest release
v1.3.2 2025-12-22 repo fix
License
MIT repo fix
GitHub
shaneholloman/mcp-knowledge-graph — ~889 stars, last commit n/a repo fix
Pricing
free / open source (MIT) 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
local repo fix
Platform vs product
product repo fix
Protocols
mcp-server repo fix

Memory taxonomy

storage
graph
retrieval
graph-traversal
persistence
long-term
update
overwrite
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 exposing graph-shaped memory — closer to Graphiti's model with smaller footprint.

Cons

Smaller community than Graphiti MCP; less polished documentation.

Claims & capabilities

Practical local installation pattern.

Technical surface

API surface
searched not found
Backend storage
searched not found
Deployment
local (Node.js MCP server; local JSON file storage)
Embedding model
searched not found
Multi-tenancy
searched not found
MCP
native (first-party) — fork of official memory server
A2A
not supported
OpenTelemetry
no

Alternatives to mcp-knowledge-graph → 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 (41 cited facts, 0 third-party)

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

Related systems

References (3)