mcp-memory-service
★ 2.0k
vs
engrim
★ 299
mcp-memory-service vs engrim
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.; engrim: Engrim is a universal, local-first SQLite memory engine specifically engineered for autonomous AI coding agents, designed to solve the '200,000-token context window trap'. It provides high-precision, curated episodic working memory, allowing developers to switch between various models and environments on the same codebase without losing architectural decisions or project state.
01
TL;DR
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.
engrimMemory & Context · ★ 299
Maintaining Project Context Across Agent Sessions: Developers can use Engrim to prevent LLMs from losing architectural decisions, user constraints, or project state when chat sessions are cleared or models are switched.
02
Side-by-Side Comparison
Field
mcp-memory-serviceengrimCategory
Memory & Context
Memory & Context
Stars
★ 2.0k
★ 299
License
Apache-2.0
MIT
Install Command
pip install mcp-memory-service
pip install engrim
Updated
1d ago
3w ago
Open Source
Yes
Yes
Tags
AI Memory, Context Management, Developer Tools
Episodic Memory, LLM Context Management, AI Agents
03
Features
mcp-memory-service01Persistent Memory
02Smart Retrieval
03Multi-Client Compatibility
04Cloud Sync (Optional)
05Web Dashboard
engrim01Precision Working Memory: Replaces raw transcript replay with ~4,000 characters of high-precision, curated episodic memory, injected at boot with zero attention dilution.
02Cross-Model/Agent Compatibility: Provides a universal substrate for memory, allowing decisions made in one agent (e.g., Claude Code) to be visible and usable in others (e.g., Antigravity, Cursor).
03Local-First & Private Storage: Stores all memories locally in a SQLite file (~/.engrim/memory.db) with WAL mode and POSIX 0600 permissions, ensuring 100% privacy with no cloud sync or telemetry.
04Self-Healing Diagnostics: The `engrim doctor --fix` command verifies all hooks and installs portable PATH fallbacks, ensuring reliable operation across machines and OSes without silent failures.
05Hybrid Retrieval & Minder: Employs a hybrid lexical (BM25) and vector (model2vec) search for efficient and relevant memory recall in approximately 30ms.
04
Use Cases
mcp-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.
engrim↳Maintaining Project Context Across Agent Sessions: Developers can use Engrim to prevent LLMs from losing architectural decisions, user constraints, or project state when chat sessions are cleared or models are switched.
↳Collaborative Multi-Agent Development: Enabling multiple AI coding agents (e.g., Antigravity, Claude Code, Cursor) to work on the same codebase and share a consistent, evolving memory store.
↳Continue-As-Clear Workflow: Allows users to clear their agent's context window at any time, with Engrim automatically re-injecting the active memory pack for seamless continuation without memory loss.
↳Auditing Agent Provenance: Tracking which agent made specific architectural decisions or added facts to the project's memory, enhancing transparency in multi-agent environments.
05
Best For
mcp-memory-serviceEssentialTrending
engrim—
FAQ
FAQ
What is the difference between mcp-memory-service and engrim?
Both mcp-memory-service and engrim are in the Memory & Context category. mcp-memory-service has 2.0k stars, while engrim has 299 stars.
Which is better, mcp-memory-service or engrim?
The best choice depends on your use case. Choose mcp-memory-service if Maintaining AI context across multiple development sessions., and engrim if Maintaining Project Context Across Agent Sessions: Developers can use Engrim to prevent LLMs from losing architectural decisions, user constraints, or project state when chat sessions are cleared or models are switched..
Is mcp-memory-service free or open source?
Yes, mcp-memory-service is open source on GitHub (Apache-2.0).
Is engrim free or open source?
Yes, engrim is open source on GitHub (MIT).
Cloud Infrastructure
AdDeploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.
→