@qase/mcp-server

What it does

Qase MCP Server bridges Claude and other AI assistants to the Qase Test Management Platform, providing full API access to create, update, and query test cases, test suites, test runs, defects, test plans, milestones, and other test artifacts. The server supports Qase Query Language (QQL) for advanced cross-project searches and includes built-in support for enterprise custom domains, ensuring compatibility with both SaaS and self-hosted deployments.

Who it's for

QA engineers, test managers, and automation architects integrating test management into AI-driven workflows—automating test case creation, recording test results, searching for defects, and extracting test metadata without context-switching away from Claude.

Common use cases

• Create and organize test cases, test suites, and test plans directly from Claude
• Record test results and track defects after test execution
• Search across projects and retrieve test artifacts using Qase Query Language (QQL)
• Query test run status, milestones, and progress
• Attach files and manage custom fields on test cases and results

Setup pitfalls

• QASE_API_TOKEN environment variable is mandatory; obtain from app.qase.io/user/api/token
• Requires Node.js 18.0 or later; verify your runtime before installation
• Enterprise deployments must configure QASE_API_DOMAIN to point to custom Qase instances; omitting this defaults to the public API
• The repository lacks active CI/CD workflows; test integration locally before production use