Xray MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your Jira account email | |
| JIRA_BASE_URL | Yes | Your Jira instance URL (e.g., https://your-domain.atlassian.net) | |
| JIRA_API_TOKEN | Yes | The API token from Atlassian | |
| XRAY_CLIENT_ID | No | Your Xray Cloud API client ID (optional, needed for test steps) | |
| XRAY_CLIENT_SECRET | No | Your Xray Cloud API client secret (optional, needed for test steps) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_testsB | List all tests in a Jira project using JQL query |
| get_testA | Get detailed information about a specific test by its key |
| get_test_with_stepsA | Get detailed test information with test steps using the reliable GraphQL getTests query. This tool always fetches test steps if they exist. |
| create_testC | Create a new test in Jira with Xray |
| update_testB | Update an existing test |
| list_test_executionsB | List test executions in a Jira project |
| get_test_executionB | Get detailed information about a test execution including test run results |
| create_test_executionC | Create a new test execution in Jira with Xray |
| update_test_runC | Update the result of a test run within a test execution |
| list_test_plansB | List all test plans in a Jira project |
| get_test_planA | Get detailed information about a test plan including associated tests |
| create_test_planB | Create a new test plan in Jira with Xray |
| add_tests_to_test_planB | Add tests to an existing test plan |
| list_test_setsB | List all test sets in a Jira project |
| get_test_setA | Get detailed information about a test set including associated tests |
| import_execution_resultsA | Import test execution results in Xray JSON format. Creates test executions and test runs with results. |
| import_cucumber_resultsA | Import Cucumber JSON test results to Xray. Automatically creates test execution and updates test statuses. |
| import_junit_resultsA | Import JUnit XML test results to Xray. Automatically creates test execution and updates test statuses. |
| import_testng_resultsB | Import TestNG XML test results to Xray. Automatically creates test execution and updates test statuses. |
| import_nunit_resultsA | Import NUnit XML test results to Xray. Automatically creates test execution and updates test statuses. |
| import_robot_resultsA | Import Robot Framework XML test results to Xray. Automatically creates test execution and updates test statuses. |
| import_behave_resultsA | Import Behave JSON test results to Xray. Automatically creates test execution and updates test statuses. |
| import_feature_fileA | Import Cucumber .feature file to Xray. Creates or updates BDD tests from Gherkin scenarios. |
| export_cucumber_featuresA | Export Cucumber feature files from Xray. Can export all features or specific test keys. |
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 24 tools
Each tool targets a distinct Xray entity or action (test, test plan, test execution, test set, import format), with clear naming and descriptions preventing confusion. The only potential overlap (get_test vs get_test_with_steps) is resolved by explicit distinction in descriptions.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_test, get_test_plan, import_cucumber_results). The pattern is predictable and matches standard CRUD operations plus imports/exports.
24 tools is slightly high but justified for a comprehensive test management server covering multiple entity types and import/export formats. Each tool serves a distinct purpose, and the count aligns with the domain's complexity.
The tool set covers essential CRUD for tests, test plans, test executions, and test sets, plus imports/exports for various formats. However, delete operations for test plans, executions, and test sets are missing, leaving a notable gap in lifecycle coverage.