Skip to main content
Glama
SunWooBang

Jira MCP Server

by SunWooBang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Jira MCP Server

No user-submitted related servers found.

    Related Servers

    • Atlassian Jira MCP Server

      aashari
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants like Claude to Jira projects, enabling natural language queries and operations for issue management, project tracking, comments, and workflows through the Jira REST API.
      11,532 npm
      77
      ISC

    • jira-mcp-server

      fkesheh
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants like Claude to interact with Jira for project management tasks, including issue creation, updates, workflow transitions, and bulk operations.
      19 npm
      4
      MIT

    • JIRA MCP Server

      rajsodhi-2
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude AI to interact with JIRA for project management and issue tracking, supporting JQL queries, comprehensive issue details retrieval with subtasks and linked issues, and release planning analysis.
      MIT

    • JIRA MCP Server

      CarloDeStefano90
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code to interact with JIRA through natural language, supporting issue creation, updates, searches, and workflow transitions, designed for enterprise intranets.
      22
      43 npm
      Apache 2.0

    • Jira MCP Server

      rui-branco
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to fetch and search Jira tickets, comments, and attachments directly within Claude Code. It features JQL support and automatically exports linked Figma designs to provide comprehensive project context.
      135 npm
      2
      MIT
    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 single tool 'example_tool' stands alone with a distinct purpose, so agents cannot misselect between multiple options.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'example_tool' follows a clear noun-based pattern, and with no other tools to compare, there are no inconsistencies in naming conventions.

    Tool Count2/5

    A single tool is too few for a server named 'Jira MCP Server', which implies a domain related to Jira project management. This minimal set fails to cover the expected scope, such as CRUD operations for issues, projects, or workflows, making it inadequate for typical agent tasks.

    Completeness1/5

    The tool set is severely incomplete for the Jira domain. With only an 'example_tool' that processes messages, it lacks any operations for managing issues, projects, users, or other Jira entities, leaving obvious gaps that will cause agent failures in real-world scenarios.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources