claude-task-graph
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@claude-task-graph Create a task for the homepage redesign and link it to the wireframe idea."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
claude-task-graph
An MCP server + live graph viewer for Claude Code. Tasks, subtasks, ideas and discussion branches are stored as a graph and rendered live in your browser as a schematic-style diagram with connector lines — so you can skim the structure instead of reading walls of text, and tangents get parked as nodes instead of getting lost.
How it works
MCP server (stdio) exposes tools to Claude Code:
create_node,update_node,link_nodes,get_graph,delete_node.Viewer at
http://localhost:7300updates live over WebSocket while Claude works. Node border color = status, node shape = type (task / subtask / idea / discussion / note). Click a node for its full description and note log.Storage is a plain JSON file (
task-graph.jsonby default) — one graph per project directory, diffable, committable.
Related MCP server: visualize-chat-mcp
Install
git clone https://github.com/<you>/claude-task-graph.git
cd claude-task-graph
npm installHook into Claude Code
From the project directory where you want the graph:
claude mcp add task-graph -- node /path/to/claude-task-graph/src/server.jsThen copy the rules from CLAUDE.md.example into that project's
CLAUDE.md. Those rules are what make Claude actually maintain the graph:
register tasks before starting, park tangents as linked idea nodes, update
status as it goes.
Open http://localhost:7300 and keep it on a second screen.
Configuration
Env var | Default | Purpose |
|
| Where the graph is stored |
|
| Viewer HTTP/WebSocket port |
Set them in the claude mcp add command with -e if needed, e.g. a fixed
graph file shared across sessions:
claude mcp add task-graph -e TASK_GRAPH_FILE=$HOME/graphs/myproject.json -- node /path/to/claude-task-graph/src/server.jsNode types and relations
Types:
task,subtask,idea,discussion,note,finding,decision,bugStatuses:
pending,in-progress,done,blocked,parkedRelations:
subtask-of,depends-on(rendered dashed copper),spawned-from,discussion-of,related-to,found-in,decision-of
License
MIT
Available Tools
6 toolscreate_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.
Inputs: type (required), title (required), doc, status, +2 more.
delete_nodeA
Delete a node and all edges touching it. Only when the user explicitly asks.
Inputs: id (required).
get_graphA
Return the full current graph (all nodes and edges). Use to re-orient yourself at the start of a session.
Inputs: no named parameters.
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.
Inputs: nodes (required), edges.
link_nodesA
Create a directed edge between two existing nodes to show logical flow.
Inputs: to (required), from (required), relation.
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 note node via create_node so it is visible in the graph.
Inputs: id (required), doc, note, title, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Repository knowledge graph MCP server for codebase understanding and debugging.
A graph-based task manager your agent can read and update: tasks, dependencies, blockers.
Remote MCP server to read and edit GanttFather projects: tasks, dates, dependencies, critical path.
Remote MCP server for notes, tasks, kanban boards and docs - the Slates agentic workspace
Related MCP Servers
- AlicenseAqualityDmaintenanceA read-only task graph visualizer for Beads projects, running as an MCP server in Claude Desktop or VS Code Copilot to display interactive DAGs, list views, and stats dashboards.320 npm1MIT
- AlicenseBqualityDmaintenanceMCP server that visualizes Claude conversations as interactive mindmaps, enabling export and optional upload to Navigate Chat.2MIT
- FlicenseBqualityDmaintenancePersonal memory MCP server for Claude Code with an Obsidian-style graph. Enables persistent, queryable memories across sessions using Markdown files with bidirectional wiki-links and a D3.js force-directed graph UI.8-
- AlicenseBqualityCmaintenanceAn MCP server for AI-assisted project development and tracking. It exposes a typed graph of design nodes (concepts, decisions, requirements, etc.) and edges to Claude Code, enabling structured management of project knowledge and report generation.253Apache 2.0