The Memory Bank MCP Server provides structured workflow tools for managing software development projects from initialization to archival across complexity levels (1-4).
Core Workflow Modes:
Initialize Projects (
van_mode): Start projects, assess complexity, and set up Memory Bank file structurePlan Implementation (
plan_mode): Create detailed step-by-step execution plans based on project complexityDesign Components (
creative_mode): Design architecture, algorithms, and UI/UX for complex componentsExecute Implementation (
implement_mode): Carry out phased implementation with progress tracking and integration testingReflect and Archive (
reflect_archive_mode): Document lessons learned and create final project archives
File Management: Automatically creates and manages project files like tasks.md, progress.md, and project-archive.md in the .memory_bank directory.
Integration: Compatible with Claude Desktop, Cursor IDE, VS Code, and other MCP-compatible applications.
Supports package management, installation, building, and running the server through npm commands
Provides TypeScript configuration for ES modules with proper module resolution to avoid import errors
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Memory Bank MCP Serverinitialize a new project with complexity level 3 for building a user authentication system"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Memory Bank MCP Server
A Model Context Protocol (MCP) server implementing the Memory Bank system based on the cursor-memory-bank custom modes.
Overview
This MCP server provides structured workflow tools for managing software development projects through different complexity levels and phases:
VAN Mode: Project initialization and complexity assessment
PLAN Mode: Detailed implementation planning
CREATIVE Mode: Design and architecture decisions
IMPLEMENT Mode: Code implementation and execution
REFLECT+ARCHIVE Mode: Project reflection and documentation archiving
Related MCP server: Node Omnibus MCP Server
Features
🎯 VAN Mode (Entry Point)
Initialize new projects with complexity levels 1-4
Set up Memory Bank file structure
Determine appropriate next mode based on complexity
📋 PLAN Mode (Planning)
Generate implementation plans based on complexity level
Create detailed step-by-step approaches
Identify components requiring creative phases
🎨 CREATIVE Mode (Design)
Architecture design with multiple options analysis
Algorithm design with complexity considerations
UI/UX design with accessibility and usability focus
Structured documentation of design decisions
⚒️ IMPLEMENT Mode (Execution)
Phase-based implementation for complex projects
Integration testing and documentation
Progress tracking and status updates
🤔 REFLECT+ARCHIVE Mode (Completion)
Implementation reflection and lessons learned
Complete project archiving
Preparation for next task initialization
Installation
Usage
Running the Server
Available Tools
1. van_mode
Initialize a project with complexity assessment.
Parameters:
complexity(required): "1" | "2" | "3" | "4"Level 1: Quick bug fix
Level 2: Simple enhancement
Level 3: Complex feature
Level 4: Major feature/refactor
task_description(optional): Description of the task
Example:
2. plan_mode
Create detailed implementation plan.
Parameters:
complexity(optional): Complexity level (reads from tasks.md if not provided)
3. creative_mode
Perform design and architecture work.
Parameters:
component_name(required): Name of component requiring designcreative_type(required): "architecture" | "algorithm" | "uiux"requirements(required): Requirements and constraints
Example:
4. implement_mode
Execute implementation based on plan.
Parameters:
phase(optional): Implementation phase for complex projectscomplexity(optional): Complexity level (reads from tasks.md if not provided)
5. reflect_archive_mode
Reflect on implementation and archive documentation.
Parameters:
action(required): "reflect" | "archive""reflect": Review and document implementation experience
"archive": Create final documentation archive
Memory Bank Files
The server creates and manages several files in the .memory_bank directory:
tasks.md: Main task tracking and statusactiveContext.md: Current context and focusprogress.md: Implementation progress trackingimplementation-plan.md: Detailed implementation planreflection.md: Post-implementation reflectioncreative-{component}.md: Creative phase documentationdocs/archive/project-archive.md: Final project archive
Workflow Example
Complexity Levels
Level 1: Quick bug fixes - Direct implementation, minimal planning
Level 2: Simple enhancements - Streamlined planning, straightforward implementation
Level 3: Complex features - Comprehensive planning, creative phases may be required
Level 4: Major features/refactors - Detailed architecture, phased implementation, creative design required
Development
Troubleshooting
Module Resolution Errors
If you encounter ERR_MODULE_NOT_FOUND errors when running the server, ensure:
Build First: Always run
npm run buildbeforenpm startES Module Imports: All imports in source files use
.jsextensionsTypeScript Config: The
tsconfig.jsonis configured for ES modules with"module": "ESNext"
Memory Bank Directory Permissions
If the server can't create the .memory_bank directory:
Integration
This MCP server can be integrated with:
Claude Desktop: Add to MCP server configuration
Cursor IDE: Use with MCP client capabilities
VS Code: Through MCP extensions
Custom clients: Any MCP-compatible application
Based On
This implementation is based on the excellent cursor-memory-bank project by vanzan01, adapted for use as an MCP server.
License
MIT