thought-graph-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THOUGHT_GRAPH_DIR | No | Override the default session artifacts directory. Defaults to ~/thought-graph-sessions/. | ~/thought-graph-sessions |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| begin_thinkingA | Start a new Thought Graph reasoning session for a complex problem. Returns a sessionId and the protocol instructions. Call this FIRST, then build the reasoning with add_thought. |
| add_thoughtA | Record one reasoning step (a graph node). Keep it to a single idea. Use |
| get_sessionA | Return the current reasoning graph as JSON (all nodes, edges, statuses) plus on-disk artifact paths. Use this to review where things stand or recover the exact graph file path. |
| revise_stepA | Pinpoint a specific step by node id, mark it superseded, and replace it with a fresh |
| finalize_thinkingA | Record the final synthesized answer for the session and refresh the artifacts. Call after the graph supports a conclusion. |
| list_sessionsA | List existing Thought Graph sessions (id, title, step count) found on disk. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| decompose | Reason about a complex problem as an explicit, editable thought graph. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clear, distinct purpose: starting a session, adding steps, revising, finalizing, and retrieving sessions. No overlap or ambiguity.
All tools use underscore_case with a verb_noun or verb_gerund pattern (e.g., add_thought, begin_thinking, list_sessions), maintaining consistency throughout.
6 tools is well-scoped for a reasoning graph system, covering core operations without unnecessary bloat.
Covers the essential lifecycle: start, add, revise, finalize, and retrieve. Missing explicit deletion of sessions or thoughts, but these are minor gaps.