Skip to main content
Glama
apo100l

MCP Jira Server

by apo100l
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MCP Jira Server

No user-submitted related servers found.

    Related Servers

    • jira-mcp-server

      TTranchese
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with self-hosted Jira instances via Personal Access Token, supporting issue management and project operations through natural language.
      43 npm
      Apache 2.0

    • 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 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 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,598 npm
      8
      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 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: issues, projects, comments, users, and issue types are clearly separated. There is no overlap between search/get/create/update/delete operations, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow the consistent pattern jira_<verb>_<noun> using snake_case. The verbs are standard and predictable, such as get, create, update, delete, search, add, and assign, with no mixed conventions.

    Tool Count5/5

    12 tools is a well-scoped count for a Jira integration, covering core issue, project, and comment workflows without unnecessary bloat. Each tool serves a clear purpose within the domain.

    Completeness4/5

    The surface covers issue CRUD, searching, comments, project lookup, assignment, and user info, which handles common workflows well. A notable gap is the absence of issue transition/status-change functionality, which is core to Jira usage, though agents can work around it with update_issue in some cases.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources