Skip to main content
Glama
jondoesflow

Jira MCP Server

by jondoesflow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Jira MCP Server

No user-submitted related servers found.

    Related Servers

    • Jira MCP Server

      GalkinV
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Jira issue management through natural language, including viewing, searching, creating, updating, and transitioning tasks via JQL and API operations.
      -

    • Jira MCP Server

      pdogra1299
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Jira Cloud instances for comprehensive issue management including creating, updating, searching issues, managing comments, workflow transitions, and project metadata discovery. Supports JQL queries, user search, and custom field operations with secure API token authentication.
      12
      1,883 npm
      8
      MIT

    • Jira MCP Integration

      Koveh
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with Jira Cloud through the REST API, supporting project management, issue operations (create, read, update, delete), JQL search, task assignments, and status transitions.
      -

    • Jira MCP

      icy-r
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage Jira Cloud instances, including creating and updating issues, managing sprints and projects, adding comments, tracking worklogs, and searching with presets.
      4 npm
      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

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap. For example, create_issue, get_issue, and update_issue handle different lifecycle stages, while get_my_issues and search_issues serve different query needs. The descriptions reinforce these distinctions, making tool selection unambiguous.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern (e.g., add_comment, create_issue, get_issue). There are no deviations in style or convention, making the set predictable and easy to parse for an agent.

    Tool Count5/5

    With 8 tools, this server is well-scoped for Jira operations, covering core workflows like issue management and project queries. Each tool serves a clear purpose without bloat, aligning with typical server sizes of 3-15 tools.

    Completeness4/5

    The toolset provides strong coverage for Jira's core domain, including CRUD operations for issues and basic project management. A minor gap exists in missing tools for deleting issues or managing comments beyond addition, but agents can work around this with available tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources