M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
M

Memory Bank MCP Server

Community
A remote memory bank management MCP server with multi-project isolation.
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #308 of 438
Stars
★ 919 Popular
Transport
stdio (local process)
Runtime
Node.js · Docker
Credentials
No credential needed
License
MIT
Last commit
⚠
Tools
5
45FMRS · D

Memory Bank MCP Server provides a practical multi-project memory bank management solution, implementing the MCP protocol for remote access, file operations, and project isolation. Suitable for developers using MCP clients to manage project context. However, users must configure environment variables themselves and be mindful of path security. The implementation is clean and includes tests and documentation.

Strongest · Setup experience 12/20 Weakest · Reliability 6/20

Reliability
6/20
Security and permissions
7/20
Maintenance
9/20
Documentation
11/20
Setup experience
12/20
Why each score
Reliability 6/20
Evidence is limited to the README: features, commands, and test scripts are described, but no source code, package.json, CI workflows, or committed test files were supplied, so the MCP init handshake, tool list, actual behavior, and error handling cannot be verified. The static calibration caps this at 12, and the absence of executable evidence and test coverage lowers the score to 6.
Security and permissions 7/20
The README claims path traversal prevention, project isolation, and safe read-only operations, and the configuration examples use a local filesystem root via an environment variable with no credentials or external network exposure. However, the source code is unavailable, so those security mechanisms cannot be confirmed; the autoApprove example silently allows write/update operations and no explicit confirmation flow is documented. No red-line issue is evident, but insufficient evidence results in a score of 7.
Maintenance 9/20
The repository is not archived, has an MIT license, an npm badge suggesting published releases, and notable star/issue counts indicating community interest. However, the supplied material contains no commit history, release dates, issue-response evidence, or dependency update records, so sustained maintenance and governance cannot be fully verified; score 9.
Documentation 11/20
The README covers overview, features, Smithery installation, configuration examples for Cline/Roo, Cursor, and Claude, Docker usage, development commands, and contribution guidelines. It lacks tool parameter schemas, limitations, troubleshooting, and prerequisites such as Node version, and the package name is inconsistent between @alioshr and @allpepper, causing confusion; score 11.
Setup experience 12/20
The README provides clear JSON configuration examples for multiple mainstream clients, npx commands, and Docker instructions. There is no verifiable CI/test execution evidence, no explicit Node version or MEMORY_BANK_ROOT creation step, and the package naming is inconsistent; per the static calibration cap of 15 with conservative deduction, the score is 12.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local files

Best for

  • Developers using MCP clients like Cline, Claude Code, or Cursor
  • Teams that need to manage memory banks for multiple projects centrally
  • Advanced users wanting to integrate memory banks via MCP

Not for

  • Simple single-project scenarios that do not need multi-project isolation
  • Environments without Node.js or network access
  • Features requiring real-time synchronization or collaborative editing

Required permissions

  • Read and write files under the specified directory (MEMORY_BANK_ROOT)
  • Create and update memory bank files
  • List projects and files within projects

Risks and side effects

  • Misconfiguration of MEMORY_BANK_ROOT may lead to accessing unintended directories
  • Unauthorized access could expose sensitive information
  • Dependency on Node.js runtime and network
  • Third-party server may not have undergone official security audit

Setup

Before you start

Runtime：Node.js · Docker

MEMORY_BANK_ROOT required A local filesystem path to the directory where project memory banks are stored (e.g. /path/to/memory-bank); set it yourself, nothing to obtain from a service.
  1. Ensure Node.js environment.
  2. Add server configuration to your MCP client (e.g., Claude Desktop, Cline, Roo Code, or Cursor).
  3. Set the MEMORY_BANK_ROOT environment variable to point to your memory bank root.
  4. Optional: Auto-install via Smithery: npx -y @smithery/cli install @alioshr/memory-bank-mcp --client claude.
claude_desktop_config.json 
{
  "allpepper-memory-bank": {
    "command": "npx",
    "args": [
      "-y",
      "@allpepper/memory-bank-mcp"
    ],
    "env": {
      "MEMORY_BANK_ROOT": "<path-to-bank>"
    },
    "disabled": false,
    "autoApprove": [
      "memory_bank_read",
      "memory_bank_write",
      "memory_bank_update",
      "list_projects",
      "list_project_files"
    ]
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

Generate and validate client config

Check that it works

The tools memory_bank_read, memory_bank_write, memory_bank_update, list_projects and list_project_files should appear in the client's tool list; running list_projects and seeing projects under MEMORY_BANK_ROOT confirms the connection.

Troubleshooting

  1. Common issues:
  2. - Ensure MCP client configuration is correct, especially command and args.
  3. - Check that the MEMORY_BANK_ROOT environment variable is set properly.
  4. - Inspect MCP client logs for error messages.
  5. - For Docker, verify volume mounts are correct.

Things to try

Once connected, you can ask your AI assistant things like:

  • List all available projects in the memory bank
  • Read the memory bank files for project my-app
  • Create a new memory bank file in project my-app
  • List which files exist in the memory bank for project my-app

Tools 5

memory_bank_read read-only
Read a memory bank file from a project.
memory_bank_write writes
Create a new memory bank file.
memory_bank_update writes
Update an existing memory bank file.
list_projects read-only
List available projects.
list_project_files read-only
List files within a project.

Use cases

Centralized management of memory banks across multiple projects
Remote access to memory bank files via MCP protocol
Maintaining project context within AI assistants
Persisting project knowledge across sessions

Supported clients

Claude Desktop
Claude Code
Cline
Roo Code
Cursor

Listed from the project's documentation, not tested by this site.

Overview

Memory Bank MCP Server is a Model Context Protocol (MCP) server implementation for remote memory bank management, inspired by Cline Memory Bank. It transforms traditional file-based memory banks into a centralized service that provides remote access to memory bank files via the MCP protocol, supports multi-project management, maintains consistent file structure and validation, and ensures proper isolation between project memory banks.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision 559e42274147 Data synced 2026-10-13 Read the FMRS scoring method