Project Brain
A local MCP memory server that gives AI assistants durable project memory across coding sessions, storing context, changes, and decisions.
README
Project Brain
Local MCP memory server for AI-assisted development.
What It Is
- Project Brain runs as a local MCP server via
project-brain stdio. - It gives your AI assistant durable project memory across coding sessions.
- It stores project context, changes, decisions, and progress under
.project-brain/. - The assistant should access memory through MCP tools, not by editing
.project-brain/files directly.
In Practice
| Feature | Experience |
|---|---|
| Change History | The AI becomes more "stateful" and stops repeating the same architectural mistakes. |
| Architecture Index | The AI is less likely to lose track of things during cross-file changes. |
| Preference Capture | The AI learns your architecture decisions and implementation choices, so its outputs feel more consistent¹. |
| Failed Attempt Memory | The AI stops recommending approaches you already tried and ruled out. |
Quick Start
Copy the text below into your AI assistant and let it complete the installation:
Please install Project Brain in this repository by following https://github.com/myczh-1/project-brain/docs/install.md.
Configure Project Brain as a local MCP server through `project-brain stdio`.
Do not edit `.project-brain/` files directly.
Explain which files you plan to modify before editing them.
Or, if you prefer, you can follow the docs and install it manually.
Integration Guides
Learn More
How It Works After Install
Once installed, your AI assistant will:
- connect to the local MCP server exposed by
project-brain stdio, - follow repository-local instructions from
AGENTS.mdwhen present, - read Project Brain when it needs project memory or task context,
- and update Project Brain through MCP tools instead of editing
.project-brain/files directly.
For the full workflow, see docs/guide-openspec-integration.md.
Architecture
Project Brain follows a layered architecture:
- protocol: Pure type definitions and schemas.
- core: Domain logic, commands, queries, and ports.
- infra-fs: Filesystem implementation of storage and git ports.
- mode-embedded: File-based integration helpers for repository-local workflows.
- app: Bootstrap CLI and stdio entry point.
License
MIT
<small> 1: Or the model's own preferences </small>
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.