Skip to main content
Glama
cosmix

JIRA MCP Server

by cosmix

Related Servers

Alternatives to JIRA MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive interaction with JIRA through the Model Context Protocol, supporting issue management, search, comments, attachments, workflow transitions, and custom fields with enterprise Kerberos authentication.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Jira instances via the Model Context Protocol, providing 36 tools for reading and writing issues, projects, sprints, metrics, and more.
      24 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Jira for managing projects, issues, tasks, and workflows through the Model Context Protocol, allowing users to delegate PM tasks through Claude Desktop.
      25 npm
      64
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides comprehensive access to Jira Cloud and Data Center instances for managing issues, epics, and attachments with AI-optimized data cleaning. It supports relationship tracking and dual transport modes via STDIO and Streamable HTTP.
      328 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A Model Context Protocol server that enables AI applications to interact with Jira issues, projects, and workflows through a standardized interface.
      2
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol server that provides integration with Jira, allowing Large Language Models to interact with Jira projects, boards, sprints, and issues through natural language.
      5
      30 npm
      3
      MIT

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific JIRA operations: create, get, update, search, transition, add attachments/comments, and get epic children. There is no overlap or ambiguity between tools like 'get_issue' and 'search_issues' or 'update_issue' and 'transition_issue', making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern with snake_case throughout (e.g., create_issue, get_issue, update_issue). The verbs are appropriate and predictable, with no mixing of conventions or styles, ensuring readability and coherence.

    Tool Count5/5

    With 9 tools, the server is well-scoped for JIRA operations, covering core workflows like issue management, searching, and status transitions. Each tool earns its place without being overly sparse or bloated, fitting typical server sizes of 3-15 tools.

    Completeness4/5

    The tool set provides strong coverage for JIRA issue lifecycle, including CRUD operations (create, get, update), searching, transitions, and attachments/comments. A minor gap exists with no delete_issue tool, but agents can work around this, and other operations like epic handling are partially covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues