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
M
Memory Bank MCP Server
Community
A remote memory bank management MCP server with multi-project isolation.
GitHub source repository ↗
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.
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.
Tools
memory_bank_read
Read a memory bank file from a project.
memory_bank_write
Create a new memory bank file.
memory_bank_update
Update an existing memory bank file.
list_projects
List available projects.
list_project_files
List files within a project.
Setup
- Ensure Node.js environment.
- Add server configuration to your MCP client (e.g., Claude Desktop, Cline, Roo Code, or Cursor).
- Set the MEMORY_BANK_ROOT environment variable to point to your memory bank root.
- 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"
]
}
}
Fit and risk
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
Troubleshooting
- Common issues:
- - Ensure MCP client configuration is correct, especially command and args.
- - Check that the MEMORY_BANK_ROOT environment variable is set properly.
- - Inspect MCP client logs for error messages.
- - For Docker, verify volume mounts are correct.
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 DesktopFull support
Claude CodeFull support
ClineFull support
Roo CodeFull support
CursorFull support