Skip to main content
Glama
sespinosa

Jira MCP Server

by sespinosa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Jira MCP Server

No user-submitted related servers found.

    Related Servers

    • Jira MCP Server

      samuelrizzo
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants like Claude to interact with Jira, allowing for project management tasks such as listing projects, searching issues, creating tickets, and managing sprints through natural language queries.
      7
      30 npm
      2
      TypeScript
      MIT

    • Jira MCP Server

      stolostron
      A
      license
      Not graded
      quality
      B
      maintenance
      A Model Context Protocol server that enables AI applications to interact with Jira issues, projects, and workflows through a standardized interface.
      2
      Apache 2.0

    • JIRA MCP

      MankowskiNick
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server for integrating JIRA with Claude, enabling AI assistants to create, search, update, and link JIRA tickets, as well as manage Zephyr test steps through natural language.
      328 npm
      7
      MIT

    • Jira MCP Server

      maximepeabody
      A
      license
      Not graded
      quality
      D
      maintenance
      A Simple Model Context Protocol server that enables AI assistants to interact with Jira, allowing operations like fetching tickets, adding comments, and updating ticket status.
      1
      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.8/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'example_tool' stands alone with a distinct purpose, so agents cannot misselect between multiple options.

    Naming Consistency5/5

    The single tool name 'example_tool' follows a consistent snake_case pattern. Since there is only one tool, there is no inconsistency in naming conventions to evaluate.

    Tool Count2/5

    A Jira MCP server with only one tool is too few for the apparent scope of Jira, which typically involves managing issues, projects, users, and workflows. This minimal tool count suggests an incomplete or trivial implementation.

    Completeness1/5

    The tool set is severely incomplete for a Jira server. With only an 'example_tool' that processes messages, there are no tools for core Jira operations like creating, updating, or querying issues, which are essential for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources