Skip to main content
Glama
ranson21

jira-readonly-mcp

by ranson21
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to jira-readonly-mcp

No user-submitted related servers found.

    Related Servers

    • jira-mini-mcp

      proprock
      A
      license
      A
      quality
      A
      maintenance
      Enables coding agents to read Jira Cloud issues, search via JQL, and retrieve comments, attachments, and change history through a lightweight, context-efficient MCP toolset.
      9
      MIT

    • JIRA MCP Server

      hackdonalds
      A
      license
      B
      quality
      D
      maintenance
      Provides tools for AI assistants to interact with JIRA APIs, enabling them to read, create, update, and manage JIRA issues through standardized MCP tools.
      6
      19 npm
      3
      MIT

    • jira-mcp-server

      chrisurf
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that provides AI agents structured access to Jira Cloud, enabling project listing, sprint overview, issue retrieval, and JQL search.
      78 npm
      MIT

    • jira-mcp

      Pandacli
      A
      license
      Not graded
      quality
      C
      maintenance
      A lightweight MCP server for self-hosted Jira Server, exposing REST API v2 tools for search, issue creation/update, transitions, comments, and more to AI clients via MCP protocol.
      MIT

    • jira-mcp-bridge

      erollando
      A
      license
      Not graded
      quality
      D
      maintenance
      A local-only MCP server providing safe, typed Jira tools for AI agents via Atlassian ACLI, enabling search, get issue, add comment, and transition issues with policy guardrails.
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have clearly distinct targets (single issue, JQL search, comments, links, my issues, project metadata). However, get_issue already returns comments and linked issues, so it partially overlaps with get_comments and get_related_issues, and get_my_open_issues is essentially a preset of search_issues. Descriptions do help clarify the intended use cases.

    Naming Consistency4/5

    All names use snake_case with a verb_noun structure (get_issue, get_comments, get_related_issues, get_project_metadata, get_my_open_issues). The only deviation is search_issues, which is still readable and semantically appropriate for a query action rather than a fetch.

    Tool Count5/5

    Six tools is well-scoped for a focused read-only Jira integration. Each tool maps to a distinct read operation with no filler or redundancy beyond the mild overlap noted.

    Completeness4/5

    The read-only surface covers the core read paths: fetch, search, comments, links/subtasks, assigned work, and project metadata. Minor gaps exist for read-only needs like attachments, worklogs, or listing all accessible projects, but these are workable omissions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources