XQual ships a native MCP Server - built into the same server as the rest of XQual, no separate install or process - so any MCP-compatible AI assistant can query and drive your requirements, tests, campaigns, bugs and more, directly in natural language.
Point Claude, or any other MCP client, at your own XQual server and start asking.
Point Claude, or any other MCP client, at your own XQual server and start asking.
- Close to 100 tools mirroring XQual's own REST API, covering requirements, specifications, tests, testcases, campaigns, sessions, bugs, SUTs, users and teams,
- Standard MCP "Streamable HTTP" transport - works with Claude Desktop, Claude.ai's remote connectors, Claude Code and any other MCP-compatible client, no local install needed,
- Authenticate with a personal API token - every call runs as that specific XQual user, with that user's own access rights,
- Read trees, details, change history, linked items and results, or create and link new requirements, tests, testcases, campaigns, bugs, SUTs and users,
- Included free with every XQual license, Cloud or On-Premise.
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external tools and data. XQual's MCP Server is mounted directly inside your own XQual server, at
/mcp - your data never leaves your own XQual instance except through the AI assistant you chose to connect.
Your Test Data, One Conversation Away
Why, how, and who it's forWhy an MCP Server
Ask, don't query- Explore requirements, tests, campaigns, bugs, SUTs, sessions, users and teams in plain language - no query syntax to remember
- Let your AI assistant draft requirements, generate tests, log bugs or build campaigns directly into XQual, with the links already in place
- Cross-reference results, change history and linked items across entities in a single conversation instead of clicking through multiple screens
- A natural companion to XQual's own AI Features and REST API, for teams who live inside their AI assistant all day
How It Works
Standard MCP, backed by the REST API- Runs as a servlet inside your own XQual server, mounted at
/mcp- nothing extra to install or host - Standard MCP "Streamable HTTP" transport - the same protocol Claude Desktop, Claude.ai's remote connectors and Claude Code all speak natively
- Authenticate with a Bearer API token - every call runs under your own XQual account and respects your existing access rights
- Read tools return trees, details, change history, linked items and test/step/testcase results; create and link tools add and connect new requirements, specifications, tests, testcases, campaigns, bugs, SUTs and users
- Also exposes read-only support resources - a tail of the server log and your redacted configuration - so your assistant can help you troubleshoot your own instance
Who is this for
From daily standups to release audits- QA and product teams who want quick answers about coverage, status or history without opening XQual
- Developers using Claude Code or another MCP-aware editor who want live requirement and test context without leaving their tool
- Admins and support teams who want an AI assistant able to check server logs and configuration alongside the data
- Both Cloud SaaS and On-Premise XQual customers
TIP - Connect Claude to your XQual MCP Server
Generate a personal API token from your XQual user profile, then in Claude:
- Go to Settings > Connectors > Add custom connector
- Enter:
- Name:
XQual - URL:
https://<your-xqual-server>/xqual/mcp
- Name:
- On the authentication screen:
- Authentication:
None - Under Request headers, click + Add header and set:
Authorization = Bearer <your-api-token>
- Authentication:
Included free with every XQual license.