Memory Bank MCP

Memory Bank MCP is an MCP server that provides AI coding assistants with remote read/write access to structured memory bank files, enabling persistent project-specific context across sessions for tools like Claude, Cline, Cursor, and Windsurf.

Evaluated Mar 06, 2026 (0d ago) vlatest
Homepage ↗ Repo ↗ Other memory context persistence typescript nodejs smithery cline cursor windsurf claude multi-project
⚙ Agent Friendliness
68
/ 100
Can an agent use this?
🔒 Security
68
/ 100
Is it safe for agents?
⚡ Reliability
60
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
65
Documentation
70
Error Messages
60
Auth Simplicity
80
Rate Limits
60

🔒 Security

TLS Enforcement
82
Auth Strength
65
Scope Granularity
58
Dep. Hygiene
72
Secret Handling
62

Agent memory/context persistence MCP. Local file-based storage. Memory may include sensitive agent context and PII. Protect storage directory. Encrypt sensitive memory entries.

⚡ Reliability

Uptime/SLA
60
Version Stability
62
Breaking Changes
58
Error Recovery
60
AF Security Reliability

Best When

You use AI coding assistants like Cline or Cursor and want them to maintain consistent project context (what was done, decisions made, next steps) across multiple sessions and machines.

Avoid When

You need semantic search over memories (use a vector DB instead), or your memory needs extend beyond file-based text storage.

Use Cases

  • Maintaining persistent AI assistant context (architecture notes, decisions, progress) across coding sessions for multiple projects
  • Centralizing memory bank management so multiple AI tools can share the same project memory without file conflicts
  • Storing and retrieving structured documentation files that AI assistants reference to maintain coherent long-term project understanding

Not For

  • General-purpose key-value or vector database storage
  • Real-time collaborative document editing between human users
  • High-throughput data storage workloads beyond text-based memory files

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication layer. Relies on filesystem-level access control via the MEMORY_BANK_ROOT environment variable. Project isolation is enforced by directory structure.

Pricing

Model: open_source
Free tier: Yes
Requires CC: No

MIT licensed. No cost. Smithery installation is also free.

Agent Metadata

Pagination
none
Idempotent
Yes
Retry Guidance
Not documented

Known Gotchas

  • MEMORY_BANK_ROOT must be set correctly; misconfiguration silently stores files in wrong location
  • No semantic search - agents must know file names to retrieve memories
  • Path traversal prevention means agents cannot access files outside the designated memory bank root

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Memory Bank MCP.

$99

Scores are editorial opinions as of 2026-03-06.

5182
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered