Official Model Context Protocol (MCP) server for Qase Test Management Platform — connect AI assistants to your test cases, runs, defects, and more.
- Overview
- Use Cases
- Quick Start
- Building on top of this server
- Upgrading from v1
- Tools
- Documentation
- Contributing
- License
- Support
- Links
The Qase MCP Server lets AI assistants (Claude, Cursor, Codex, and any other MCP client) read and write Qase test cases, runs, results, defects, suites, milestones, and more — through a standardized protocol, with no custom integration code.
Features:
- 36 task-oriented tools (37 total, including
qase_discover_tools) — consolidated from 83 v1 tools for lower token usage and better LLM accuracy - Composite tools — multi-step workflows in a single call: CI reporting, defect triage, regression run setup
- QQL support — Qase Query Language for advanced searches across cases, runs, results, defects, and plans
- Project context bootstrap — one call returns full project structure (suites, milestones, environments, users, custom fields)
- Test case review — propose new cases or changes for review, assign reviewers, and track status (approving and merging remain UI-only)
- Tool discovery — secondary tools stay hidden until needed, keeping the default tool list small
- Hosted or self-run — connect to
https://mcp.qase.io/mcpwith just your Qase login, or run the server locally with your own API token - Tenant-safe caching & HTTP resilience — two-tier cache (in-memory + optional Redis), connection pooling, retry with backoff
- Escape hatch — direct REST API access for any endpoint via
qase_api