Skip to main content
Glama
vaspap1790

jira-mcp

by vaspap1790
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to jira-mcp

No user-submitted related servers found.

    Related Servers

    • @abdelrahmanhsn/jira-mcp

      abdelrahman-hsn
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that connects your AI IDE to Jira. Query your tickets, active sprint, and issue details directly from GitHub Copilot, Cursor, Claude Desktop, or any MCP-compatible client.
      16 npm
      ISC

    • 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
      -

    • 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

    • Jira MCP Server

      sthirugn
      A
      license
      Not graded
      quality
      D
      maintenance
      A clean and focused Model Context Protocol (MCP) server that provides seamless integration between AI assistants and Jira, enabling natural language interaction with your Jira projects, issues, and workflows.
      5
      MIT

    • JIRA MCP Server

      Dsazz
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that integrates JIRA directly into Cursor IDE, allowing users to view assigned issues, get detailed information on specific tickets, and convert JIRA issues into local tasks without leaving their editor.
      14
      12 npm
      6
      TypeScript
      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.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct operation: retrieving a ticket, fetching linked tickets, and updating status. No overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent 'verb_noun' pattern in snake_case (get_ticket, get_linked_tickets, update_ticket_status), making them predictable.

    Tool Count4/5

    Three tools is on the lower end of the ideal range but still reasonable for a focused Jira server. Each tool serves a clear purpose without feeling sparse.

    Completeness2/5

    Missing essential CRUD operations such as create_ticket, search_tickets, or add_comment. Agents cannot create new tickets or perform most lifecycle actions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources