Skip to main content
Glama
pym2282

project-brain-mcp

by pym2282

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_plan checks 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: Cortex

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.

A
license - permissive license
-
quality - not tested
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • A
    license
    B
    quality
    D
    maintenance
    A 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.
    Last updated
    9
    MIT
  • A
    license
    C
    quality
    A
    maintenance
    Stores and recalls Claude Code session content as persistent memory, auto-injects relevant prior decisions and lessons at session start, and exposes 33 MCP tools for memory, knowledge-graph navigation, and cognitive profiling — backed by 41 neuroscience papers and 97.8% R@10 on LongMemEval.
    Last updated
    40
    6
    68
    MIT

View all related MCP servers

Related MCP Connectors

  • Persistent memory and cross-session learning for AI coding assistants (hosted remote MCP).

  • Experience memory for coding agents: validated traps, fixes and dead-ends at decision time.

  • Hosted memory for AI agents that learns and forgets — one key across Claude, Cursor & ChatGPT.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pym2282/project-brain-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server