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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/PontusO/iLabs_task_graph'
If you have feedback or need assistance with the MCP directory API, please join our Discord server