Skip to main content
Glama

Related Servers

Alternatives to jira-delivery-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      It enables agents to coordinate GitHub, Jira, and Notion around one Jira issue by creating linked branches and work docs, opening PRs with status transitions, and providing unified status, standup, and release-note views.
      10
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to automate Jira and GitHub/GitLab workflows. It handles issues, branches, pull requests, and deployments with project-aware context and safety checks.
      32
      82 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables an AI agent to retrieve assigned tickets and their context, assign and mark tickets in progress, create pull requests that close tickets, and move tickets through review and done states while leaving Git actions to the agent and merges to humans.
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI coding agent to scan a day's git commits across work repositories and group them into Jira tickets, creating or updating them with estimates and logged time. It also surfaces actionable, categorized errors so an agent knows what failed and whether to retry.
      MIT

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target clearly different stages: read (jira_get_issue), brief (jira_prepare_work_brief), verify (delivery_check_changes, delivery_traceability_matrix), and generate artifacts. The main risk is overlap between check_changes and traceability_matrix and between get_issue and prepare_work_brief, but descriptions explicitly steer callers between them.

    Naming Consistency4/5

    Consistent snake_case with meaningful domain prefixes (jira_, confluence_, delivery_), and most names are verb_noun. Minor deviations: delivery_project_patterns is a noun-only, multi-action tool (scan/get/clear) that breaks the pattern, and jira_prepare_work_brief sits under jira_ but is a workflow tool rather than a raw Jira verb.

    Tool Count5/5

    10 tools is squarely in the well-scoped range, with each covering a distinct delivery workflow step (read, search, brief, verify, generate). Nothing appears redundant or padding.

    Completeness3/5

    The read/verify/generate side of the lifecycle is well covered, but there are no write-back operations to Jira: no commenting, status transitions, or issue updates, which limits closing the loop after work is verified. Confluence is read-only, which is reasonable, but the missing Jira mutations are a notable gap for a delivery workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues