Skip to main content
Glama
corbym

backlog-mcp

by corbym
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Related Servers

Alternatives to backlog-mcp

Related Servers

  • 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

  • MATRIX

    aminfara
    A
    license
    Not graded
    quality
    B
    maintenance
    A local, project-scoped requirement management MCP server that enables AI agents to manage tasks and requirements via SQLite.
    8 npm
    MIT

  • primer-mcp

    ivanlai
    A
    license
    A
    quality
    B
    maintenance
    A Jira-lite MCP server that enables planning-first workflows for AI-assisted development. It manages tickets as markdown files with YAML frontmatter, guiding agents through epics, stories, tasks, and architecture decision records.
    17
    MIT

  • EngiMCP

    GreenLordUA
    A
    license
    B
    quality
    B
    maintenance
    An MCP server that gives LLM agents structured, safe, and traceable access to engineering project documentation stored in Markdown/Git repositories, enabling management of requirements, decisions, tests, tasks, and impact analysis.
    14
    6 npm
    MIT

  • Trellis MCP

    langadventurellc
    A
    license
    Not graded
    quality
    D
    maintenance
    A file-backed MCP server for hierarchical project management that enables AI assistants to create, claim, and complete tasks within a project→epic→feature→task structure, with dependency management and Markdown-based storage.
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 16 tools

Disambiguation4/5

Most tools target distinct resources/actions, but there is some overlap between single-item and bulk operations (e.g., set_story_status vs. bulk_update_stories; check_acceptance_criterion vs. bulk_update_acceptance_criteria). The descriptions mitigate this by clarifying scope and validation behavior, so an agent could usually select correctly with careful reading.

Naming Consistency5/5

Tool names consistently follow a verb_noun snake_case pattern (get_story, create_epic, set_story_status, bulk_update_epics, reorder_backlog). Even less common verbs like groom_epic and complete_story fit the same pattern, making the naming convention predictable and coherent.

Tool Count4/5

Sixteen tools is slightly above the typical well-scoped range, but the server covers epics, stories, statuses, acceptance criteria, notes, batching, and backlog ordering. A few bulk operations feel redundant with single-item variants, but overall the count is still appropriate for the domain.

Completeness3/5

The set covers creation, reading, status updates, acceptance criteria management, note-taking, completion, grooming, and reordering. However, there are notable gaps: no way to delete or truly edit an epic/story, no dedicated tool to fetch a single epic's full content, and no direct story content update beyond status/AC/notes, which agents may need for full lifecycle management.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources