A memory system for Cline that tracks progress between conversations.
Cline Memory Bank MCP server exists for a simple reason — assistants are far more useful when they can act on Cline Memory Bank directly instead of describing what you should do. A memory system for Cline that tracks progress between conversations.
This project is still in development but is mostly working.
The Memory Bank MCP server helps maintain consistent project context across development sessions by providing structured tools and resources for managing:
Once Cline Memory Bank is connected, these are the calls the assistant has available:
Prerequisites — The Prerequisites tool exposed by this serverTools — After installation and building, initialize the memory bank for your project by running this command in the project's root directory: bash nodeResources — 1. memory://project/context - Project overview and technical stack - Architecture principles and guidelinesSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cline Memory Bank's toolset — Prerequisites, Tools, Resources — is a fair guide to whether it matches your workflow. It is maintained by dazeb; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Tools | After installation and building, initialize the memory bank for your project by running this command in the project's root directory: bash node /path/to/cline-mcp-memory-bank/build/index.js initialize_memory_bank . (Repl |
| Resources | 1. memory://project/context - Project overview and technical stack - Architecture principles and guidelines |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
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.
Chat with your second brain — search, read and write vault notes through the Local REST API.