Skip to main content
Glama
RakshitRabugotra

Jirum

by RakshitRabugotra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Jirum

No user-submitted related servers found.

    Related Servers

    • atlassian-mcp

      amzu-dev
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude and Claude Code to interact with Atlassian Cloud (Confluence and Jira) through natural language, supporting full CRUD operations, search, comments, and attachments.
      MIT

    • jira-mcp-server

      fkesheh
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants like Claude to interact with Jira for project management tasks, including issue creation, updates, workflow transitions, and bulk operations.
      12 npm
      4
      MIT

    • Jira MCP Server

      SunWooBang
      A
      license
      C
      quality
      D
      maintenance
      Connects Jira with Claude, enabling users to search issues, view issue details, update issues, add comments, and retrieve project information through natural language commands.
      1
      226 npm
      1
      MIT

    • JIRA MCP Server

      rajsodhi-2
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude AI to interact with JIRA for project management and issue tracking, supporting JQL queries, comprehensive issue details retrieval with subtasks and linked issues, and release planning analysis.
      MIT

    • Jira MCP

      icy-r
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage Jira Cloud instances, including creating and updating issues, managing sprints and projects, adding comments, tracking worklogs, and searching with presets.
      18 npm
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.4/5.0

    Scored across 38 tools

    Disambiguation3/5

    The read/lookup tools are well separated, but the create surface has heavy overlap: jira_create_issue can do anything jira_create_epic, jira_create_child_issue, jira_create_subtask, and jira_create_ticket_from_context do, and jira_get_fields / jira_get_create_fields / jira_get_issue_types all answer 'what fields do I need?'. Descriptions do explain when to prefer each, which keeps this from being worse than moderate ambiguity.

    Naming Consistency4/5

    Nearly everything follows a jira_verb_noun snake_case pattern (jira_get_issue, jira_list_projects, jira_add_to_sprint), making the set easy to scan. A few stragglers drop the noun or use noun-only forms (jira_myself, jira_connect, jira_disconnect, jira_auth_status), but they are few and readable.

    Tool Count2/5

    38 tools is heavy even for Jira's breadth, and several are convenience composites that duplicate existing primitives (jira_create_epic_with_children, jira_create_ticket_from_context, jira_find_duplicate_ticket, jira_count_issues). The surface could be trimmed substantially without losing capability.

    Completeness4/5

    Core workflows are well covered: JQL search, issue CRUD, hierarchy creation, transitions, assignment, links, comments (create/read), boards, sprints, and sprint membership. Gaps remain around attachments, worklogs, watchers, changelog, and deleting/updating comments or links, which agents cannot work around for those tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources