Skip to main content
Glama
Milo0821

Zephyr Scale MCP Server

by Milo0821
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Zephyr Scale MCP Server

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
      41 npm
      MIT

    • jira-mcp

      nayzo
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Jira Cloud tailored for ALM projects with Zephyr Scale integration, enabling issue management, sprint tracking, and test step operations.
      408 npm
      1
      MIT

    • zephyr-squad-server-mcp

      alejandroviera
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that enables AI agents to drive Zephyr for Jira (Server/Data Center) test management via ZAPI. It exposes operations for test cycles, folders, executions, test steps, step results, and ZQL search over stdio for use with any MCP client.
      40
      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

    B3.4/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (folders, test cases, test runs, executions). There is no overlap or ambiguity; even similar tools like create_test_case and update_test_case_bdd are clearly differentiated by operation and scope.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., create_test_case, get_test_run, update_test_run). Names are descriptive and predictable, making it easy for an agent to infer functionality.

    Tool Count4/5

    16 tools is slightly above the typical well-scoped range but still reasonable for a test management server covering folders, test cases, runs, and executions. Each tool appears justified, with no redundant ones.

    Completeness3/5

    The surface covers most CRUD operations for test cases and runs, but has notable gaps: update_test_case only supports BDD content (no general update), and some operations are restricted to Cloud or Data Center. Missing delete for test executions is minor.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources