Skip to main content
Glama
Satttoshi

jira-mcp

by Satttoshi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to jira-mcp

No user-submitted related servers found.

    Related Servers

    • JIRA MCP Server

      klapro
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Jira issues via JQL search, epic management, comments, attachments, and issue CRUD, with support for both Cloud and Server/Data Center instances.
      9
      5 npm
      MIT

    • jira-mcp-server

      mftnakrsu
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables read-only interaction with JIRA instances via MCP, allowing searching issues, worklogs, sprints, users, and projects through natural language.
      MIT

    • 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-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
    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.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: whoami validates identity, get_issue loads full details, get_comments retrieves only the discussion, get_issue_context maps relationships, search_issues runs JQL queries, and get_attachment downloads image content. No two tools overlap in function.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (get_issue, get_comments, search_issues, etc.). The only exception is 'whoami', which is a standard, recognizable command name and does not break the overall pattern.

    Tool Count5/5

    Six tools cover the essential read-only workflows for a Jira server: authentication, issue retrieval, comment access, relationship mapping, search, and attachment download. The count is well-scoped for the server's purpose without being excessive or sparse.

    Completeness4/5

    The surface covers common read-only Jira tasks comprehensively, including authentication, issue detail, comments, links, search, and images. Minor gaps exist—such as lacking project listing or issue creation/update—but these appear intentionally omitted for a read-centric server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources