memory-bank

Memory Bank MCP Server is a modular MCP service that manages project-specific contextual data using an SQLite database stored under memory-bank/memory.db within each project path. It exposes a standardized set of MCP tools to initialize storage, check status, read sections (like product_context, decisions, progress, focus, and system_patterns), and append new entries to these sections. You typically run this server via npx, which fetches the package from npm and launches the MCP service in-line. The server is designed to be integrated into MCP-enabled hosts or clients (e.g., RooCode) using the provided MCP tools and a standard server entry in your mcp_settings.json configuration. The tools allow you to initialize a project’s memory bank, query existing records, and add new entries with structure tailored to each section.

Prerequisites:

• Node.js version 18.x or higher (>=18.0.0)
• Internet access to fetch the MCP package via npx

Installation steps:

1. Ensure Node.js is installed and up to date. You can verify with: node -v npm -v
2. (Recommended) Use a Node version manager if your system packages lag behind (example with NVM): curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash source ~/.bashrc nvm install 18 nvm use 18
3. Run the Memory Bank MCP Server directly from npm without local installation: npx -y @telagod/memory-bank-mcp-server
4. If integrating with RooCode or another MCP host, configure your mcp_settings.json as shown in the integration guide (see below).

Notes and tips:

• The memory bank uses an SQLite database stored at memory-bank/memory.db within the project directory. Ensure the hosting process has write access to this path.
• When using npx, ensure your Node.js environment is up to date; older Node.js versions (e.g., v12) can cause npx to fail.
• For Windows, PowerShell or CMD should work with the npx command if Node.js is in PATH. For macOS/Linux, ensure Node.js is installed via a supported method (NVM recommended).
• If you encounter permission or path issues, try running the command from a directory where you have full write permissions or specify a custom project_path in the MCP tool calls.
• The MCP tools are designed to be called by MCP clients (like RooCode). Validate that the client is configured to allow the initialized commands (initialize_memory_bank, get_memory_bank_status, read_memory_bank_section, update_memory_bank_entry) as shown in the integration example.