jira-xray-cloud-mcp
Related Servers
Alternatives to jira-xray-cloud-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables integration with Xray Cloud APIs for comprehensive test management including creating and managing test cases, test executions, test plans, and test sets. Supports CI/CD automation and test result tracking through GraphQL APIs.2320 npm3ISC
- AlicenseAqualityDmaintenanceEnables interaction with Xray Cloud and Data Center for test management, including authentication, GraphQL queries, test execution/plan management, and result import via MCP.98 npmMIT
- FlicenseBqualityFmaintenanceEnables AI assistants to interact with Xray Test Management for both Cloud and Server deployments. Supports test execution, importing results from multiple formats (JUnit, Cucumber, Robot Framework, TestNG), and managing test plans and executions.83-
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible clients to directly manage Jira Requirements and Test Management resources such as requirements, test cases, plans, executions, defects, tree structures, and automation via exposed tools.12 npmMIT
- AlicenseBqualityDmaintenanceEnables comprehensive test management in Zephyr Scale Cloud, including creating and managing test cases, executing tests with step-by-step results, organizing test cycles and plans, and performing advanced JQL searches.1816 npmMIT
- AlicenseNot gradedqualityCmaintenanceA lightweight server that bridges the MCP protocol with the Atlassian Jira Xray API, enabling safe and configurable access to Xray Server+DC via OpenAPI spec with multiple transports.11MIT
TDQS
Scored across 82 tools
Descriptions are generally precise, but the large surface creates several close pairs and groups: get_test/get_tests/get_expanded_test, get_test_run/get_test_runs, and the multiple test-run update variants. These boundaries are mostly explained, yet an agent can still misselect among similar read/update operations.
Tool names follow a highly consistent xray_verb_noun pattern across the entire set, including create_, get_, add_, remove_, update_, import_, and export_ actions. The convention is predictable and readable throughout.
At 82 tools, the set is far beyond a practical MCP surface and hits the extreme-mismatch threshold. Even for a broad domain like Xray test management, this volume makes discovery, selection, and maintenance unnecessarily difficult.
The surface covers the full Xray lifecycle: tests, preconditions, test sets, plans, executions, runs, folders, coverage, imports/exports, attachments, history, settings, and GraphQL escape hatches. There are no obvious dead ends for the stated domain.