Skip to main content
Glama
pedrohedro

Jira MCP Server

by pedrohedro

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
      30 npm
      1
      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.
      11,401 npm
      74
      ISC
    • 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.
      25 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude to Jira and Confluence, enabling natural language research, design with Mermaid diagrams, documentation writing, and ticket creation without needing an Anthropic API key.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code to interact with JIRA through natural language, supporting issue creation, updates, searches, and workflow transitions, designed for enterprise intranets.
      22
      30 npm
      Apache 2.0

    TDQS

    B3.1/5.0

    Scored across 22 tools

    Disambiguation2/5

    Several tools overlap in purpose: list_my_tasks, list_subtasks, list_sprint_active, list_in_development, and list_my_board_tasks all list tasks assigned to the current user with only subtle filter differences. custom_query can also replicate these searches, making tool boundaries unclear.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun snake_case pattern (e.g., list_projects, create_issue, add_comment, get_confluence_page). Minor deviations include custom_query (not verb_noun) and update_issue_status (three-part), but the overall style is predictable.

    Tool Count3/5

    With 22 tools, the server is on the heavier side for a Jira+Confluence integration. While not extreme, the count falls in the 16-25 range that feels somewhat bloated but still manageable for the scope.

    Completeness3/5

    Core workflows are covered: issue creation/update/status, comments, worklogs, attachments, JQL queries, and Confluence get/search/create/update. However, there is no direct get_issue by key, no delete operations for issues/comments/worklogs/attachments, and no Confluence space listing, leaving notable gaps that require workarounds.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues