This is an MCP server for retrieving all files in the memory-bank directory at once. Its purpose is to reduce AI tool invocation frequency when
Most knowledge and memory work still happens through a UI a human drives. Memory MCP server moves it into the conversation instead. This is an MCP server for retrieving all files in the memory-bank directory at once. Its purpose is to reduce AI tool invocation frequency when loading memory-bank, saving both time and money.
The server publishes 4 tools. What each one is for:
read-memory-bank — Read and consolidates files from the specified memory bank directory. Use this to provide project context (Memory Bank) to the AIInput — **Returns — **Build — The Build tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Memory's toolset — read-memory-bank, Input, Returns and 1 more — is a fair guide to whether it matches your workflow. It is maintained by abeyuya; 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 |
|---|---|
| read-memory-bank | Read and consolidates files from the specified memory bank directory. Use this to provide project context (Memory Bank) to the AI. |
| Input | ** |
| Returns | ** |
| Build | The Build tool exposed by this server. |
{
"mcpServers": {
"memory-bank-loader": {
"command": "npx",
"args": [
"-y",
"memory-bank-loader-mcp@latest",
],
}
}
}Configuration as documented by the project. Restart the client after saving.
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.