Skip to main content
Glama
namcpgem

Jira MCP

by namcpgem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Jira MCP

No user-submitted related servers found.

    Related Servers

    • MCP Jira

      amruthabesto28
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Jira Cloud and Server/Data Center deployments for issue management, project tracking, and workflow automation. Supports multiple authentication methods including API tokens, OAuth 2.0, and personal access tokens.
      MIT

    • jira-mcp

      thammarongg
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to access and manage Jira boards, sprints, epics, issues, JQL searches, transitions, comments, worklogs, projects, users, and any REST endpoint across Jira Cloud and Data Center.
      43
      216 npm
      MIT

    • Jira MCP

      cup0ra
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to search, read, create, and update Jira Server/Data Center issues, comments, and attachments, and to move issues through workflow transitions using Personal Access Token authentication. It also supports file uploads and downloads from allowlisted local paths, plus paginated search and issue-detail retrieval including links and attachment metadata.
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.6/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., add_comment vs update_comment vs delete_comment; log_work vs update_worklog vs delete_worklog). The only potential overlap is update_ticket vs transition_ticket, but descriptions clearly separate field updates from status changes.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (get_ticket, create_ticket, add_comment, delete_worklog, etc.). Minor variations like move_to_sprint and generate_release_notes remain readable and do not break the overall convention.

    Tool Count4/5

    17 tools is slightly above the typical 3-15 range, but each tool covers a necessary Jira operation with no obvious redundancy. The count is justified by the breadth of ticket management tasks.

    Completeness4/5

    The set covers core ticket lifecycle operations (create, read, update, search, transition, comments, worklogs, watchers, links) but lacks delete_ticket and some project/sprint management functions. Agents can work around most gaps using JQL and existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources