Xray MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XRAY_TOKEN | No | Your Personal Access Token for Xray Server/Data Center | |
| XRAY_PASSWORD | No | Your password for Basic Authentication with Xray Server/Data Center | |
| XRAY_USERNAME | No | Your username for Basic Authentication with Xray Server/Data Center | |
| XRAY_AUTH_TYPE | No | Authentication type for Xray Server/Data Center: 'token' for Personal Access Token or 'basic' for Basic Authentication | |
| XRAY_DEPLOYMENT | No | Xray deployment type: 'cloud' for Xray Cloud or 'server' for Xray Server/Data Center | |
| XRAY_JIRA_BASE_URL | No | The base URL of your Jira instance (e.g., https://your-jira-instance.com) | |
| XRAY_CLOUD_CLIENT_ID | No | Your Xray Cloud client ID (get from https://xray.cloud.getxray.app/api-keys) | |
| XRAY_CLOUD_CLIENT_SECRET | No | Your Xray Cloud client secret (get from https://xray.cloud.getxray.app/api-keys) |
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 |
|---|---|
| import_test_resultsC | Import automated test execution results from various formats (JUnit, Cucumber, Xray JSON, Robot Framework, TestNG) |
| execute_testsC | Create and execute a test run in Xray for specified test cases |
| query_test_executionsC | Query and filter test executions in Xray |
| get_test_infoC | Retrieve detailed information about a specific test case |
| create_test_executionC | Create a new test execution container in Xray |
| update_test_executionC | Update status and details of a test within an execution |
| get_test_plansC | List test plans in a project |
| associate_tests_to_executionC | Add test cases to an existing test execution |
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 8 tools
Most tools have distinct purposes focused on different aspects of test management (creation, querying, execution, import), but there is some potential overlap between 'create_test_execution' and 'execute_tests' where the latter might be confused as a superset of the former. The descriptions help clarify that 'execute_tests' specifically creates and runs tests, while 'create_test_execution' is just a container, but the naming could cause mild confusion.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., 'associate_tests_to_execution', 'create_test_execution', 'get_test_info'). There are no deviations in naming conventions, making the set predictable and easy to parse for an agent.
With 8 tools, the server is well-scoped for test management in Xray, covering key operations like creation, querying, execution, and import without being overly complex or sparse. Each tool appears to serve a specific function that contributes to the domain's workflow.
The tool set provides strong coverage for test execution and management, including CRUD-like operations (create, query, update) and import capabilities. A minor gap is the lack of tools for deleting or archiving test executions or plans, which might limit full lifecycle management, but agents can likely work around this with existing tools.