Skip to main content
Glama

Related Servers

Alternatives to JIRA MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      D
      maintenance
      Connects Jira with Claude, enabling users to search issues, view issue details, update issues, add comments, and retrieve project information through natural language commands.
      1
      73 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude AI to interact with JIRA for project management and issue tracking, supporting JQL queries, comprehensive issue details retrieval with subtasks and linked issues, and release planning analysis.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants like Claude to interact with Jira for project management tasks, including issue creation, updates, workflow transitions, and bulk operations.
      33 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to fetch and search Jira tickets, comments, and attachments directly within Claude Code. It features JQL support and automatically exports linked Figma designs to provide comprehensive project context.
      441 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants like Claude to Jira projects, enabling natural language queries and operations for issue management, project tracking, comments, and workflows through the Jira REST API.
      15,675 npm
      77
      ISC

    TDQS

    A3.6/5.0

    Scored across 22 tools

    Disambiguation5/5

    Tools are clearly separated by prefixes (confluence_, jira_, xray_), and each tool targets a distinct action on a specific resource. There is no overlap or ambiguity between tools, as even similar operations like adding comments are scoped to different platforms.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case, prefixed by platform (confluence_, jira_, xray_). This makes the naming predictable and easy for agents to parse and select tools.

    Tool Count5/5

    With 22 tools covering Jira, Confluence, and Xray, the count is well-scoped for a combined server. It provides enough functionality without overwhelming the agent, and each tool serves a clear purpose.

    Completeness4/5

    The set covers core CRUD-like operations for both Jira and Confluence, including search, comments, transitions, and project roles. Missing delete operations (common in MCP) and some advanced features, but the main workflows are supported. The Xray tool is limited but fits the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues