brain-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRAIN_DIR | Yes | Path to the brain directory containing the Markdown notes (e.g. `./examples/brain` or `$HOME/brain`). Passed as an environment variable when launching the `brain-mcp` stdio MCP server. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| brain_searchA | Recall notes relevant to a task. Call this before any non-trivial step. |
| brain_readB | Return the full Markdown of one note, frontmatter included. |
| brain_listB | List cortices with their note counts, or the notes of one cortex. |
| brain_encodeA | Store one durable learning: a fix that worked, a constraint, a preference, a decision. |
| brain_linkC | Link two notes both ways. Links across cortices are the most valuable. |
| brain_supersedeB | Retire an outdated note in favour of a newer one. Never edit history in place. |
| brain_validateB | Mark a note as re-checked today, optionally with a new confidence. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool maps to a distinct action on notes: browse (list), create (encode), relate (link), retire (supersede), re-check (validate), find (search), open (read). The only mild overlap is between brain_list and brain_search, both retrieval paths, but descriptions differentiate enumeration from query-based recall.
Every tool follows a uniform brain_<verb> pattern (brain_list, brain_encode, brain_link, brain_supersede, brain_validate, brain_search, brain_read). Fully predictable and consistent.
Seven tools is well-scoped for a note-memory system, covering browse/search/read/create/link/supersede/validate without redundancy. Each tool earns its place.
The lifecycle is well covered: create, retrieve, relate, retire, and confidence-update, with intentional design that history is never edited in place. Minor gap is no explicit cortex management or bulk cleanup, though cortex creation is folded into encode.