Brain-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Runtime environment (development/production) | |
| BRAIN_MCP_STORAGE_PATH | No | The storage path for memory data | ./memory_data |
| BRAIN_MCP_AUTO_SAVE_INTERVAL | No | Auto-save interval in milliseconds (default is 5 minutes) | 300000 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| addShortTermMemoryB | Add a temporary memory to the short-term cache (FIFO, limited capacity) |
| getShortTermMemoryB | Retrieve all short-term memories (newest first) |
| clearShortTermMemoryB | Clear all short-term memories |
| addLongTermMemoryB | Create a new persistent memory node with optional associations to other nodes |
| getLongTermMemoryB | Retrieve a memory node by ID with its associations up to specified depth |
| searchLongTermMemoryB | Search memory nodes by keyword (text matching) |
| updateLongTermMemoryB | Update a memory node's text and/or associations |
| deleteLongTermMemoryB | Delete a memory node and remove it from all associations |
| getAssociationsB | Get all direct association IDs of a memory node |
| saveMemoryB | Manually trigger saving all long-term memories to disk |
| getMemoryStatsB | Get statistics about the memory system |
| startThoughtProcessB | Start a new thought process chain with a goal |
| addThoughtB | Add a thought to an existing thought chain |
| branchThoughtB | Create a branch from an existing thought to explore alternative paths |
| evaluateThoughtC | Evaluate and update the confidence level of a thought |
| completeThoughtProcessB | Mark a thought process as complete and store the conclusion |
| getCurrentThoughtChainB | Retrieve the current state of a thought chain with all thoughts |
| pauseThinkingB | Pause an active thought process |
| resumeThinkingB | Resume a paused thought process |
| switchCognitiveModeC | Switch the cognitive mode for thinking processes |
| getOptimalModeForTaskB | Get the recommended cognitive mode for a specific task type |
| getThinkingProgressB | Get progress statistics for a thought chain |
| getActiveChainsB | Get all currently active thought chains |
| getThinkingStatsB | Get overall thinking process statistics |
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 24 tools
Most tools have distinct purposes, but some overlap exists. For example, 'getThinkingProgress' and 'getThinkingStats' both provide statistics about thinking processes, which could cause confusion. However, the descriptions clarify that one focuses on a specific thought chain while the other gives overall statistics, helping to differentiate them.
Tool names follow a highly consistent verb_noun pattern throughout, such as 'addLongTermMemory', 'getActiveChains', and 'updateLongTermMemory'. All tools use camelCase with clear, descriptive verbs and nouns, making them predictable and easy to understand.
With 24 tools, the count is borderline high for a cognitive processing server. While the domain is complex, this many tools might feel heavy and could overwhelm agents, though each tool appears to serve a specific function in memory and thought management.
The tool set provides comprehensive coverage for cognitive processing, including CRUD operations for memories (add, get, update, delete), thought chain management (start, branch, complete, pause, resume), and system monitoring (stats, progress). There are no obvious gaps, supporting full lifecycle management of thoughts and memories.