project-brain-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@project-brain-mcpget context for my current project to review past decisions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: rawthink
Installation
pip install git+https://github.com/pym2282/project-brain-mcp
claude mcp add project-brain project-brain-mcp --scope userRestart Claude Code. The MCP server is now active in all your projects.
Uninstall
pip uninstall project-brain-mcp
claude mcp remove project-brain --scope userMemory 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.jsonTools
Tool | When to call |
| Session start — returns slim index |
| When index shows relevant entries — returns full content |
| Before any architectural proposal |
| When a decision is confirmed |
| When an investigation question is answered |
| When a wrong approach is identified |
| To correct an existing entry |
| To remove an outdated entry |
| 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.
This server cannot be deployed
Maintenance
Related MCP Connectors
Persistent, governed institutional memory for Claude Code — specs, decisions, learnings.
Persistent cross-session memory shared by Codex, Claude Code, ChatGPT, and other AI agents.
Persistent memory for Claude Code and Cursor. Stop re-explaining your project every session.
Persistent, outcome-grounded episodic memory for Claude. 14ms CPU retrieval, no GPU, no vector DB.
Related MCP Servers
- AlicenseBqualityDmaintenanceA persistent memory layer for Claude Code that maintains project information, technology stack, tasks, decisions, and session history between coding sessions, eliminating the need to re-explain project context.9MIT
- AlicenseAqualityAmaintenancePersistent memory for Claude Code — hybrid search, knowledge graph, session lifecycle.17MIT
- AlicenseAqualityDmaintenancePersistent memory and automatic git snapshots for Claude Code, capturing decisions, patterns, and architecture across sessions.1037 npm98MIT
- AlicenseNot gradedqualityDmaintenancePersistent memory for Claude Code — a self-evolving knowledge layer that survives across sessions, grows from every conversation, and surfaces relevant context automatically.14MIT