Skip to main content
Glama
proprock
by proprock

Related Servers

Alternatives to jira-mini-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Gives local coding agents safe, read-only access to an existing Jira instance through MCP over stdio, keeping Jira credentials out of the LLM. It exposes tools for reading issues, comments, linked items, JQL search results, assigned open issues, and project metadata.
      6
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides Jira Cloud integration for AI agents, enabling them to search issues with JQL, retrieve detailed issue information, and create new tickets. It supports multiple Jira configurations and provides tools for managing attachments and comments through natural language.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Provides tools for AI assistants to interact with JIRA APIs, enabling them to read, create, update, and manage JIRA issues through standardized MCP tools.
      6
      14 npm
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Jira Cloud tickets, including listing, searching, creating, and updating issues through a set of MCP tools.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with JIRA through MCP, providing 35 tools for issues, comments, transitions, projects, boards, sprints, epics, links, worklogs, versions, attachments, users, and fields.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants and agents to retrieve, inspect, update, complete, transition, search, and comment on Jira issues across Cloud and Data Center/Server via the Model Context Protocol.
      9
      MIT

    TDQS

    A4.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: search vs. fetch, comments, attachment metadata vs. download, changelog, add comment, transition, update. The get_issue description explicitly excludes comments, attachments, and changelog, and get_attachments vs. download_attachment are clearly separated by metadata vs. content.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores: search_issues, get_issue, get_comments, get_attachments, download_attachment, get_changelog, add_comment, transition_issue, update_issue. No mixing of conventions.

    Tool Count5/5

    9 tools is well within the ideal 3-15 range, and each tool covers a distinct aspect of Jira issue interaction without redundancy or bloat.

    Completeness2/5

    The set is missing create_issue and delete_issue, which are core lifecycle operations for an issue tracker. While it covers reading, updating, transitioning, and adding comments, the absence of create/delete is a significant gap that will cause agent failures when those actions are needed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues