claude-task-graph
Related Servers
Alternatives to claude-task-graph
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn 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.3Apache 2.0
- AlicenseBqualityDmaintenancePersonal 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.820 npmMIT
- AlicenseAqualityAmaintenanceMCP server for Claude Code agents to manage persistent shared task boards with dependency graphs, atomic claims, and git-bound tasks.11MIT
- 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
- AlicenseBqualityAmaintenanceMCP server for coding-os, a cognitive operating system that gives AI agents memory, structure, and discipline. It exposes tools for project management, task tracking, knowledge graphs, and cognition traces to Claude Code and Codex.876Apache 2.0
- AlicenseBqualityDmaintenanceMCP server that visualizes Claude conversations as interactive mindmaps, enabling export and optional upload to Navigate Chat.27 npmMIT
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.