mcp-memory-service logo
mcp-memory-service
★ 2.0k
vs
engram-mcp logo
engram-mcp
★ 18

mcp-memory-service vs engram-mcp

mcp-memory-service: MCP Memory Service prevents AI assistants from losing context across sessions by automatically capturing project architecture, decisions, and code patterns. This ensures your AI always remembers essential information, eliminating the need for repetitive re-explanation and saving valuable development time.; engram-mcp: Engram is an MCP server that provides persistent, Git-aware session memory for coding agents, allowing structured handoffs between sessions and branches. It helps agents retain context, decisions, and tasks, backed by local SQLite and ONNX embeddings without cloud dependencies.

01

TL;DR

mcp-memory-service logo
mcp-memory-serviceMemory & Context · ★ 2.0k
When to choose:
  • You use Claude Code, Claude Desktop, Cursor, VS Code or another MCP client and want chat sessions to stop starting from zero.
  • You want a choice of storage: local SQLite, Cloudflare for multi-device sync, or a hybrid.
  • You need team features: the README lists OAuth, a dashboard and document ingestion.
When to skip:
  • Your problem is codebase navigation rather than conversation memory; a code-graph tool or a project scaffold fits better.
  • You handle sensitive material and cannot put it in a persistent store, especially with cloud sync.
  • You want a short README to start from: it mixes release notes with documentation.
engram-mcp logo
engram-mcpMemory & Context · ★ 18

Developers can capture session state and structured notes (decisions, todos, blockers) at the end of a coding session for seamless handover.

02

Side-by-Side Comparison

Field
mcp-memory-service logomcp-memory-service
engram-mcp logoengram-mcp
Category
Memory & Context
Memory & Context
Stars
★ 2.0k
★ 18
License
Apache-2.0
Apache-2.0
Install Command
pip install mcp-memory-service
cargo install engram_mcp
Updated
1d ago
5d ago
Open Source
Yes
Yes
Tags
AI Memory, Context Management, Developer Tools
Git-aware Memory, Coding Agent Tools, Context Management
03

Features

mcp-memory-service logomcp-memory-service
01Persistent Memory
02Smart Retrieval
03Multi-Client Compatibility
04Cloud Sync (Optional)
05Web Dashboard
engram-mcp logoengram-mcp
01Provides Git-aware session memory that scopes context to specific git branches, preventing information leakage.
02Enables structured session handoffs to capture summaries, decisions, todos, blockers, and mental models for continuity.
03Offers local-first persistent storage using SQLite and ONNX embeddings, ensuring no cloud or LLM calls are needed for storage.
04Features advanced memory retrieval with hybrid scoring (cosine, recency, importance), hierarchical clustering, and branch-aware queries.
05Includes automated memory management capabilities such as decay, semantic deduplication, and auto-pruning of low-relevance memories.
04

Use Cases

mcp-memory-service logomcp-memory-service
↳Maintaining AI context across multiple development sessions.
↳Avoiding repetitive explanations of project architecture and tech stack to AI.
↳Enhancing continuous and intelligent collaboration with AI assistants.
engram-mcp logoengram-mcp
↳Developers can capture session state and structured notes (decisions, todos, blockers) at the end of a coding session for seamless handover.
↳Automatically retrieve relevant context and prior session details when resuming work on the same or a different Git branch.
↳LLM agents can proactively load relevant memories at the start of a conversation, building context from recent Git activity.
↳Passively capture coding decisions and session summaries into memory through integrated hooks without explicit tool calls.
↳Maintain a centralized, searchable, and structured memory of project-specific decisions, recurring patterns, and past debug solutions.
05

Best For

mcp-memory-service logomcp-memory-service
EssentialTrending
engram-mcp logoengram-mcp
—
FAQ

FAQ

What is the difference between mcp-memory-service and engram-mcp?
Both mcp-memory-service and engram-mcp are in the Memory & Context category. mcp-memory-service has 2.0k stars, while engram-mcp has 18 stars.
Which is better, mcp-memory-service or engram-mcp?
The best choice depends on your use case. Choose mcp-memory-service if Maintaining AI context across multiple development sessions., and engram-mcp if Developers can capture session state and structured notes (decisions, todos, blockers) at the end of a coding session for seamless handover..
Is mcp-memory-service free or open source?
Yes, mcp-memory-service is open source on GitHub (Apache-2.0).
Is engram-mcp free or open source?
Yes, engram-mcp is open source on GitHub (Apache-2.0).
Cloud Infrastructure
Ad

Deploy on DigitalOcean

Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.

Claim $200 Free Credit
→

Related