MCP server for remote management of project memory banks
MCP server for remote management of project memory banks
A Model Context Protocol (MCP) server implementation for remote memory bank management, inspired by Cline Memory Bank.
The Memory Bank MCP Server transforms traditional file-based memory banks into a centralized service that:
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| disabled | Set to false to enable the server |
| autoApprove | List of operations that don't require explicit user approval: |
| memory_bank_read | Read memory bank files |
| memory_bank_write | Create new memory bank files |
| memory_bank_update | Update existing memory bank files |
| list_projects | List available projects |
| list_project_files | List files within a project |
| Variable | Description | Required |
|---|---|---|
| MEMORY_BANK_ROOT | Configuration value read at startup. | Optional |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Enables AI assistants to securely interact with Azure DevOps through a standardized protocol.