A biologically-inspired persistent memory system for LLMs, modeled on neuroplasticity, consolidation, and sleep.
A biologically-inspired persistent memory system for LLMs, modeled on neuroplasticity, consolidation, and sleep. The claude brain mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Everything the assistant can do here goes through one of these:
memory_store — Ingest conversation text — extracts concepts and relationships via Claudememory_retrieve — Query the graph — returns formatted context with inline connectionsmemory_dream — Run a full dream cycle (NREM + REM + waking + threat)memory_dream_report — Human-readable narrative of the last dream cyclememory_goals — Manage research goals — add, list, or removememory_status — Graph statistics (node/edge counts, score distributions)memory_stats_detailed — Detailed appraisal breakdown per node, top edges, contradictions, dream edgesmemory_tune — Adjust parameters at runtime (e.g. dream.rem_jump_probability)You will need 2 environment variables: PYTHONPATH, ANTHROPIC_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Claude Brain's toolset — memory_store, memory_retrieve, memory_dream and 5 more — is a fair guide to whether it matches your workflow. It is maintained by gammon-bio; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Claude Brain's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| memory_store | Ingest conversation text — extracts concepts and relationships via Claude |
| memory_retrieve | Query the graph — returns formatted context with inline connections |
| memory_dream | Run a full dream cycle (NREM + REM + waking + threat) |
| memory_dream_report | Human-readable narrative of the last dream cycle |
| memory_goals | Manage research goals — add, list, or remove |
| memory_status | Graph statistics (node/edge counts, score distributions) |
| memory_stats_detailed | Detailed appraisal breakdown per node, top edges, contradictions, dream edges |
| memory_tune | Adjust parameters at runtime (e.g. dream.rem_jump_probability) |
{
"mcpServers": {
"neuroplastic-memory": {
"command": "/absolute/path/to/mind/.venv/bin/python",
"args": ["-m", "mind"],
"cwd": "/absolute/path/to/mind",
"env": {
"PYTHONPATH": "/absolute/path/to/mind/src"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PYTHONPATH | Filesystem location the server is allowed to use. | Optional |
| ANTHROPIC_API_KEY | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.