AgentIndex icon
AgentIndex
memory-bank-mcp logo
memory-bank-mcp
★ 920
vs
deja-vu logo
deja-vu
★ 1.3k

memory-bank-mcp vs deja-vu

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.; deja-vu: Deja-vu is a zero-dependency, local-first binary that indexes and makes searchable the historical sessions of various AI coding agents. It acts as a universal memory layer, allowing agents to recall past solutions and context efficiently, even from before its installation.

01

TL;DR

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

Centralized management of AI model context across various projects.

Read memory-bank-mcp full review →
deja-vu logo
deja-vuMemory & Context · ★ 1.3k

Reusing solutions from past agent conversations to avoid re-debugging or re-implementing.

Read deja-vu full review →
02

Side-by-Side Comparison

Field
memory-bank-mcp logomemory-bank-mcp
deja-vu logodeja-vu
Category
Memory & Context
Memory & Context
Stars
★ 920
★ 1.3k
License
MIT
MIT
Install Command
npx -y @smithery/cli install @alioshr/memory-bank-mcp --client claude
curl -fsSL https://raw.githubusercontent.com/vshulcz/deja-vu/main/install.sh | sh
Updated
1y ago
1d ago
Open Source
Yes
Yes
Website
↗ Visit
↗ Visit
GitHub
↗ GitHub
↗ GitHub
Tags
MCP, Memory Bank, Node.js
AI Agent Memory, Session Search, Code Assistant
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
deja-vu logodeja-vu
01Fast, Retroactive Session Search
02Automatic AI Agent Memory Recall
03Cross-Machine Memory Synchronization
04Seamless Agent Context Handoff
05Automated Sensitive Data Redaction
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.
deja-vu logodeja-vu
↳Reusing solutions from past agent conversations to avoid re-debugging or re-implementing.
↳Debugging complex issues by accessing comprehensive past debugging sessions and design decisions.
↳Maintaining persistent context across different AI agents and development machines.
↳Sharing sanitized session digests with colleagues for onboarding or knowledge transfer.
↳Understanding file change history and decision-making via session blame.
FAQ

FAQ

What is the difference between memory-bank-mcp and deja-vu?
Both memory-bank-mcp and deja-vu are in the Memory & Context category. memory-bank-mcp has 920 stars, while deja-vu has 1.3k stars.
Which is better, memory-bank-mcp or deja-vu?
The best choice depends on your use case. Choose memory-bank-mcp if Centralized management of AI model context across various projects., and deja-vu if Reusing solutions from past agent conversations to avoid re-debugging or re-implementing..
Is memory-bank-mcp free or open source?
Yes, memory-bank-mcp is open source on GitHub (MIT).
Is deja-vu free or open source?
Yes, deja-vu 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 deja-vu →memory-bank-mcp details →deja-vu details →