Skip to main content
Glama
jl-0

JIRA MCP Server

by jl-0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to JIRA MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      43 npm
      Apache 2.0

    • jira-readonly-mcp

      ranson21
      A
      license
      A
      quality
      C
      maintenance
      Gives local coding agents safe, read-only access to an existing Jira instance through MCP over stdio, keeping Jira credentials out of the LLM. It exposes tools for reading issues, comments, linked items, JQL search results, assigned open issues, and project metadata.
      6
      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

      Satttoshi
      F
      license
      A
      quality
      B
      maintenance
      Provides read-only access to Jira, enabling users to retrieve issue details, comment threads, linked-issue context, epic children, and JQL search results as compact Markdown.
      6
      1
      -
    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.6/5.0

    Scored across 14 tools

    Disambiguation4/5

    Each tool targets a clear resource and action, but the three field-discovery tools (jira_get_issue_type_fields, jira_get_issue_field_names, jira_search_issue_fields) have overlapping purposes for discovering field IDs, which could cause confusion. However, their descriptions differentiate them sufficiently by scope (issue type vs issue vs search).

    Naming Consistency5/5

    All tools follow a consistent jira_<verb>_<noun> pattern with verbs limited to get, list, and search. Naming is uniform, predictable, and easy to navigate.

    Tool Count5/5

    At 14 tools, the count is appropriate for a JIRA server covering projects, issues, comments, transitions, users, and field metadata. Each tool has a clear role, though the set is somewhat read-heavy.

    Completeness2/5

    The server lacks any create, update, or transition operations, so agents cannot modify issues, add comments, or change statuses. It provides broad read capabilities but is severely incomplete for a JIRA MCP server that would normally support issue lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources