Skip to main content
Glama
proprock

jira-mini-mcp

by proprock
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to jira-mini-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • Simple Jira MCP

      timohaa
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides Jira Cloud integration for AI agents, enabling them to search issues with JQL, retrieve detailed issue information, and create new tickets. It supports multiple Jira configurations and provides tools for managing attachments and comments through natural language.
      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
      6 npm
      3
      MIT

    • jira-helper

      namssy
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Jira Cloud tickets, including listing, searching, creating, and updating issues through a set of MCP tools.
      -

    • JIRA MCP Server

      scarnyc
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with JIRA through MCP, providing 35 tools for issues, comments, transitions, projects, boards, sprints, epics, links, worklogs, versions, attachments, users, and fields.
      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.3/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: search vs single-issue fetch, comments vs attachments vs changelog, and update vs transition vs comment. Where overlap could occur, the descriptions explicitly disambiguate boundaries.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern like search_issues, get_comments, add_comment, and transition_issue. The get_attachments vs download_attachment distinction is clear from the verbs.

    Tool Count5/5

    Nine tools is a well-scoped set for a focused Jira issue server. Each tool earns its place, covering search, read, update, transition, comments, attachments, and changelog.

    Completeness3/5

    The server covers reading, searching, updating, transitioning, commenting, and attachment download well. However, create_issue is missing, along with attachment upload and comment edit/delete, which are notable gaps for a Jira issue-management surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources