project-brain-mcp
Engineering memory for Claude Code — prevents re-investigating solved problems and repeating rejected architectural decisions across sessions and projects.
README
Project Brain MCP
Engineering memory for Claude Code — prevents re-investigating solved problems and repeating rejected architectural decisions across sessions and projects.
What it does
- Prevent re-investigating: Answered questions are recorded as findings. Future sessions skip re-investigation.
- Prevent repeating rejected architectures:
validate_planchecks your proposal against past decisions and mistakes before you proceed. - Cross-project learning: Decisions from other projects appear as soft references, not hard blocks.
- Persistent memory: Survives across sessions, stored in
~/.project-brain/memory.json.
Installation
pip install git+https://github.com/pym2282/project-brain-mcp
claude mcp add project-brain project-brain-mcp --scope user
Restart Claude Code. The MCP server is now active in all your projects.
Uninstall
pip uninstall project-brain-mcp
claude mcp remove project-brain --scope user
Memory location
Memory is stored at ~/.project-brain/memory.json — shared across all projects, never committed to any repo.
To use a custom path:
export PROJECT_BRAIN_MEMORY_PATH=/path/to/memory.json
Tools
| Tool | When to call |
|---|---|
get_context() |
Session start — returns slim index |
get_context(focus=[...]) |
When index shows relevant entries — returns full content |
validate_plan(plan, current_project) |
Before any architectural proposal |
add_decision(title, reason, tags, project) |
When a decision is confirmed |
add_finding(question, conclusion, tags, project) |
When an investigation question is answered |
add_mistake(description, lesson, tags, project) |
When a wrong approach is identified |
update_entry(id, updates) |
To correct an existing entry |
delete_entry(id) |
To remove an outdated entry |
update_open_questions(questions) |
To track unresolved questions |
How validate_plan works
validate_plan("use sqlite for storage", current_project="my-app")
→ conflicts: [entries from "my-app" that match — must resolve]
→ references: [entries from other projects — consider as context]
Same project matches are hard conflicts. Other project matches are soft references.
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
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
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.