Memory Bank MCP Server
An MCP server for a project memory bank: the agent stores and reads memory files through one service instead of inside the project
- 926 ★ on the repository
- Last commit
- MIT
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/memory-bank-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads and writes memory files to disk
This is third-party code. Review the repository files before installing.
What it does
The server turns the usual file-in-project memory bank into a separate service. Through MCP tools the agent reads and writes memory files organized by project, while the files themselves live in a chosen root directory outside the repo. The idea comes from Cline Memory Bank: the agent keeps notes about a project across sessions so it does not lose context. The server sets one place for these files and access rules for them, and ships ready instructions for the agent that go into its settings. It runs via npx, with the memory directory path set by an environment variable.
Who it is for. For developers who want to keep the agent's project memory in one place outside their repos.
Good fit when
- You want the agent to remember project context across sessions
- You want to store memory files apart from the code
- You run several projects and need shared memory across them
Not a fit when
- Memory in files inside the project is enough
- You do not need persistent context storage
Example request
Save the key decisions for this project to the memory bank and pull them at the start of the next sessionMCP
- Transport
- stdio
- Authentication
- not required
Environment variables
MEMORY_BANK_ROOTrequired- Path to the root directory where per-project memory files are stored
Limitations
It needs a memory root path via an environment variable. To be useful, add the provided instructions to the agent's settings, or it may not use the memory bank. Storage is file-based at the given path.
How to disable. Remove the allPepper-memory-bank server from your MCP config.
FAQ
Where are memory files stored?
In the directory you set with MEMORY_BANK_ROOT, separate from the project code.
Why does the agent not use memory?
Add the provided instructions to its settings so it reaches the memory bank.
Discussion
No questions or reviews yet.
Related
MCP serversA self-hosted MCP server for long-term agent memory: structured records, versioned rollback and a visual dashboard
A local memory MCP server for coding agents: records issues, attempts, fixes and decisions and warns before repeating a failed approach
Local memory for agents: stores conversations and project files verbatim and retrieves them with semantic search over MCP
An MCP server for long-term agent memory: compresses dialogues into atomic facts, resolves pronouns and anchors relative time to absolute dates
The Memanto memory MCP server: an agent stores facts and decisions and finds them in later sessions, even as of a date.
Membase keeps one shared memory for AI agents that Claude Code, Cursor and Codex read through MCP, an SDK or the membase command
README in short
The README describes an MCP server that turns a file memory bank into a separate service accessed through MCP tools. Memory files are organized by project and live in a chosen root directory, an idea drawn from Cline Memory Bank. Install is via npx with a MEMORY_BANK_ROOT variable, and it ships ready instructions to paste into the agent's settings for Cline, Claude and Cursor. MIT licensed.