mcp-xray
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_PAT | No | Personal access token for Jira authentication (datacenter) | |
| JIRA_EMAIL | No | Email for Jira authentication (cloud) | |
| JIRA_BASE_URL | No | Base URL for Jira instance | |
| JIRA_PASSWORD | No | Password for Jira authentication (datacenter, alternative to PAT) | |
| JIRA_USERNAME | No | Username for Jira authentication (datacenter, alternative to PAT) | |
| XRAY_BASE_URL | No | Base URL for Xray API (default: https://xray.cloud.getxray.app for cloud, same as JIRA_BASE_URL for datacenter) | |
| JIRA_API_TOKEN | No | API token for Jira authentication (cloud) | |
| XRAY_CLIENT_ID | No | Client ID for Xray Cloud authentication | |
| XRAY_DEPLOYMENT | No | Deployment type: 'cloud' or 'datacenter' | |
| XRAY_CLIENT_SECRET | No | Client secret for Xray Cloud authentication | |
| XRAY_TOKEN_TTL_SECONDS | No | Token TTL in seconds (default: 3000) |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| xray_check_connectionA | Validates authentication against the configured Xray deployment (cloud or datacenter) and Jira instance. Call this first to verify credentials are working before using other tools. |
| xray_graphqlA | Executes a GraphQL query against Xray Cloud. Only available for cloud deployments. Use this for advanced Xray-specific queries like fetching test runs, test steps, preconditions, or test sets. |
| xray_import_execution_resultsA | Imports automated test execution results into Xray. Supports formats: junit, nunit, xunit, robot, testng, cucumber, behave, json. Provide the full report content as a string. Optionally target a specific project or existing Test Execution issue. |
| xray_get_test_executionA | Fetches a single Test Execution issue from Jira by its issue key (e.g. 'OQA10-42', 'GAP-100'). Returns the full Jira issue details. Use the 'fields' parameter to limit which fields are returned. |
| xray_search_test_executionsA | Searches for Test Execution issues in Jira using filters. The issuetype filter is applied automatically. Use 'projectKey' to filter by project (e.g. 'OQA10'), 'jql' for additional JQL conditions (e.g. 'status = "Done"'), and 'orderBy' for sorting (e.g. 'created DESC'). Example: to find recent test executions in project OQA10, use projectKey='OQA10' and orderBy='created DESC'. |
| xray_create_test_executionA | Creates a new Test Execution issue in Jira/Xray. Requires a project key and summary. Optionally provide a description and additional Jira fields (e.g. labels, components). |
| xray_get_test_planA | Fetches a single Test Plan issue from Jira by its issue key (e.g. 'GAP-12471'). Returns the full Jira issue details. Use the 'fields' parameter to limit which fields are returned. |
| xray_search_test_plansA | Searches for Test Plan issues in Jira using filters. The issuetype filter is applied automatically. Use 'projectKey' to filter by project (e.g. 'GAP'), 'jql' for additional JQL conditions, and 'orderBy' for sorting (e.g. 'created DESC'). Example: to find test plans in project GAP, use projectKey='GAP'. |
| xray_create_test_planA | Creates a new Test Plan issue in Jira/Xray. Requires a project key and summary. Optionally provide a description and additional Jira fields (e.g. labels, components). |
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 9 tools
Each tool targets a distinct resource and action: connection check, GraphQL query, import results, and CRUD operations for test executions and test plans. There is no overlap or ambiguity between tools.
Most tools follow the consistent xray_verb_noun pattern (e.g., get_test_plan, search_test_executions, create_test_execution). The exception is xray_graphql, which breaks the verb_noun convention but is still identifiable.
With 9 tools covering connection, querying, importing results, and managing test executions/plans, the server is well-scoped. Each tool serves a clear purpose without over-fragmentation.
The server covers create, get, and search for both test executions and test plans, plus import and GraphQL queries. However, it lacks update and delete operations for these entities, which are common lifecycle operations and would require workarounds.