Skip to main content
Glama
IvanBBaev

jira-mcp-ai

by IvanBBaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to jira-mcp-ai

No user-submitted related servers found.

    Related Servers

    • jira-mcp

      Pandacli
      A
      license
      Not graded
      quality
      C
      maintenance
      A lightweight MCP server for self-hosted Jira Server, exposing REST API v2 tools for search, issue creation/update, transitions, comments, and more to AI clients via MCP protocol.
      MIT

    • Jira MCP OAuth gateway

      Wasim-Shaikh25
      F
      license
      B
      quality
      C
      maintenance
      MCP server that connects AI assistants to your Jira site, supporting PAT or SSO authentication for search, read, create, update, and delete operations on issues.
      17
      45 npm
      -

    • jira-mcp-bridge

      erollando
      A
      license
      Not graded
      quality
      D
      maintenance
      A local-only MCP server providing safe, typed Jira tools for AI agents via Atlassian ACLI, enabling search, get issue, add comment, and transition issues with policy guardrails.
      MIT

    • mcp-jira-server

      dev-pradeep-singh
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides AI assistants with access to Jira Cloud for issue management, search, and workflow operations.
      -

    • mcp-jira

      judexzhu
      F
      license
      A
      quality
      C
      maintenance
      An async MCP server for JIRA integration, enabling AI assistants to search, create, and manage JIRA issues via JQL and other operations.
      6
      2
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 52 tools

    Disambiguation5/5

    Every tool maps to a distinct resource/action pair, and the verbose descriptions actively disambiguate near-neighbors: jira_get_sprint_issues is scoped by sprint, jira_search by JQL, and jira_get_create_meta is separated from jira_list_fields by focusing on the create screen. Overlap exists only where Jira itself exposes similar concepts, and the descriptions handle it.

    Naming Consistency4/5

    All 52 tools use the jira_ prefix and snake_case, and most follow a clear verb_noun pattern: get_issue, list_sprnts, create_component, delete_worklog. The exceptions—jira_search, jira_count, and jira_capabilities—deviate slightly from that pattern, but the overall convention is highly predictable.

    Tool Count1/5

    52 tools is an extreme surface for one MCP server, crossing the rubric's 50+ threshold. Even though Jira is a broad domain, the sheer number of resource/action pairs makes selection heavy and increases the chance of mispicks.

    Completeness4/5

    The core issue lifecycle is well covered: create, get, update, delete, transition, assign, link, comments, worklogs, attachments, watchers, votes, and sprint management. Gaps like no component/version delete, no filter create/update/delete, and no worklog update are present but mostly affect secondary workflow edges rather than blocking primary use.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources