mind-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROOT | Yes | The root directory of the project (corresponds to --root argument) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mind_readB | Read a file inside .mind/ by relative path. |
| mind_routeA | Return the routing table from INDEX.md. |
| mind_recallB | Search memory/ and context/ files by substring query. |
| mind_propose_writeC | Create a .mind/diff/*.md proposing a change to a target file. |
| mind_listB | List markdown files under a subdirectory of .mind/. |
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 5 tools
Each tool has a clearly distinct purpose: listing, reading, writing proposals, searching, and retrieving routing tables. No overlap or ambiguity.
All tools follow the 'mind_verb' pattern with snake_case, including 'mind_propose_write' which uses a compound verb. The naming is consistent and predictable.
With 5 tools, the set is well-scoped for memory/context management. It covers listing, reading, writing proposals, searching, and routing without being too sparse or excessive.
The set covers core operations but lacks delete or direct update tools. However, the proposal-based workflow may compensate, leaving only minor gaps.