Skip to main content
Glama
cfollette18

Jira MCP

by cfollette18
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Jira MCP

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.
      529 npm
      MIT

    • MCP Jira Server

      edrich13
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for interacting with self-hosted Jira instances using Personal Access Token (PAT) authentication. It enables users to perform CRUD operations on issues, search with JQL, manage comments, and list projects through the Jira REST API.
      12
      627 npm
      13
      MIT

    • Jira MCP OAuth gateway

      Wasim-Shaikh25
      F
      license
      B
      quality
      B
      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
      110 npm
      -

    • 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

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    get_issue and create_issue have unambiguous, non-overlapping purposes — one reads, one writes. An agent can select correctly without hesitation.

    Naming Consistency5/5

    Both tools follow a clean, predictable verb_noun snake_case pattern (get_issue, create_issue), consistent with common MCP conventions.

    Tool Count2/5

    Only 2 tools for a server branded as a general 'Jira MCP' is thin; it covers just a narrow read/create slice of the Jira domain and leaves the set feeling minimally scoped.

    Completeness3/5

    Create and get are present but there is no update, delete, search, transition, or comment operation, so agents hit dead ends for common Jira workflows. The narrow customfield focus partially excuses the gap but not fully.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources