engram-mcp

★ 18

mneme

★ 171

engram-mcp vs mneme

Q: Which is better, engram-mcp or mneme?

By GitHub stars, mneme has more community adoption, but the best choice depends on your specific use case.

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.; mneme: dsh-mneme is a DeepSeek Harness plugin providing sophisticated cross-session memory for LLMs. It not only stores information but actively manages it through features like background deduplication, conflict resolution, and auditable history, ensuring AI remembers past interactions.

TL;DR

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.

Read engram-mcp full review →

mnemeMemory & Context · ★ 171

Continuing project discussions across multiple sessions without repetition.

Read mneme full review →

Side-by-Side Comparison

Field

engram-mcp

mneme

Features

engram-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.

mneme

01Replayable and Auditable Memory

02Conflict Resolution with Human Oversight

03Agent and Workspace Memory Isolation

04Offline-first Local Semantic Search

05Automatic Background Memory Consolidation

Use Cases

engram-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.

mneme

↳Continuing project discussions across multiple sessions without repetition.

↳Persisting AI's understanding of user preferences and coding habits long-term.

↳Automatic archiving and retrieval of organized research notes after closing chat windows.

FAQ

What is the difference between engram-mcp and mneme?

Both engram-mcp and mneme are in the Memory & Context category. engram-mcp has 18 stars, while mneme has 171 stars.

Which is better, engram-mcp or mneme?

The best choice depends on your use case. Choose engram-mcp if Developers can capture session state and structured notes (decisions, todos, blockers) at the end of a coding session for seamless handover., and mneme if Continuing project discussions across multiple sessions without repetition..

Is engram-mcp free or open source?

Yes, engram-mcp is open source on GitHub (Apache-2.0).

Is mneme free or open source?

Yes, mneme is open source on GitHub (MIT).

Cloud Infrastructure

Deploy on DigitalOcean

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

Claim $200 Free Credit

→

Alternatives to engram-mcp →Alternatives to mneme →engram-mcp details →mneme details →

TL;DR

Side-by-Side Comparison

Features

Use Cases

FAQ

Deploy on DigitalOcean

Related