memory-bank

Memory Bank MCP Server is a multi-project MCP-compliant server that stores project documents and rules in the filesystem using Markdown. It supports isolated projects, Markdown-based documents, a web management UI, and an MCP tool interface for large language models to manage projects, documents, and rules. You can use the MCP tool endpoints to list, create, update, and delete projects, documents, and rules, enabling seamless integration with LLM-driven workflows and automation.

To run and interact with the server, first ensure the server is started in MCP mode. The server exposes both a web UI and MCP endpoints. You can manage projects and documents through the REST API or invoke MCP tool calls such as list_projects, get_document, update_document, list_rules, and more. When using Cursor or other tooling, you can configure a tool provider that points to the MCP entrypoint (node dist/index.js mcp) and then invoke operations like creating a new project, updating a project’s documents, or applying global and project-specific rules.

Prerequisites:

• Node.js 16+ (recommended 18+)
• npm 7+ or yarn 1.22+

Installation steps:

# 1. Clone the repository
git clone https://github.com/your-username/memory-bank-mcp-server.git
cd memory-bank-mcp-server

# 2. Install dependencies
npm install

# 3. Build the project
npm run build

# 4. Run the MCP server (MCP mode)
# This starts both Web and MCP servers according to README
npm start

# Or explicitly start only MCP server (if configured)
npm start -- mcp

Environment variables (config how to set):

• Create a .env file or export variables:

PORT=3000
ROOT_DIR=/app/data
SESSION_SECRET=your-secret-key

Notes:

• The server stores data under the ROOT_DIR, organizing projects under projects/, documents/, and rules/ as described in the README.
• The UI is accessible via the configured web port, and MCP tool calls can be issued by LLMs or automation pipelines.

Tips and common notes:

• Ensure the filesystem permissions allow read/write for the ROOT_DIR path to avoid document save errors.
• When deleting a project, all associated documents and rules are removed; this action cannot be undone.
• If the MCP connection fails, verify that the MCP server is running and the entrypoint path (dist/index.js) is correct for your installation.
• The server uses Markdown for documents; take advantage of Markdown templates under templates/ to standardize project documentation.
• You can customize global and per-project rules; project rules take precedence over global rules.
• For production deployments, consider configuring a reverse proxy and enabling HTTPS, plus setting a robust SESSION_SECRET.