Skip to main content
Glama
rwese

MCP Backlog Server

by rwese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP Backlog Server

No user-submitted related servers found.

    Related Servers

    • aiboard

      flashist
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to manage a filesystem-based issue tracker through typed MCP tools such as list_tasks, create_task, change_task_status, log_work, and get_sprint, instead of shelling out to a CLI. Tasks and sprints are plain folders of Markdown files, so agents can create, claim, comment on, and move work by topic without any database or server state.
      MIT

    • Agile Planner MCP Server

      cyberlife-coder
      A
      license
      Not graded
      quality
      D
      maintenance
      Automatically generates structured agile backlogs including epics, features, and user stories from natural language descriptions within AI-powered IDEs. It streamlines project management by creating AI-optimized markdown files and directory structures to guide step-by-step implementation.
      11 npm
      3
      MIT

    • Backlog MCP Server

      gkoreli
      A
      license
      B
      quality
      A
      maintenance
      Enables managing a minimal task backlog with operations to create, list, update, and retrieve tasks with different statuses (open, in progress, blocked, done, cancelled). Tasks are stored in a local JSON file with atomic writes.
      28
      264 npm
      5
      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.
      -

    • Workfile

      illodev
      A
      license
      A
      quality
      A
      maintenance
      Repository-native protocol and MCP server for coordinating work items, documentation, changelogs, and project memory between humans and AI agents, using Markdown files in a Git repository as the canonical data source.
      30
      3
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Tools are mostly distinct, but 'done' and 'ticket-done' could confuse an agent as both mark items complete; similarly 'read' vs 'ticket-read' and 'write' vs 'ticket-write' are pairs with overlapping purposes, though descriptions clarify the backlog vs ticket context.

    Naming Consistency3/5

    Naming is inconsistent: plain verbs (done, prune, read, write) and noun-verb with hyphen (ticket-done, ticket-read, ticket-write) mix styles. The verb placement also varies (verb-first vs noun-first).

    Tool Count5/5

    Seven tools is a reasonable number for managing backlog items and tickets, covering necessary operations without excess or deficiency.

    Completeness4/5

    The tool set covers core CRUD-like operations for both backlog items and tickets, including creation, reading, updating, completing, and pruning. Minor gaps include lack of explicit delete for backlog items or tickets (beyond pruning), but these are not severe.

    Maintenance

    ActivityInactive
    ResponsivenessResponsive

    Resources