Tiden is live on Product Hunt today. See the launch.

MCP

The MCP Server for AI Test Management

No context switching. Qase MCP Server meets you where you already work.

Start trialTalk to sales

No credit card required

npm install -g @qase/mcp-server
ISO/IEC 27001·SOC 2·GDPR·Enterprise SLA

Works with your tools

Claude Desktop
Cursor
Claude Code
OpenAI Codex
OpenCode

AI writes tests. Nobody manages them. Until now.

MCP closes the loop between AI-generated tests and the team responsible for shipping quality.

No traceability or coverage

AI agents generate tests in a black box, with no link back to suites, runs, or coverage reporting, and no way for the team to coordinate on what's been tested.

No governance or compliance

Enterprises need audit trails, role-based access, and approval workflows. Most AI test workflows have none of those.

No human oversight

AI-generated tests still need human review. Without organizational visibility, bad tests slip through and good ones get duplicated.

The solution

Qase MCP Server brings AI-driven testing into the same governance, traceability, and review surface your team already uses.

Full traceability, built in

Tests created via MCP are stored in Qase with their suites, runs, and results, and exposed through 41 MCP tools so coverage stays connected to your work.

Enterprise governance by default

Role-based access, audit trails, milestones, and approval workflows apply to MCP-driven changes the same way they do everywhere else in Qase.

Human review at every step

Every test, run, and defect created from an MCP client is visible in the Qase UI with full filtering and auditing — no shadow test suites.

Everything you need, nothing you don't

A focused MCP surface that exposes the parts of Qase your AI assistant actually needs.

Test cases & runs

Create, update, and execute test cases and runs from your AI assistant. 41 tools, all available.

Query your TMS

Use Qase Query Language to filter test cases, defects, and results by any field, directly from your MCP client.

Defect tracking

Create, resolve, and manage defects without leaving your coding environment.

Full API coverage

Projects, suites, plans, milestones, environments, shared steps, custom fields. The whole surface, MCP-ready.

Bulk operations

Create multiple test cases or results in a single call so AI workflows stay fast at scale.

Enterprise ready

Custom domain support, type-safe TypeScript implementation, and full validation out of the box.

Three minutes to connect

From token to your first AI-driven Qase query in minutes.

01

Get your API token

Generate a token in app.qase.io → Settings → API tokens.

02

Add the MCP server to your client

Drop the Qase MCP config into Claude Desktop, Cursor, Claude Code, OpenAI Codex, or OpenCode.

03

Query Qase from your assistant

Try "List all my Qase projects" and your MCP client routes it through Qase and responds inline.

Pre-made skills

Want to extend your capabilities even further? Quality Supervisor, an installable plugin for MCP-capable AI clients, adds software quality related skills to your agentic workflow.

Coverage gaps

“Where are our coverage gaps?” Finds requirements, suites and critical paths with no tests, then drafts the missing cases for you to approve.

Failure triage

“Triage the latest run and tell me what’s a real bug.” Groups failures and sorts each one into product bug, automation issue, environment problem or flake. Creates and links defects when you say so.

Flaky tests

“Which tests should we quarantine?” Measures instability from result history, confirms with re-runs, and recommends quarantine or a fix for each test.

Release readiness

“Are we ready to ship milestone 2.3?” A go/no-go check across 5 dimensions for a milestone, test plan or release.

Quality pulse

“Give me a quality pulse for the last two weeks.” An HTML report card covering execution, pass rates, defect backlog and test case activity.

Change impact

“What should QA test on this branch?” Reads the diff, traces the affected code paths, and returns a regression checklist plus the new tests the change needs.

Want all of it at once? Run with your project code for coverage, flakiness, triage and readiness in one read-only pass.

Ship quality software faster with Qase

FAQs

The MCP server works with Claude Desktop, Claude Code, Cursor, OpenAI Codex, OpenCode and other MCP-capable clients. Quality Supervisor runs in Claude Code, Claude Desktop, Cowork, Cursor, VS Code and Atlassian Rovo.
The MCP server is on every plan. You run it locally with an API token. Enterprise adds a hosted MCP server you connect to over OAuth, so there's no token to store or rotate. Queries that use QQL need Teams or Enterprise.
No. The MCP server works on its own, and your assistant can read and write Qase data as soon as it's connected. Quality Supervisor is an optional, free plugin that adds ready-made analysis like failure triage and release readiness.
Every change made through MCP runs under your Qase permissions and shows up in the Qase UI (and in audit logs on Enterprise), same as a change made by hand. Quality Supervisor goes further: it has no delete operations, and anything it writes waits for your confirmation.
Ask your assistant which query it ran. Quality Supervisor includes the QQL query behind every finding, so you can run it in Qase and check the same data yourself.
Your test data stays in Qase, which remains the system of record. When you ask a question, the results your assistant pulls are sent to the AI model your client uses, under that provider's terms. Qase is ISO/IEC 27001 and SOC 2 certified and GDPR compliant.

Trust center →
Both are. The Qase MCP server is MIT-licensed on npm as @qase/mcp-server, and Quality Supervisor is MIT-licensed.