AgentIndex icon
AgentIndex
memory-bank-mcp logo
memory-bank-mcp
★ 921
vs
engrim logo
engrim
★ 299

memory-bank-mcp vs engrim

memory-bank-mcp: The Memory Bank MCP Server provides a centralized service for managing memory bank files remotely. It supports multiple projects, ensures file structure consistency, and offers secure, isolated access via the MCP protocol.; 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

memory-bank-mcp logo
memory-bank-mcpMemory & Context · ★ 921

Centralized management of AI model context across various projects.

Read memory-bank-mcp full review →
engrim logo
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.

Read engrim full review →
02

Side-by-Side Comparison

Field
memory-bank-mcp logomemory-bank-mcp
engrim logoengrim
Category
Memory & Context
Memory & Context
Stars
★ 921
★ 299
License
MIT
MIT
Install Command
npx -y @smithery/cli install @alioshr/memory-bank-mcp --client claude
pip install engrim
Updated
1y ago
3w ago
Open Source
Yes
Yes
Website
↗ Visit
↗ Visit
GitHub
↗ GitHub
↗ GitHub
Tags
MCP, Memory Bank, Node.js
Episodic Memory, LLM Context Management, AI Agents
03

Features

memory-bank-mcp logomemory-bank-mcp
01Multi-project memory bank management
02Remote access to memory banks via MCP protocol
03Consistent file structure enforcement and validation
04Project isolation for enhanced security
05Comprehensive CRUD operations for memory bank files
engrim logoengrim
01Precision 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

memory-bank-mcp logomemory-bank-mcp
↳Centralized management of AI model context across various projects.
↳Providing remote memory bank capabilities to multiple AI assistants or development tools.
↳Integrating with AI clients like Claude, Cursor, or VS Code extensions to enhance their memory functions.
engrim logoengrim
↳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.
FAQ

FAQ

What is the difference between memory-bank-mcp and engrim?
Both memory-bank-mcp and engrim are in the Memory & Context category. memory-bank-mcp has 921 stars, while engrim has 299 stars.
Which is better, memory-bank-mcp or engrim?
The best choice depends on your use case. Choose memory-bank-mcp if Centralized management of AI model context across various projects., 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 memory-bank-mcp free or open source?
Yes, memory-bank-mcp is open source on GitHub (MIT).
Is engrim free or open source?
Yes, engrim is open source on GitHub (MIT).
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

Alternatives to memory-bank-mcp →Alternatives to engrim →memory-bank-mcp details →engrim details →