Brain MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRAIN_VAULT | No | Path to the markdown vault | ./vault |
| BRAIN_EMBED_URL | No | URL of the embedding service | http://127.0.0.1:8091/embed |
| BRAIN_AGENT_LOGS | No | Path to agent logs | ./agentlogs |
| BRAIN_COLLECTION | No | Name of the Qdrant collection | brain |
| BRAIN_QDRANT_HOST | No | Qdrant host | 127.0.0.1 |
| BRAIN_QDRANT_PORT | No | Qdrant port | 6333 |
| BRAIN_DASHBOARD_PORT | No | Port for the dashboard UI | 8090 |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| brain_grepB | Exact/regex search via ripgrep. Returns file:line:match. |
| brain_searchB | Dense + BM25 prefetch, RRF fusion. Optional path_prefix narrows scope. |
| brain_readA | Read a vault file by relative path. |
| brain_batch_readA | Read up to 5 vault files in one call. |
| brain_listB | List files in the vault with depth and pattern limits. |
| brain_statsA | Collection size, disk usage, embed service health, .md count. |
| brain_writeA | Create or overwrite a vault file. Auto-reindexes. |
| brain_appendB | Append to a vault file. Auto-reindexes. |
| brain_logC | Timestamped daily log entry (YYYY-MM-DD.md). Auto-reindexes. |
| brain_lessonB | Persist a reusable lesson under knowledge/agent-lessons/. Auto-reindexes. |
| brain_task_claimC | Atomically claim a task for parallel agent coordination. |
| brain_task_releaseA | Release a task claim if you own it. |
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 12 tools
Each tool has a clearly distinct purpose: grep and search differ by exact/regex vs semantic search; read and batch_read differ by count; write, append, log, and lesson each target different write behaviors and destinations. The task claim/release pair is also unambiguous in ownership semantics.
Most tools follow a consistent brain_<verb> pattern such as brain_read, brain_write, brain_append, and brain_list. Minor deviations like brain_stats, brain_lesson, and brain_task_claim/task_release introduce nouns or object-verb ordering, but the overall pattern remains predictable.
Twelve tools is well within the ideal range and matches the server's dual purpose of knowledge vault management and agent task coordination. Each tool covers a meaningful operation without unnecessary redundancy or feature bloat.
Core vault operations like search, read, write, append, list, and specialized logging are covered well. However, there is no delete/remove or rename/move tool, and task coordination lacks a way to discover or list tasks, which can create dead ends in some workflows.