Skip to main content
Glama
hakenshi

Agentic Backlog MCP Server

by hakenshi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Agentic Backlog MCP Server

No user-submitted related servers found.

    Related Servers

    • project-tasks-mcp

      augustoOliveira1993
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables managing projects, features, tasks, dependencies, executions, and human review through a Streamable HTTP endpoint, along with persistent inter-agent cooperation via task messaging and event subscriptions. It also supports administrative actions such as approvals, cancellations, unblocking, and member management.
      -

    • sprinter

      danimoya
      A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted backlog tracker with priority scoring and an MCP server, enabling AI agents to autonomously pull, work on, and update tasks via JSON-RPC tools.
      MIT

    • todo-mcp

      Karsten-Larson
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage a local-first Kanban board with Azure DevOps-style workflow rules, including task creation, status updates, subtask breakdown, full-text search, daily summaries, and next-task suggestions.
      -

    • MCP Task Manager Server

      bsmi021
      A
      license
      A
      quality
      D
      maintenance
      A local Model Context Protocol server providing backend tools for AI agents to manage projects and tasks with persistent storage in SQLite, enabling structured tracking of project tasks with dependencies, priorities, and statuses.
      12
      3 npm
      25
      GPL 3.0
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    C2.9/5.0

    Scored across 22 tools

    Disambiguation3/5

    Many tools are distinct, but there are several overlapping boundaries: get_board and get_console_table both return board snapshots, update_task/update_task_by_title/update_task_status all mutate tasks, and get_focus/list_tasks overlap as list-like views. Descriptions help, but an agent could easily pick the wrong one for state changes or snapshot retrieval.

    Naming Consistency4/5

    Names consistently use the backlog. prefix with snake_case verb_noun construction (list_tasks, create_task, update_task). Minor deviations are bare nouns health and version and the looser get_/list_ distinction, but the overall pattern is predictable and readable.

    Tool Count3/5

    22 tools is on the heavy side and sits in the 16-25 borderline range. Many could be consolidated (board formats, update variants, health/version), though the broad project/task/planning/claim domain explains some of the volume.

    Completeness4/5

    The surface covers task CRUD well, including restore, status transitions, notes, claims, board snapshots, focus, and planning. Minor gaps exist such as no project update/delete and limited search beyond title keywords, but core agent workflows do not hit dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources