Memory Bank MCP

🚀 Memory Bank MCP

A project knowledge management system based on the Model Context Protocol (MCP) for structured documentation recording and management.

Memory Bank is an MCP server that helps teams create, manage, and access structured project documentation. It captures different aspects of project knowledge, from high - level goals to technical details and daily progress, by generating and maintaining a set of interconnected Markdown documents.

✨ Features

• AI - Automated Documentation Generation: Automatically generate comprehensive project documentation using the Gemini API.
• Structured Knowledge System: Maintain a hierarchical structure of six core document types.
• MCP Integration: Implement the Model Context Protocol for seamless integration with AI assistants.
• Custom Location: Specify the location to create the Memory Bank directory.
• Document Templates: Provide ready - made templates, including project briefs, product backgrounds, system patterns, etc.
• AI - Assisted Updates: Manually update documents or regenerate them via AI.
• Advanced Query: Conduct context - aware relevance searches across all documents.

📦 Installation

# Clone the repository
git clone https://github.com/tuncer - byte/memory - bank - mcp.git
cd memory - bank - mcp

# Install dependencies
npm install

# Create a .env file containing the Gemini API key (optional)
echo "GEMINI_API_KEY=your_api_key_here" > .env

💻 Usage Examples

Basic Usage

# Start in development mode
npm run dev

Advanced Usage

# Build the project
npm run build

# Start in production mode
npm run start

MCP Configuration

The Memory Bank is configured via the following JSON file:

{
    "memoryBank": {
        "api_key": "your_api_key_here",
        "context_size": 1024,
        "temperature": 0.7
    }
}

📚 Documentation

Memory Bank organizes project knowledge into six core document types:

1. Project Brief (projectbrief.md): The core document defining project goals, scope, and vision.
2. Product Background (productContext.md): Records product features and values from the user's perspective.
3. System Patterns (systemPatterns.md): Establishes the system's architecture and component relationships.
4. Technical Background (techContext.md): Specifies the technology stack and implementation details.
5. Active Context (activeContext.md): Tracks current tasks, outstanding issues, and development priorities.
6. Progress Record (progress.md): Records completed work, milestones, and project history.

📄 License

MIT