Skip to main content
Glama
sina-haseli

mcp-server-jira

by sina-haseli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-server-jira

No user-submitted related servers found.

    Related Servers

    • 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

      BillNobill
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to manage Jira projects and issues using natural language, including creating, updating, searching issues, managing sprints, and more via the Jira API.
      36
      60 npm
      1
      MIT

    • Jira MCP Server

      Eliya-56
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage Jira issues with full CRUD, transitions, linking, commenting, and file attachments via the Jira REST API v3.
      10
      60 npm
      Apache 2.0

    • 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 Cloud MCP Server

      yaakovmargalit
      A
      license
      A
      quality
      B
      maintenance
      Enables LLMs to interact with Jira Cloud through the official REST API v3, supporting operations like creating issues, searching with JQL, fetching issue details, and managing transitions.
      9
      60 npm
      Apache 2.0
    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

    A4.1/5.0

    Scored across 16 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action: story CRUD, comments, transitions, project metadata, and Agile board/sprint operations are clearly separable. Even with shared verbs like 'get' or 'create', the noun targets prevent confusion.

    Naming Consistency5/5

    Tool names consistently follow verb_noun conventions with get/create/update/delete/list/transition/add prefixes. Minor pluralization in search_stories and the info suffix in get_project_info do not break the overall pattern.

    Tool Count4/5

    16 tools is slightly above the ideal 3-15 range but appropriate for a Jira server covering both story lifecycle management and Agile board/sprint operations. Each tool appears purposeful with minimal redundancy.

    Completeness4/5

    The story lifecycle is well covered: get, create, update, delete, search, transition, and comment. Some minor gaps exist around generic issue operations and board/sprint deletion, but the set covers the core PRD-to-Jira and Agile tracking workflows well.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources