Skip to main content
Glama
w-10-m

Jira Enterprise MCP

by w-10-m
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Jira Enterprise MCP

No user-submitted related servers found.

    Related Servers

    • 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-dev-mcp

      nianyi778
      A
      license
      A
      quality
      F
      maintenance
      A local MCP server for Jira Cloud-driven development. Connects MCP clients to Jira for searching issues, reading tasks, parsing attachments, and mapping projects to local repos.
      10
      22 npm
      MIT

    • jira-mcp

      ibacher
      F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that wraps the Jira REST API v3, enabling issue management, searching, commenting, and transitions for openmrs.atlassian.net via Basic Auth.
      1
      -

    • 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
    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 17 tools

    Disambiguation4/5

    Most tools have distinct purposes, but `jira_add_attachment` and `jira_add_comment_with_attachment` overlap in attachment functionality, potentially causing misselection. Descriptions help clarify, so ambiguity is minimal.

    Naming Consistency5/5

    All tools follow the `jira_verb_noun` pattern consistently. Naming is predictable and clear, with only minor exceptions like `search` (no noun) which is still unambiguous.

    Tool Count4/5

    17 tools is slightly above the typical well-scoped range but reasonable for a complex system like Jira. The set covers many aspects without being excessive.

    Completeness3/5

    Core issue operations (create, read, update, transition) are covered, but a delete issue tool is missing. Other gaps like project management and user operations are acceptable for a focused MCP server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources