Memory Bank MCP Server

Content

Memory Bank MCP Server turns Cline-style project memory banks into an MCP service. It stores project-specific memory files under a configured root and exposes tools for listing projects, listing project files, reading files, writing new files, and updating existing memory files.

Use it when a team wants a consistent file-backed memory-bank structure across Claude, Cline, Roo Code, Cursor, or another MCP client. Keep it scoped to a dedicated memory directory so the agent manages notes rather than arbitrary local files.

Source Review

• https://github.com/alioshr/memory-bank-mcp
• https://raw.githubusercontent.com/alioshr/memory-bank-mcp/main/README.md
• https://registry.npmjs.org/%40allpepper%2Fmemory-bank-mcp
• https://raw.githubusercontent.com/alioshr/memory-bank-mcp/main/LICENSE
• https://raw.githubusercontent.com/alioshr/memory-bank-mcp/main/package.json
• https://raw.githubusercontent.com/alioshr/memory-bank-mcp/main/custom-instructions.md
• https://raw.githubusercontent.com/alioshr/memory-bank-mcp/main/src/validators/path-security-validator.ts
• https://raw.githubusercontent.com/alioshr/memory-bank-mcp/main/src/main/protocols/mcp/routes.ts
• https://raw.githubusercontent.com/alioshr/memory-bank-mcp/main/src/infra/filesystem/repositories/fs-file-repository.ts

These sources were reviewed on 2026-06-06. Prefer the live repository, README, npm metadata, license, package metadata, custom instructions, path validator, MCP route definitions, and filesystem repository implementation for current setup and behavior details.

Features

• Manage memory-bank files through a TypeScript MCP server.
• Use MEMORY_BANK_ROOT to define the storage root.
• List available projects under the memory-bank root.
• List files for one project.
• Read memory-bank file contents.
• Write new memory-bank files.
• Update existing memory-bank files.
• Validate required parameters and reject path traversal or slash-containing file/project names.
• Run through npx, Smithery, or Docker with a mounted memory-bank directory.

Installation

Create or choose a dedicated memory-bank directory, then configure the server:

{
  "mcpServers": {
    "memory-bank": {
      "command": "npx",
      "args": ["-y", "@allpepper/memory-bank-mcp@latest"],
      "env": {
        "MEMORY_BANK_ROOT": "ABSOLUTE_PATH_TO_MEMORY_BANK"
      }
    }
  }
}

For a direct shell check:

MEMORY_BANK_ROOT=ABSOLUTE_PATH_TO_MEMORY_BANK npx -y @allpepper/memory-bank-mcp@latest

If running with Docker, bind-mount only the memory-bank directory that should be visible to the server.

Use Cases

• Maintain project context files shared by Claude, Cline, Roo Code, and Cursor.
• Keep architecture notes, decisions, active tasks, progress summaries, and project conventions in a consistent memory-bank structure.
• Let an agent read memory before starting a task and update memory after a reviewed milestone.
• Manage separate memory directories for multiple projects from one MCP server.
• Pair memory-bank updates with human review before writing durable project state.

Safety and Privacy

Memory Bank MCP is intentionally file-backed. That makes it simple to inspect and back up, but it also means write tools create durable notes. Use a dedicated root, do not store secrets in memory files, and keep write/update operations out of auto-approval until the workflow is trusted.

Review memory files periodically. Project memories can drift, accumulate stale decisions, or accidentally preserve sensitive context that should have stayed in the chat session.

Duplicate Notes

Existing catalog entries cover other memory systems, knowledge graphs, note-taking integrations, and agent memory tools. This entry covers the separate alioshr/memory-bank-mcp package for file-backed, Cline-style project memory bank management.

• Source repositorygithub.com 2026-07-21T07:17:01+00:00
• Documentationraw.githubusercontent.com
• Submitted by oktofeesh12026-06-06