Skip to main content
Glama
kornbed

Jira MCP Server for Cursor

by kornbed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Jira MCP Server for Cursor

No user-submitted related servers found.

    Related Servers

    • Jira MCP Server

      KS-GEN-AI
      A
      license
      B
      quality
      F
      maintenance
      A TypeScript-based server that enables interaction with Jira, providing tools to execute JQL queries, manage tickets, list projects and statuses through natural language.
      11
      26
      MIT

    • jira-mcp

      vaspap1790
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides tools for interacting with Jira. Enables Cursor and other MCP clients to fetch tickets, manage linked tickets, and update ticket status.
      3
      -

    • MCP Jira

      TusharShahi
      F
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol server that allows AI assistants to interact with Jira, supporting operations like creating tickets and fetching project information directly from the cursor.
      1
      -

    • mcp-server

      ElJijuna
      A
      license
      Not graded
      quality
      C
      maintenance
      A thin TypeScript MCP server that exposes engineering tools (Bitbucket, Jira, Confluence, ArgoCD) to MCP-compatible editors via a single API key per developer, delegating all service interactions to an internal backend.
      261 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

    B3.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific Jira operations: list_tickets vs. search_tickets differentiate between personal assignment and project-wide text search, while get_ticket vs. get_comments separate ticket details from comment retrieval. No tools appear to overlap in functionality, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case (e.g., add_comment, create_ticket, get_comments). The verbs are appropriately chosen for each action (add, create, get, list, search, update), creating a predictable and readable naming convention throughout the set.

    Tool Count5/5

    With 7 tools, this server is well-scoped for Jira ticket management. Each tool earns its place by covering essential operations like creating, retrieving, listing, searching, updating status, and managing comments, without being overly sparse or bloated for the domain.

    Completeness4/5

    The tool set provides strong coverage for core Jira ticket workflows, including CRUD-like operations (create, get, list, update_status) and comment management. A minor gap exists in the lack of a tool to update ticket details beyond status (e.g., edit description or fields), but agents can work around this by creating new tickets or using comments.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources