Skip to main content
Glama
SuppleAardvark

JIRA MCP Server

by SuppleAardvark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to JIRA MCP Server

No user-submitted related servers found.

    Related Servers

    • jiraxmcp

      vaibhavpandeyvpz
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for interacting with Jira Cloud, providing tools for issues, search, agile boards, comments, links, attachments, and webhook notifications.
      7 npm
      2
      MIT

    • mcp-jira-server

      r-kitaev
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for Jira that enables comprehensive issue management, sprint operations, comments, attachments, and batch processing with localization and flexible date support.
      625 npm
      2
      MIT

    • Jira MCP Server

      AlexVulaj
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for integrating with Jira Server instances, enabling natural language interactions to create, update, search, and manage issues and comments.
      73 npm
      1
      MIT

    • Jira Cloud MCP Server

      aaronsb
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for interacting with Jira Cloud instances. Enables issue management, JQL queries, project and sprint management, and batch operations via natural language interfaces.
      206 npm
      4
      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.8/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear separation between issues, sprints, boards, attachments, comments, and fields. Even similar tools like get_sprint_issues vs get_my_sprint_issues have explicit filters that differentiate them.

    Naming Consistency5/5

    All tools follow a consistent 'jira_' prefix followed by verb_noun (e.g., get_issue, create_issue, list_sprints). The verb set is predictable and the object is always the resource type, making the naming pattern uniform and intuitive.

    Tool Count3/5

    23 tools borders on heavy, but the complexity of JIRA's domain justifies a comprehensive set. That said, a more minimalist server could merge some functions (e.g., list_attachments with get_issue) to reduce count without losing clarity.

    Completeness4/5

    Core issue lifecycle (create, read, update, transition, comment, attachment) is fully covered, and sprint/board features are well represented. Missing delete, sprint creation/update, and project listing are minor gaps that agents can work around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources