brain-v42
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log granularity (e.g. INFO, DEBUG) | INFO |
| POSTGRES_URL | Yes | PostgreSQL connection string (SQLAlchemy async URL) | |
| RERANKER_URL | No | URL of the reranker endpoint | http://localhost:8003 |
| GRAPH_ENABLED | No | Enable the relationship graph (Neo4j) | false |
| MCP_HTTP_TOKEEN | No | Bearer token for MCP HTTP endpoint (stored in private file) | |
| BRAIN_MCP_PROFILE | No | MCP tool catalog profile: 'compact' (default) or 'native' | compact |
| EMBEDDING_DIMENSION | No | Vector dimension for embeddings (<=2000, pgvector HNSW ceiling) | 1536 |
| BRAIN_RERANK_API_KEY | No | API key for external reranker service (stored in private file) | |
| BRAIN_RERANK_BACKEND | No | Reranker backend: 'shim' (default) or 'cohere' | shim |
| BRAIN_EMBEDDING_MODEL | No | Model name sent by the openai backend (e.g. 'qodo') | |
| EMBEDDING_SERVICE_URL | No | URL of the local unified embedding endpoint | http://localhost:8003 |
| MCP_HTTP_DREAM_TOKEENS | No | Bearer tokens for dream-mode HTTP endpoint (stored in private file) | |
| BRAIN_EMBEDDING_API_KEY | No | API key for external embedding service (stored in private file) | |
| BRAIN_EMBEDDING_BACKEND | No | Backend for embeddings: 'shim' (default) or 'openai' | shim |
| GRAPH_LEDGER_WRITE_ENABLED | No | Enable writes to the graph ledger | false |
| BRAIN_EMBEDDING_QUERY_PREFIX | No | Query prefix for asymmetric embedding models (e.g. 'query: ') | |
| BRAIN_EMBEDDING_DOCUMENT_PREFIX | No | Document prefix for asymmetric embedding models; change requires full re-embed |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| brain_session_startA | Start or replay a concurrent session from an explicit user command.
An agent tracer is the only session the server opens or closes on its own; no hook and no auto-close may invoke this lifecycle boundary. |
| brain_session_captureA | Attach durable artifacts from an explicit user command — to repair or refine. No longer a compulsory ritual. With derived capture armed, artifacts
created during the session are attributed without this call, and It never steals: an artifact already attributed stays where it is. An agent tracer is the only session the server opens or closes on its own; no hook and no auto-close may invoke this lifecycle boundary. |
| brain_session_heartbeatA | Refresh an open session from an explicit user command. An agent tracer is the only session the server opens or closes on its own; no hook and no auto-close may invoke this lifecycle boundary. |
| brain_session_endA | End a session from an explicit user command, on judgement alone.
What For a bound session, For an UNBOUND session, An agent tracer is the only session the server opens or closes on its own; no hook and no auto-close may invoke this lifecycle boundary. |
| brain_session_relayA | Relay an open session onto its slot, or its project base: capture, end, restart. One transaction: the named
Bound session: send Unbound session: send The same 70% guard applies to a bound slot body ( An equal replay returns the same successor with A guard mod the operator explicitly enabled may make this call as a standing
user command, and only this one (Amendment — slot relay (ADR #34)); with
An agent tracer is the only session the server opens or closes on its own; no hook and no auto-close may invoke this lifecycle boundary. |
| brain_session_listA | List sessions only in response to an explicit user command. An agent tracer is the only session the server opens or closes on its own; no hook and no auto-close may invoke this lifecycle boundary. |
| brain_session_resumeB | Resume an open session from an explicit user command. An agent tracer is the only session the server opens or closes on its own; no hook and no auto-close may invoke this lifecycle boundary. |
| brain_session_bindA | Bind an open operator session to one focus slot, from an explicit user command. Once per session; binding the same slot again is a replay. From then on the
session's An agent tracer is the only session the server opens or closes on its own; no hook and no auto-close may invoke this lifecycle boundary. |
| brain_session_abandonB | Abandon a session only from an explicit user command. An agent tracer is the only session the server opens or closes on its own; no hook and no auto-close may invoke this lifecycle boundary. |
| brain_find_toolA | Search for tools using natural language. Returns up to 5 matching tools ranked by relevance, each as a summary: name, one-line description, required parameters with types, optional parameter names. Pass an exact tool name to get that tool's full input schema. |
| brain_call_toolA | Call a tool by name with the given arguments. Use this to execute tools discovered via search_tools. |
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 11 tools
The nine brain_session_* tools each nominally target a distinct lifecycle action, and the verbose descriptions clarify nuances, but several boundaries overlap heavily — relay internally performs capture+end+start, making it confusable with end/start, and start vs resume vs bind blur together. An agent could plausibly pick the wrong lifecycle tool for a given situation.
All names are snake_case with a consistent brain_ prefix, so the set is readable. There is a minor structural deviation: session tools use brain_<noun>_<verb> (brain_session_start) while the meta tools use brain_<verb>_<noun> (brain_call_tool, brain_find_tool), but the pattern is still predictable.
11 tools is within the well-scoped 3-15 range. The session lifecycle legitimately needs many operations, though nine session tools plus two meta tools is on the heavier side for what is essentially one domain.
The session lifecycle is thoroughly covered — start, heartbeat, capture, resume, bind, relay, end, abandon, list — plus meta tools for discovery and invocation. The only notable gap is that slots/focus are referenced extensively in relay/end but no tool here creates or manages slots, leaving a potential dead end for that sub-resource.