Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BRAIN_DIRYesPath 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
brain_searchA

Recall notes relevant to a task. Call this before any non-trivial step.

Returns id, title, description and score; open the promising ones with brain_read.
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.

Start the body with a 2-3 sentence blockquote addressed to the next agent.
Pick an existing cortex when one fits (see brain_list); create a new one only for a new theme.
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 7 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues