Skip to main content
Glama
PontusO

claude-task-graph

by PontusO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to claude-task-graph

No user-submitted related servers found.

    Related Servers

    • redraft

      KaelinGraf
      A
      license
      B
      quality
      C
      maintenance
      An 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.
      25
      3
      Apache 2.0

    • memory-mcp

      otaviosenne
      A
      license
      B
      quality
      D
      maintenance
      Personal 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
      10 npm
      MIT

    • taskops

      bernatch22
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Claude Code agents to manage persistent shared task boards with dependency graphs, atomic claims, and git-bound tasks.
      11
      MIT

    • beads-viz

      pyros-projects
      A
      license
      A
      quality
      D
      maintenance
      A 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.
      3
      20 npm
      1
      MIT

    • coding-os

      kouroshez
      A
      license
      B
      quality
      A
      maintenance
      MCP 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.
      89
      116 PyPI
      6
      Apache 2.0
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityStale
    ResponsivenessNo issues

    Resources