Skip to main content
Glama
razvancanuci

Jira Issue MCP Server

by razvancanuci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Jira Issue MCP Server

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
      339 npm
      13
      MIT

    • Jira MCP

      cfollette18
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to read and create Jira issues against Jira Cloud or Data Center through a self-hosted FastMCP server with secure authentication and configurable fields.
      2
      MIT

    • MCP JIRA Server

      Warzuponus
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI applications to manage JIRA issues, workflows, and tasks through a standardized MCP interface, facilitating real-time updates and seamless interaction with JIRA's API.
      10
      MIT

    • Jira MCP Server

      ilidaniys
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to interact with Jira for managing tasks, including fetching assigned issues and creating new tasks. It supports retrieving detailed task information and filtering by project or status using the Jira API.
      30 npm
      Apache 2.0
    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

    C2.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: create_issue handles issue creation, get_accessible_resources lists general resources, and get_projects focuses specifically on projects. There is no overlap or ambiguity between these functions.

    Naming Consistency4/5

    The naming is mostly consistent with a verb_noun pattern (create_issue, get_projects), but get_accessible_resources uses a more descriptive adjective, slightly deviating from pure verb_noun. Overall, it remains readable and predictable.

    Tool Count2/5

    With only 3 tools for a Jira server, the count feels too thin for the domain. Jira typically involves CRUD operations on issues, projects, and other resources, so this limited set is insufficient for comprehensive coverage.

    Completeness2/5

    The tool surface is significantly incomplete for a Jira server. It includes create_issue but lacks get_issue, update_issue, and delete_issue, and while get_projects is present, other common operations like search_issues or manage_workflows are missing, leading to potential agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources