Memory Bank MCP
An AI-assisted development plugin that maintains persistent project context using structured markdown files for goals, decisions, and progress.
Memory Bank MCP
A guided Memory Bank plugin for AI-assisted development
Memory Bank MCP is a Model Context Protocol (MCP) plugin that helps AI assistants maintain persistent project context through structured markdown files. It provides a systematic approach to tracking project goals, decisions, progress, and patterns through guided instructions rather than direct operations.
Features
- Guided Operations: Provides instructions for AI assistants to perform operations themselves
- Structured Context Management: Organize project information across 5 core files
- Intelligent Guidance: Step-by-step instructions for initialization and updates
- Flexible Updates: Smart update guidance based on different change types
- Cross-Platform Support: Automatic path normalization for Windows/macOS/Linux
MCP Configuration
Using the published npm package:
{
"mcpServers": {
"memory-bank": {
"command": "npx",
"args": ["@neko0721/memory-bank-mcp"],
"timeout": 600
}
}
}
Quick Start
-
Initialize Memory Bank
Use init-memory-bank to create the memory-bank directory and core files -
Read Memory Bank
Use get-memory-bank-info to view all Memory Bank content -
Update Memory Bank
Use update-memory-bank to get guidance on updating specific files
Core Files
1. productContext.md (Product Context)
- High-level project overview
- Goals and key features
- Overall architecture
- Automatically incorporates projectBrief.md if available
2. activeContext.md (Active Context)
- Current work status
- Recent changes
- Open questions and issues
- Focus areas
3. progress.md (Progress)
- Task tracking in checklist format
- Completed, current, and planned tasks
- Progress timeline
4. decisionLog.md (Decision Log)
- Architectural and implementation decisions
- Rationale and implications
- Decision history
5. systemPatterns.md (System Patterns)
- Recurring patterns and standards
- Coding conventions
- Architectural patterns
- Testing strategies
Usage Guidelines
For AI Assistants
- Start Every Session: Check if memory-bank directory exists, then use
get-memory-bank-infoto understand project state - Initialize When Needed: Use
init-memory-bankfor new projects - Read Context: Use
get-memory-bank-infoto understand project state - Update Guidance: Use
update-memory-bankto get update instructions - Follow Instructions: Execute the provided guidance to maintain Memory Bank
Update Triggers
- Architecture Changes: Major structural decisions
- Feature Completion: New features or capabilities
- Bug Fixes: Significant issue resolutions
- Refactoring: Code structure improvements
- Decisions: Any important technical choices
- Progress Updates: Task status changes
Tool Reference
init-memory-bank
Initializes Memory Bank with all core files.
Parameters:
rootPath: Project root directory pathforce(optional): Force re-initialization
Returns: Created files list and next steps guidance
get-memory-bank-info
Reads and returns all Memory Bank content (similar to codelf's get-project-info).
Parameters:
rootPath: Project root directory path
Returns: Formatted Memory Bank content for AI context
update-memory-bank
Provides guidance for updating Memory Bank files.
Parameters:
rootPath: Project root directory pathchangeType: Type of change (architecture/feature/bugfix/refactor/decision/progress)description: Brief description of the change
Returns: Detailed update instructions with templates and timestamps
Integration Tips
Cursor Setup
Add to Settings → Rules → User Rules:
Before starting any task, check if memory-bank directory exists in the project. If not, run the MCP command init-memory-bank.
Use the MCP command get-memory-bank-info to read Memory Bank content at session start.
After completing tasks or conversations, you must use the MCP command update-memory-bank to update Memory Bank content.
Follow the MCP guidance to maintain Memory Bank files.
Windsurf Setup
Add to Settings → Cascade → Memories and Rules → Global Rules:
Before starting any task, check if memory-bank directory exists in the project. If not, run the MCP command init-memory-bank.
Use the MCP command get-memory-bank-info to read Memory Bank content at session start.
After completing tasks or conversations, you must use the MCP command update-memory-bank to update Memory Bank content.
Follow the MCP guidance to maintain Memory Bank files.
Contributing
Contributions are welcome! Please feel free to submit issues or pull requests.
License
MIT
Acknowledgments
Inspired by the SPARC methodology and codelf.
Related Servers
Scout Monitoring MCP
sponsorPut performance and error data directly in the hands of your AI assistant.
Alpha Vantage MCP Server
sponsorAccess financial market data: realtime & historical stock, ETF, options, forex, crypto, commodities, fundamentals, technical indicators, & more
Icons8 MCP server
Get access to MCP server SVG and MCP server PNG icons in your vibe-coding projects
Cloudflare Remote MCP Server
A remote MCP server example deployable on Cloudflare Workers without authentication.
SCMCP
A natural language interface for single-cell RNA sequencing (scRNA-Seq) analysis, supporting various modules from IO to enrichment.
Model Context Protocol servers
A collection of reference implementations for the Model Context Protocol (MCP), showcasing various MCP servers implemented with TypeScript and Python SDKs.
Volatility MCP Server
An MCP server for memory forensics using the Volatility 3 framework.
GDB MCP Server
An MCP server that enables LLM clients to interact with GDB for debugging and binary analysis.
Hayhooks
Deploy and serve Haystack pipelines as REST APIs, MCP Tools, and OpenAI-compatible chat completion backends.
Unified MCP Client Library
A TypeScript library for integrating MCP with tools like LangChain and Zod, providing helpers for schema conversion and event streaming.
MCP Servers Collection
A collection of MCP servers for Claude Desktop, providing access to network tools, code linters, and Proxmox virtualization management.
TUUI - Tool Unitary User Interface
A desktop MCP client for tool integration and cross-vendor LLM API orchestration.