Skip to main content
Glama

Related Servers

Alternatives to jira-stories

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Code CLI to interact with Jira, including fetching issue details, searching issues with JQL, retrieving comments, and getting user info, with support for multiple Jira environments.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables local MCP-based interaction with Jira Cloud, offering tools for issues, comments, transitions, worklogs, attachments, and user lookups while addressing gaps like attachment downloads, mention notifications, and multi-step status transitions.
      409 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables Claude Code to interact with JIRA through natural language, supporting issue creation, updates, searches, and workflow transitions, designed for enterprise intranets.
      22
      51 npm
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Jira issues via JQL search, epic management, comments, attachments, and issue CRUD, with support for both Cloud and Server/Data Center instances.
      9
      12 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools target clearly distinct actions: list projects, get metadata, search issues, preview, create, and update. The main potential confusion is between jira_get_create_fields and jira_preview_issue, since both relate to issue creation fields, though one describes the schema and the other previews actual values.

    Naming Consistency5/5

    Every tool follows the same jira_<verb>_<noun> pattern using snake_case. The verbs are clear and consistently used, making the tool set highly predictable.

    Tool Count5/5

    Seven tools is well-scoped for a Jira issue creation/update workflow. Each tool serves a necessary step in the process without unnecessary redundancy.

    Completeness4/5

    The workflow covers project discovery, issue type/field metadata, duplicate checking, preview, creation, and update. A direct get-single-issue tool is missing but search can serve that purpose, and deeper Jira lifecycle operations like transitions are outside the apparent scope.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues