A powerful, production-ready context management system for Large Language Models (LLMs). Built with ChromaDB and modern embedding technologies, it
MCP Memory Bank MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Memory Bank directly instead of describing what you should do. A powerful, production-ready context management system for Large Language Models (LLMs). Built with ChromaDB and modern embedding technologies, it provides persistent, project-specific memory capabilities that enhance your AI's.
This project is fully Docker-ready for easy deployment and local development. The provided Dockerfile and docker-compose.yml set up both the main application and its required ChromaDB vector database.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Once MCP Memory Bank is connected, these are the calls the assistant has available:
Requirements — The Requirements tool exposed by this serverPorts — The Ports tool exposed by this serverYou will need one environment variable: CHROMADB_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
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. MCP Memory Bank's toolset — Requirements, Ports — is a fair guide to whether it matches your workflow. It is maintained by bsmi021; 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 |
|---|---|
| Requirements | The Requirements tool exposed by this server. |
| Ports | The Ports tool exposed by this server. |
| Variable | Description | Required |
|---|---|---|
| CHROMADB_URL | Endpoint or connection string the server talks to. | Yes |
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.