Skip to main content
Glama
Naveen-Automation

Jira MCP Server

by Naveen-Automation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Jira MCP Server

No user-submitted related servers found.

    Related Servers

    • jira-mcp

      skurekjakub
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables headless Jira Cloud automation via MCP: create issues and subtasks, read and JQL-search issues, inspect agile boards and swimlanes, move issues through workflows, and add comments and attachments.
      522 npm
      MIT

    • jira-mcp

      EllGree
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables local MCP-based interaction with Jira Cloud, offering tools for issues, comments, transitions, worklogs, attachments, and user lookups while addressing gaps like attachment downloads, mention notifications, and multi-step status transitions.
      522 npm
      MIT

    • jira-mcp

      LesterAJohn
      A
      license
      Not graded
      quality
      C
      maintenance
      Jira Cloud MCP server providing Jira-first tools for common workflows and full REST API coverage through a generic request tool.
      522 npm
      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.
      121 npm
      4
      MIT

    • JIRA MCP Server

      scarnyc
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with JIRA through MCP, providing 35 tools for issues, comments, transitions, projects, boards, sprints, epics, links, worklogs, versions, attachments, users, and fields.
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    C2.9/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but some overlap exists among board/sprint/issue-data retrieval tools (e.g., getJiraBoardIssueData vs searchJiraIssuesUsingJql) and version tools. Descriptions generally clarify boundaries well enough for an agent to select correctly.

    Naming Consistency4/5

    Names mostly follow a verb + Jira + noun pattern (e.g., getJiraIssue, listJiraProjects, createJiraIssue). Minor deviations like uploadAttachmentToJiraIssue and searchJiraIssuesUsingJql break the pattern slightly but remain readable and predictable.

    Tool Count2/5

    41 tools is heavy for a single MCP server and exceeds the 25+ threshold for being too many. Many operations could be consolidated (e.g., list/get/manage variants across issues, boards, and versions).

    Completeness3/5

    The surface covers broad read/write operations for issues, comments, worklogs, links, attachments, users, projects, versions, boards, sprints, filters, dashboards, and properties. However, delete operations are largely missing for issues, comments, worklogs, links, attachments, and boards/sprints/filters/dashboards, leaving notable lifecycle gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources