cline -memory-bank
A memory system for Cline that tracks progress between conversations.
claude mcp add --transport stdio dazeb-cline-mcp-memory-bank node /path/to/cline-memory-bank/build/index.js
How to use
The Cline Memory Bank MCP server provides a persistent project context for AI-assisted development. It stores and manages project context, session state, progress milestones, and a log of technical decisions to help your AI assistant stay aligned across sessions. After you initialize the memory bank for a project, you can invoke tools like initialize_memory_bank, update_context, record_decision, and track_progress to build and maintain a structured memory of intent, tasks, and decisions. The memory endpoints are exposed through the memory-bank MCP, and can be triggered via the Cline extension or direct MCP tool calls when integrated into your workflow.
How to install
Prerequisites:
- Node.js v16 or later
- pnpm (recommended for dependency management)
- TypeScript tooling if you plan to contribute or develop locally
Setup steps:
-
Clone the repository git clone https://github.com/dazeb/cline-mcp-memory-bank cd cline-mcp-memory-bank
-
Install dependencies (using pnpm as recommended) pnpm install
-
Build the server pnpm run build
-
Initialize the memory bank for a project (example) node build/index.js initialize_memory_bank .
-
Configure Cline to load the MCP server (example settings snippet inside your Cline config): { "mcpServers": { "memory-bank": { "command": "node", "args": [ "/path/to/cline-memory-bank/build/index.js" ], "disabled": false, "autoApprove": [] } } }
Replace /path/to/cline-memory-bank with the absolute path to your cloned and built server. The initialization command above can also be run automatically by the Cline workflow after building.
Additional notes
Tips and considerations:
- Ensure Node.js v16+ is installed and available in your PATH.
- The memory-bank server stores project context in Markdown files and structured JSON; ensure the process has write access to the project directory.
- If you use the manual Cline settings method, ensure the path matches your OS-specific configuration and that the settings file is accessible by your Cline extension.
- The following MCP tool calls are available after initialization:
- initialize_memory_bank: create the memory structure for a new project
- update_context: refresh the current session context with mode, tasks, and session state
- record_decision: log architectural decisions with rationale
- track_progress: update milestones and task statuses
- Environment variables you may encounter include PATH for Node, and any project-specific data paths used by the server. You can add a .env or equivalent environment config if you extend the server.
- If you see permissions errors, verify that the process running the MCP server has read/write access to the project directory and the build/index.js path.
Related MCP Servers
mcp-rest-api
A TypeScript-based MCP server that enables testing of REST APIs through Cline. This tool allows you to test and interact with any REST API endpoints directly from your development environment.
autowpmcp
AutoWP MCP (Model Context Protocol) server connects Claude to WordPress site and allows users to ask Claude to write blog posts and automatically publish them to WordPress sites.
create -kit
Scaffold a production-ready Model Context Protocol (MCP) server in seconds.
wikipedia -image-crawler
A Wikipedia Image Search Tool. Follows Creative Commons Licences for images and uses them in your projects via Claude Desktop/Cline.
together
MCP server enabling high-quality image generation via Together AI's Flux.1 Schnell model.
keyshade
This is the official repository of Keyshade MCP Server