claude-task-graph
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASK_GRAPH_FILE | No | Where the graph is stored | ./task-graph.json |
| TASK_GRAPH_PORT | No | Viewer HTTP/WebSocket port | 7300 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_nodeA | Create a node in the task graph. Use for every task, subtask, idea, discussion topic, note, finding (something learned), decision (with reasoning) or bug that comes up. If it grew out of another node, pass parent_id so the graph shows where it branched from. |
| update_nodeA | Update a node's title, description or status, and/or append a timestamped note. Notes are for the node's own status trail (why blocked, what the fix was); standalone information worth keeping should be its own |
| link_nodesA | Create a directed edge between two existing nodes to show logical flow. |
| import_graphA | Bulk-create many nodes and edges in one call. Use when reconstructing a graph from existing project history (e.g. context injected by a memory plugin such as claude-mem). Provide your own temporary ids in nodes[].ref and reference them in edges; real ids are assigned and returned as a ref->id map. |
| get_graphA | Return the full current graph (all nodes and edges). Use to re-orient yourself at the start of a session. |
| delete_nodeA | Delete a node and all edges touching it. Only when the user explicitly asks. |
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 6 tools
Each tool targets a distinct action: create, get, update, link, import, delete. Even create_node and import_graph are clearly separated by purpose (single vs bulk creation), with descriptions that prevent confusion.
All tool names follow a consistent verb_noun snake_case pattern (create_node, get_graph, update_node, link_nodes, import_graph, delete_node). The plural in link_nodes is a minor variation but still fits the overall structure.
Six tools is well-scoped for a task graph server. Each tool has a clear role, covering creation, retrieval, update, linking, bulk import, and deletion without unnecessary overlap or bloat.
The set covers core graph lifecycle operations (create, read, update, delete, link, import). Gaps include lack of explicit unlink and inability to change a node's parent_id via update_node, which may require workarounds like recreating nodes.