Skip to main content
Glama

Related Servers

Alternatives to MCP JIRA Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol server that enables AI applications to interact with Jira issues, projects, and workflows through a standardized interface.
      2
      Apache 2.0
    • A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants like Claude to interact with Jira Cloud instances, providing capabilities for issue management, project listing, and JQL search.
      1
      76 npm
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants like Claude to interact with Jira, allowing for project management tasks such as listing projects, searching issues, creating tickets, and managing sprints through natural language queries.
      7
      76 npm
      2
      TypeScript
      MIT

    TDQS

    C2.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    Three JIRA-related tools have clear distinct purposes: create, search, and update issues. However, the 'echo' tool is completely unrelated to the JIRA domain, which creates a minor but noticeable ambiguity in the toolset's overall purpose. The JIRA tools themselves are well-differentiated.

    Naming Consistency3/5

    The three JIRA tools follow a consistent verb_noun pattern with underscores (create_jira_issue, search_jira_issues, update_jira_issue). However, the 'echo' tool breaks this pattern by using a single word without the JIRA prefix, creating mixed conventions within the set. The naming is readable but not fully consistent.

    Tool Count3/5

    With only 4 tools, the count feels thin for a JIRA server, especially given that one tool ('echo') is unrelated to JIRA. For a domain as rich as JIRA issue management, having just three core tools (create, search, update) is borderline minimal, lacking expected operations like delete, get details, or comment management.

    Completeness2/5

    The toolset has significant gaps for JIRA issue management. While it covers create, search, and update, it lacks essential operations like deleting issues, retrieving specific issue details, adding comments, or managing attachments. The inclusion of an unrelated 'echo' tool further dilutes the domain coverage, making the surface incomplete for typical JIRA workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues