Skip to main content
Glama
alejandroviera

zephyr-squad-server-mcp

by alejandroviera
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to zephyr-squad-server-mcp

No user-submitted related servers found.

    Related Servers

    • zephyr-scale-mcp

      vilaabo
      A
      license
      A
      quality
      A
      maintenance
      MCP server for managing test cases, cycles, and results in Zephyr Scale on self-hosted Jira. Enables AI agents to create, search, update, and delete test artifacts through natural language.
      41
      43 npm
      MIT

    • QTM4J MCP Server

      salehrifai42
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that exposes the QMetry Test Management for Jira Cloud REST API as tools for MCP-compatible clients. It enables users to manage test cases, test cycles, test executions, test plans, folders, and automation rules through natural language interactions.
      30
      32 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

    • Zephyr Scale MCP Server

      Milo0821
      A
      license
      B
      quality
      B
      maintenance
      An MCP server for Zephyr Scale test management supporting Jira Cloud and Data Center. It enables creating, reading, and managing test cases and test runs via the Atlassian REST API with official API-compliant schemas.
      16
      511 npm
      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

    A3.7/5.0

    Scored across 40 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose. Even similar tools like add_tests_to_cycle_from_cycle and copy_executions_to_cycle have explicit descriptions differentiating their behavior (UNEXECUTED vs. preserving status). Agents should reliably select the correct tool.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case. Verbs like list_, create_, update_, delete_, add_, copy_, move_ are appropriately chosen. Even longer names like get_execution_status_counts_by_assignee maintain consistency.

    Tool Count3/5

    40 tools is heavy for a single server, with many specialized operations (e.g., multiple ways to add tests). While the domain justifies many tools, the count is borderline excessive and may overwhelm agents. A more curated set (20-25) would improve focus.

    Completeness4/5

    The tool set covers CRUD for cycles, folders, executions, test steps, plus search, status reports, defect linking, and async job polling. Minor gaps exist: no tool to unlink defects from executions, and test steps cannot be reordered. Overall, core workflows are well supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources