zephyr-scale-mcp
Related Servers
Alternatives to zephyr-scale-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Zephyr Scale test management enabling test case, test run, folder, and assignment operations via natural language.2MIT
- AlicenseNot gradedqualityFmaintenanceMCP server for Zephyr Scale test management tool, enabling test case, test plan, test cycle, and test execution management.25 npm2MIT
- AlicenseAqualityBmaintenanceAn 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.40MIT
- AlicenseBqualityBmaintenanceAn 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.16511 npm6MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Zephyr Scale Cloud for test management, including test cases, cycles, plans, folders, priorities, and statuses via the MCP protocol.2MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Jira Cloud tailored for ALM projects with Zephyr Scale integration, enabling issue management, sprint tracking, and test step operations.408 npm1MIT
TDQS
Scored across 22 tools
Each tool targets a distinct resource and action (e.g., add_test_steps vs set_test_script, clone_test_case vs create_test_case, etc.), with no overlapping purposes. Agents can clearly differentiate between tools.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_test_case, update_test_plan, download_attachment). No mixing of conventions or vague verbs.
22 tools is well-scoped for a test management server, covering core entities (test cases, plans, runs, folders, attachments) and common operations without bloat.
Missing several expected operations: delete_test_case, delete_test_run, delete_attachment, list_folders, search_test_cases, and get_test_run_results. These gaps will likely cause agent failures in standard workflows.