What it does

The Qase MCP Server bridges AI assistants with the Qase Test Management Platform. It provides programmatic access to all Qase entities including test cases, test runs, defects, projects, test suites, milestones, and custom fields. The server is built in TypeScript with full API coverage and supports QQL (Qase Query Language) for advanced cross-project searches. It handles enterprise custom domains and integrates into Claude, Cursor, Claude Code, and other AI clients.

Who it's for

QA engineers automating test workflows, development teams seeking AI-assisted test case generation, and enterprises managing complex test portfolios in Qase. Teams already using Qase benefit most—they can now ask Claude to draft test cases from requirements, search defects by pattern, or organize test suites without switching tools.

Common use cases

• Generate test cases from requirements using Claude as a natural language interface
• Query test results across projects with QQL to identify failure patterns and trends
• Create defects from failed tests with full test run context
• Document and organize test cases by syncing with existing suite hierarchies
• Search and retrieve shared test parameters and steps for reuse

Setup pitfalls

• QASE_API_TOKEN is required—obtain it from https://app.qase.io/user/api/token and set it as an environment variable; without it, requests fail silently.
• Enterprise custom domains require QASE_API_DOMAIN (e.g., api.yourcompany.qase.io); the default assumes standard Qase SaaS.
• Node.js 18+ is required; earlier versions will fail at runtime.
• Configuration format differs by client (Claude Desktop JSON vs. Cursor vs. OpenCode)—verify your client's config location and structure before starting.