claude-supermemory
https://github.com/supermemoryai/claude-supermemory
Wraps Supermemory cloud API. Team memory shared across project members, separate from personal memories. Auto-capture on session end; per-repo config.
Active · Verified 2026-10-22 · fresh as of 2026-10-22 · 39 cited facts, 1 with a third-party source · 1 recorded change · Suggest a correction
At a glance
- Type
- Team-scope memory plugin repo fix
- Tier
- T2
- Section
- Claude Code memory mechanisms
- Latest release
- v0.0.2 2026-02-09 repo fix
- GitHub
- supermemoryai/claude-supermemory — ~2.8k stars repo fix
- Funding
- not applicable — not commercial fix
- Freshness
- 2026-10-22 fix
- Layer
- agent-infra repo fix
- Licensing
- open-source repo fix
- Protocols
- mcp-server repo fix
- Developer activity
- OpenRank 1.5 (12-mo avg 1.56) · 9 participants — 2026-09 third-party 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
Claude Code plugin packaging Supermemory for per-project memory.
Cons
Plugin-distributed product layered on a smaller memory layer than Mem0 / Graphiti.
Claims & capabilities
Distributed via Claude Code plugin marketplace. Requires Supermemory Pro.
Technical surface
- API surface
- searched not found
- Backend storage
- searched not found
- Deployment
- Supermemory cloud API by default (API key); local self-host option via npx supermemory local
- Embedding model
- searched not found
- Multi-tenancy
- searched not found
- MCP
- no — implemented as Claude Code plugin hooks (Node.js scripts), not an MCP server
- A2A
- not supported
- OpenTelemetry
- no
Alternatives to claude-supermemory → 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.
- codebase-memory-mcp (DeusData) T1
High-performance MCP server building persistent code knowledge graphs via AST. 155 languages via vendored tree-sitter; SQLite + WAL; single static binary; zero runtime deps. Knowledge graph: Project/Package/File/Module/Class/Function/Method/Interface/Enum/Type/Route/Resource nodes; CALLS/IMPORTS/DEFINES/IMPLEMENTS/INHERITS/HTTP_CALLS/ASYNC_CALLS/EMITS/LISTENS_ON/DATA_FLOWS/SIMILAR_TO/SEMANTICALLY_RELATED edges. 14 MCP tools incl. Cypher-like query.
Sources (38 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 it is Team-scope memory plugin repo
- What it does & what's distinct Wraps Supermemory cloud API. Team memory shared across project members, separate from pe… repo
- Claims / benefits Distributed via Claude Code plugin marketplace. Requires Supermemory Pro. repo
- Modalities text repo
- Created 2026-01 repo
- Latest release v0.0.2 2026-02-09 repo
- License MIT repo
- GitHub supermemoryai/claude-supermemory — ~2.8k stars repo
- Mindshare 2.6k GitHub stars; small but growing Claude Code ecosystem signal repo
- Pricing requires Supermemory Pro (pricing not publicly listed; contact sales) repo
- Deployment Supermemory cloud API by default (API key); local self-host option via npx supermemory l… vendor
- Founders / pedigree Supermemory (Dhravya Shah, solo founder; 19; Google AI-backed) repo
- Memory volume / scale cloud-managed; no published per-user cap repo
- Schema evolution schema with migration repo
- Namespace primitives per-tenant repo
- Contradiction handling LLM resolves and overwrites repo
- MCP support no — implemented as Claude Code plugin hooks (Node.js scripts), not an MCP server vendor
- A2A support not supported repo
- OTel no repo
- Webhooks / events no repo
- Import / export JSON via Supermemory REST vendor
- Validated verticals coding agents only - Claude Code users (horizontal SWE) repo
- Time to running <10min (plugin / MCP install) repo
- Anti-fit not for non-Claude-Code clients (some are MCP-portable) repo
- Optimised for Claude-Code-native + MCP-portable memory repo
- Adjacent infrastructure requires Claude Code or MCP client; BYO storage repo
- Pros Claude Code plugin packaging Supermemory for per-project memory. repo
- Cons Plugin-distributed product layered on a smaller memory layer than Mem0 / Graphiti. repo
- Project & sources GitHub supermemoryai/claude-supermemory repo
- commit-trajectory [{"ym":"2026-01","cum":19},{"ym":"2026-02","cum":40},{"ym":"2026-03","cum":45},{"ym":"20… repo
- cost-pricing-model subscription repo
- cost-last-verified 2026-06-29 repo
- architecture-deployment-locus cloud repo
- licensing-bucket open-source repo
- positioning-platform-vs-product product repo
- taxonomy-three-layer-rollup agent-infra repo
- developer-activity-opendigger {"activity":17.25,"as_of":"2026-09","openrank_12mo":1.56,"openrank_current":1.5,"partici… third-party
- protocol-support mcp-server repo
What changed
Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)
- 2026-10-22
- License “Unlicensed” → “MIT” source
- Deployment “cloud — Supermemory managed API; no self-host option” → “Supermemory cloud API by default (API key); local self-host option via npx supermemory local” source
- MCP support “native (first-party)” → “no — implemented as Claude Code plugin hooks (Node.js scripts), not an MCP server” source
Related systems
References (3)
- Anthropic Claude (foundation models) depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
- Model Context Protocol (MCP spec) depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
- Supermemory builds on — Claude Code plugin packaging Supermemory for per-project memory.