Qase Test Management

Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.

Developer Tools
37stars
No ratings
UpdatedOct 21, 2026

InstallRepository Website

Install Qase Test Management

Pick your client, then add it in one click or paste the config.

STDIONode.js

~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "qase-test-management": {
      "command": "npx",
      "args": [
        "-y",
        "@qase/mcp-server"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 42 tools correctly (2d ago).

Overview

Tools42

What Qase Test Management lets your agent do. Expand a tool for its parameters.

Verified live~13.6k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

9/9 checks healthy over the last 49d

What it can do

From the 42 tools this server returned when we ran it; 42 declare their own safety hints.

Can delete or modify data · 14Writes files · 1Makes network requests · 38Read-only tools · 27

Network at startup3 connections

Files written at startupNone

Install scriptsprepare

npm provenanceSigned build

Package age360 days

Maintainers1

Observed 2026-10-25 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @qase/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars37Stargazers on the source repository.

npm downloads7.2kPackage downloads in the last 30 days.

Last commit6d agoMost recent push to the default branch.

Availability100%Our rolling endpoint + install checks that succeeded.

Install checkPassedOur sandbox started it and listed its tools.

Tools exposed42Callable tools this server registers over MCP.

From the project README

Qase MCP Server

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
- Use the hosted Qase MCP (recommended)
- Run it yourself
Building on top of this server
Upgrading from v1
Tools
Documentation
Contributing
License
Support
Links

Overview

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:

40 task-oriented tools (42 total, with qase_discover_tools and qase_tool_help) — 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)
Short descriptions, documentation on demand — every tool is listed from the first request; qase_tool_help returns a tool's full documentation when the agent first reaches for it, and qase_discover_tools searches the catalogue by task
Hosted or self-run — connect to https://mcp.qase.io/mcp (or https://mcp-eu.qase.io/mcp on the EU cluster) with 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

Use Cases

Scenario	Example prompt	Tool
Bootstrap project context	"Show me the structure of project DEMO — suites, milestones, environments"	`qase_project_context`
Create or update a test case	"Create a high-priority smoke test case in project DEMO titled 'Login with valid credentials'"	`qase_case_upsert`
Report CI results	"Report these CI results for project DEMO: case 1 passed, case 2 failed with 'timeout error'"	`qase_ci_report`
Triage a failed test	"Create a critical defect for the login timeout failure in run #42"	`qase_triage_defect`
Search with QQL	"Find all failed test results from the last 7 days in project DEMO"	`qql_search`

See Tools and docs/tools.md for the full reference.

Quick Start

Use the hosted Qase MCP (recommended)

No install, no API token — connect to the Qase-hosted server and sign in with your Qase account.

Note: The hosted Qase MCP is available on every paid plan. On the Free plan, or on a dedicated instance, run the server yourself with your own API token — that works everywhere.

Pick the URL for your region: https://mcp.qase.io/mcp for the main cloud (app.qase.io), https://mcp-eu.qase.io/mcp for the EU cluster (app-eu.qase.io). The examples below use the main cloud; on the EU cluster substitute the EU URL and change nothing else.

Claude — open Settings → Connectors, find Qase Test Management, click Connect. (The directory connector is main-cloud; on the EU cluster add https://mcp-eu.qase.io/mcp as a custom connector.)
Cursor — add {"mcpServers": {"qase": {"url": "https://mcp.qase.io/mcp"}}} to .cursor/mcp.json.
Codex — add the URL https://mcp.qase.io/mcp in Settings → MCPs → Add server, or configure ~/.codex/config.toml for the CLI.
VS Code — add {"servers": {"qase": {"type": "http", "url": "https://mcp.qase.io/mcp"}}} to .vscode/mcp.json, or run MCP: Add Server.

Full per-client steps, other clients, and the active-workspace model: docs/connect.md.

Run it yourself

Install the package and provide your own API token:

Terminal

npm install -g @qase/mcp-server
export QASE_API_TOKEN=your_api_token_here

Then point your MCP client's stdio config at the @qase/mcp-server binary. Full install options, client configs (Claude Desktop, Cursor, Claude Code, Codex, OpenCode), environment variables, and transports (stdio/SSE/streamable-HTTP): docs/self-run.md.

Building on top of this server

For integration authors only — if you use the server directly, nothing here applies to you.

If your product drives this server (a plugin, an agent, a wrapper CLI), it can identify itself so its usage is attributable in Qase analytics, independently of which AI host is connected:

bash

QASE_MCP_INTEGRATION=quality-supervisor/1.4.0   # <name>/<version>, version optional

The name must be on the allowlist in src/utils/integration-marker.ts — add yours in a PR. Anything unlisted or malformed is ignored, and the API call still succeeds. HTTP transports also accept the marker per request (X-Qase-Integration header or ?integration=). Details: docs/self-run.md.

Upgrading

From 2.x to 3.0.0: no tool was renamed and no argument changed, so prompts and automation keep working. What changed is the protocol underneath — the server speaks MCP 2026-07-28, sessions are gone, every tool is listed from the first request, and deleting takes two round trips. Self-hosting more than one replica now requires QASE_MCP_REQUEST_STATE_KEY.

From v1 to v2: v2 consolidated 83 v1 tools into 29 task-oriented tools (30 total, including a discovery tool), and has since grown to 40 (42 total). Tool names and response shapes have changed.

Both upgrades, with the complete v1 → v2 tool mapping table and before/after examples: docs/migration.md.

Tools

42 tools across 6 groups (40 task-oriented tools plus two meta tools: qase_discover_tools to search the catalogue and qase_tool_help to read a tool's full documentation). All of them are listed from the first request:

Group	Count	Description
Read	2	Fetch any entity by type/ID, or bootstrap full project context in one call
QQL	2	Search across cases, runs, results, defects, and plans with Qase Query Language
Write	32	Create, update, and delete cases (single or up to 100 at once), runs, results, defects, suites, milestones, plans, shared steps, environments, and attachments; link cases and runs to Jira issues; propose and manage test case reviews
Composite	3	Multi-step workflows in one call: CI reporting, defect triage, regression run setup
Escape hatch	1	Direct REST API access for any endpoint not covered by the tools above
Meta	2	`qase_discover_tools` — search the catalogue by what you are trying to do; `qase_tool_help` — the full documentation of one tool, on demand

Full tool-by-tool reference with parameters: docs/tools.md.

Documentation

docs/connect.md — connect to the hosted Qase MCP (Claude, Cursor, Codex, other clients)
docs/self-run.md — install and run the server yourself (config, clients, transports)
docs/tools.md — full tool reference, groups, and the discovery model
docs/troubleshooting.md — auth, OAuth/connector, and SSL issues
docs/migration.md — upgrade guides: 2.x → 3.0.0, and the v1 → v2 tool mapping

Contributing

Contributions are welcome! See CONTRIBUTING.md for development setup, testing, and linting guidelines.

License

MIT License — see LICENSE for details.

Support

Documentation: https://docs.qase.io/en/articles/14984302-qase-mcp-server
Email: support@qase.io
GitHub Issues: https://github.com/qase-tms/qase-mcp-server/issues

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Qase Test Management

Qase Test Management is an MCP server that connects AI assistants to Qase Test Management Platform through the Model Context Protocol. It provides tools to read and write test cases, runs, results, defects, suites, milestones, and related project data, including composite workflows, QQL search, project context, and direct REST API access.

The Qase MCP server lets AI assistants manage test cases, runs, results, defects, suites, milestones, and other Qase data. It includes tools for project context, case creation and updates, CI result reporting, defect triage, QQL searches, test case review, and multi-step regression workflows.

You can connect to the hosted Qase MCP server at https://mcp.qase.io/mcp through supported MCP clients such as Claude, Cursor, or Codex. The hosted option uses Qase sign-in; alternatively, you can run the server locally with your own Qase API token.

The hosted Qase MCP server requires the Enterprise plan and a workspace on Qase’s main cloud at qase.io. If you use another plan or a dedicated Qase instance, run the MCP server yourself with your own API token.

Related MCP servers

All in Developer Tools All alternatives

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Qase Test Management AllMCPs Directory Badge

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/qase-test-management?style=directory)](https://allmcps.com/mcp/qase-test-management)

HTML Embed

<a href="https://allmcps.com/mcp/qase-test-management"><img src="https://allmcps.com/api/badge/qase-test-management?style=directory" alt="Qase Test Management on AllMCPs" /></a>

At a glance

Category: Developer Tools
Transport: STDIO
Runtime: Node.js
Last updated: Oct 21, 2026

GitHub stars37

Last commit6d ago

npm / month7,170

75Quality signal: Great · 75/100How this signal is calculated ▾

Server availability25/25

Verified ownership10/20

Documentation & tools29/30

Adoption & activity11/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

Own this project?

This listing is pre-filled from public sources. Claim it via your GitHub README, a site badge, or DNS TXT to edit it and earn the Verified badge.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically.

Claim this listing

Install Qase Test Management

What it can do

Supply-chain signal

Adoption & maintenance

From the project README

Qase MCP Server

Table of Contents

Overview

Use Cases

Quick Start

Use the hosted Qase MCP (recommended)

Run it yourself

Building on top of this server

Upgrading

Tools

Documentation

Contributing

License

Support

Links

Frequently Asked Questions about Qase Test Management

What is the Qase Test Management MCP server?

What can the Qase MCP server do?

How do I connect an AI assistant to Qase MCP?

Does the hosted Qase MCP server require a specific Qase plan?

AllMCPs Directory Badge