Xray MCP Server

MCP server for Xray test management plugin for Jira. Avoids the problem of slow Jira/ Xray combination. Can bring an entire test suite faster than manually adding. Can integrate AI testing as this is able to update test cases as well. Why MCP and not a skill? MCP communicates well with Atlassian MCP.

AnMCPserver forXray Cloud(test management for Jira). It lets an MCP client (Claude Code, Claude Desktop, etc.) import automation results and manage Xray test entities — Tests, Test Executions, and Test Sets — directly.

Create an XrayAPI Keyin Jira →Xray → Global Settings → API Keys(for a service user). This yields aclient_id+client_secret. The server resolves them at startup,never from a file on disk, in this order:
- Direct env varsXRAY_CLIENT_ID+XRAY_CLIENT_SECRET, if both are set — simplest for local use and CI.
- Azure Key Vault— read from the vault atXRAY_KEY_VAULT_URLviaDefaultAzureCredential(az loginlocally, managed identity in Azure). Useful when you don't want secrets in env.

npm install npm run build # -> dist/ npm run auth-check # resolves credentials + obtains a token (prints no secret)

{ "mcpServers": { "xray": { "command": "node", "args": ["/absolute/path/to/xray-cloud-mcp/dist/index.js"], "env": { "XRAY_CLIENT_ID": "your-client-id", "XRAY_CLIENT_SECRET": "your-client-secret" } } } }

Or, with Azure Key Vault instead of inline secrets:

"env": { "XRAY_KEY_VAULT_URL": "https://your-vault.vault.azure.net" }

- Description on create:some Jira projects make the Description field mandatory;create_testdefaults it to the summary so creation never fails for lack of one.
- Importing results:pointimport_execution_junitat the JUnit XML your test runner produces (Playwright, Jest, JUnit, etc.). Useimport_execution_xrayfor the richer native Xray JSON.
- stdio only:the server speaks MCP over stdio; diagnostics go to stderr (stdout is the protocol channel).

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Interact with Jira to manage issues, projects, and workflows using the Jira Cloud Platform REST API.

An MCP server for interacting with the Jira API to manage projects, issues, and workflows.

About AI-powered Jira CLI and MCP server for humans and agents manage issues, sprints, boards with interactive wizards, multi-provider AI

Connects to a Jira instance to generate weekly reports based on issue activity.

Integrates with JIRA's Zephyr test management system.

An MCP server for managing Tempo worklogs in Jira. It connects to Jira and Tempo services using API tokens and environment variables.

AI-native MCP server connecting Claude, Cursor, Windsurf, and other AI assistants to TestRail — manage test cases, runs, and results through natural-language conversation, with typed schemas built for LLMs.

Connect bugAgent to any MCP-compatible AI client. File, classify, and manage bugs, feature requests, and more directly from your AI coding assistant. No context switching, no copy-paste — just describe the issue and bugAgent handles the rest.

his repository contains a fully functional MCP (Model Context Protocol) server, providing solutions for Constraint Satisfaction Problems (CSP) and Linear Programming (LP). It is based on the gurddy package and supports solving a variety of classic problems.

Integration with QA Sphere test management system, enabling LLMs to discover, summarize, and interact with test cases directly from AI-powered IDEs