Xray MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XRAY_CLIENT_ID | Yes | Your Xray Cloud API Client ID | |
| XRAY_CLIENT_SECRET | Yes | Your Xray Cloud API Client Secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_test_caseC | Create a new test case in Xray Cloud |
| get_test_caseC | Get details of a specific test case by key |
| update_test_caseC | Update an existing test case |
| delete_test_caseC | Delete a test case |
| search_test_casesC | Search for test cases using JQL (Jira Query Language) |
| get_project_test_casesC | Get all test cases for a specific project |
| create_test_executionC | Create a new test execution in Xray Cloud to run tests |
| get_test_executionB | Get details of a specific test execution by key, including all test runs |
| search_test_executionsC | Search for test executions using JQL (Jira Query Language) |
| get_project_test_executionsC | Get all test executions for a specific project |
| update_test_run_statusC | Update the status of a specific test run (e.g., mark as PASS or FAIL) |
| create_test_planC | Create a new test plan in Xray Cloud to organize tests |
| get_test_planC | Get details of a specific test plan by key, including all tests |
| search_test_plansC | Search for test plans using JQL (Jira Query Language) |
| get_project_test_plansB | Get all test plans for a specific project |
| add_tests_to_test_planC | Add tests to an existing test plan |
| remove_tests_from_test_planC | Remove tests from an existing test plan |
| create_test_setB | Create a new test set in Xray Cloud to group related tests |
| get_test_setC | Get details of a specific test set by key, including all tests |
| search_test_setsC | Search for test sets using JQL (Jira Query Language) |
| get_project_test_setsC | Get all test sets for a specific project |
| add_tests_to_test_setC | Add tests to an existing test set |
| remove_tests_from_test_setC | Remove tests from an existing test set |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 23 tools
Every tool has a clearly distinct purpose targeting specific Xray entities (test cases, test plans, test sets, test executions) and actions (create, get, update, delete, add/remove tests, search). No ambiguity exists between tools, as each name precisely indicates its function and target resource.
All tools follow a consistent verb_noun pattern with clear, descriptive names. The naming convention is uniform throughout, using snake_case and consistent verb choices (e.g., create_, get_, update_, delete_, search_, add_, remove_) paired with specific entity names.
With 23 tools, the count is borderline high for a test management server, potentially feeling heavy. However, given the comprehensive coverage of CRUD operations, searches, and management actions across multiple entity types, it is somewhat justified but could be streamlined.
The tool set provides complete CRUD/lifecycle coverage for all core Xray entities (test cases, test plans, test sets, test executions), including search capabilities and specific operations like adding/removing tests and updating test run status. No obvious gaps exist for the domain.