Qase Test Management

Name: Qase Test Management
Author: qase-tms

by qase-tmsversion 3.0.6i★ 37iComputer or cloud

Registry nameio.qase/mcp-server

How to install

What it does

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

Connects Computer or cloud
Account or key Cloud: Sign in to the service when you connect (OAuth) · Local: Needs QASE_API_TOKEN
Category Other

Install

Pick the AI app you use, then copy the settings.

Passed 5/5 checks · What you ask goes through the maker’s server (mcp.qase.io) · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

ClaudeWeb · app · phoneChatGPTWebClaude CodeTerminalCursorCode editorVS CodeCode editorOtherOther apps

Pick your app and the steps appear below.

Works with Claude · about 2 min

No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it

Open Claude’s Connectors page
CustomizeConnectors
Done
Click “Add” → “Custom” → “Web” and fill in these 2 fields
Copy each value into the field with the same name in Claude, then click Continue
Name · NameQase Test Management
Remote MCP server URL · Addresshttps://mcp.qase.io/mcp
Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
Done
Turn it on in a chat
+ConnectorsQase Test Management
Done
Try it
Use Qase Test Management and tell me what you can do for me, then show me one thing
✓ If Claude says it is using Qase Test Management or shows a Qase Test Management tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with ChatGPT, depending on your plan

Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only

Open ChatGPT’s add-MCP page on the web
Plugins+Add custom MCP server
Done
Fill in the name and address
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Name · NameQase Test Management
Connection · Addresshttps://mcp.qase.io/mcp
Done
Pick Qase Test Management in a chat
Start a new chat and pick Qase Test Management from your plugins before typing
Done
Try it
Use Qase Test Management and tell me what you can do for me, then show me one thing
✓ If ChatGPT says it is using Qase Test Management or shows a Qase Test Management tool in the answer, you are connected

Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Claude Code · about 2 min

No key, nothing to install

Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Done

Paste this command and press Enter

claude mcp add --transport http --scope user qase https://mcp.qase.io/mcp

Done

Type /mcp in Claude Code
You should see Qase Test Management listed as connected
Done
Try it
Use Qase Test Management and tell me what you can do for me, then show me one thing
✓ If Claude Code says it is using Qase Test Management or shows a Qase Test Management tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor · about 2 min

No key, nothing to install

Click this button to open Cursor
Open in Cursor
Cursor asks you to confirm; click Install
Done
Open the AI chat in Cursor in Agent mode
Done
Try it
Use Qase Test Management and tell me what you can do for me, then show me one thing
✓ If Cursor says it is using Qase Test Management or shows a Qase Test Management tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code · about 2 min

No key, nothing to install

Click this button to open VS Code
Open in VS Code
VS Code asks you to confirm; click Install
Done
Open the AI chat in VS Code in Agent mode
Done
Try it
Use Qase Test Management and tell me what you can do for me, then show me one thing
✓ If VS Code says it is using Qase Test Management or shows a Qase Test Management tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

Address for apps that connect over the web

Addresshttps://mcp.qase.io/mcp

JSON settings are under “For developers” below

Stuck? Ask people who use Qase Test Management💬 Discussion →

For developers: Terminal commands and JSON settings

Over the web

Claude Code

claude mcp add --transport http --scope user qase https://mcp.qase.io/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "qase": {
      "url": "https://mcp.qase.io/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "qase": {
      "type": "http",
      "url": "https://mcp.qase.io/mcp"
    }
  }
}

Installed on your computer

Claude Code

claude mcp add --scope user qase --env QASE_API_TOKEN=your-value --env QASE_API_DOMAIN=your-value --env QASE_API_PROTOCOL=your-value -- npx -y @qase/mcp-server

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "qase": {
      "command": "npx",
      "args": [
        "-y",
        "@qase/mcp-server"
      ],
      "env": {
        "QASE_API_TOKEN": "your-value",
        "QASE_API_DOMAIN": "your-value",
        "QASE_API_PROTOCOL": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "qase": {
      "command": "npx",
      "args": [
        "-y",
        "@qase/mcp-server"
      ],
      "env": {
        "QASE_API_TOKEN": "your-value",
        "QASE_API_DOMAIN": "your-value",
        "QASE_API_PROTOCOL": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "qase": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@qase/mcp-server"
      ],
      "env": {
        "QASE_API_TOKEN": "your-value",
        "QASE_API_DOMAIN": "your-value",
        "QASE_API_PROTOCOL": "your-value"
      }
    }
  }
}

Values you fill in

QASE_API_TOKEN secret required env
Qase API token from app.qase.io > Settings > API Tokens
QASE_API_DOMAIN env
Custom API domain for enterprise (default: api.qase.io)
QASE_API_PROTOCOL env
Scheme used to reach the API domain: http or https. Use http only for self-hosted deployments served without TLS (default: https)

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

GitHub stars i: 37
Downloads per weeki: 9,305/wk
Verified domain: ✓ qase.io
Licence i: MIT
Connection: Computer or cloud
Transport: stdio, streamable-http
Latest versioni: 3.0.6
Categoryi: Other
Published to registryi: Nov 4, 2026
Code last changedi: Nov 4, 2026
Maker: qase-tms
Packages: npm: @qase/mcp-server
Repo: qase-tms/qase-mcp-server
Website: qase.io
Registry status: Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

Claude ChatGPT Goose LM Studio Msty Studio Cherry Studio Cursor VS Code + GitHub Copilot Visual Studio Windsurf (Devin Desktop)Zed Kiro Cline Continue JetBrains AI Assistant Claude Code Codex CLI Gemini CLI OpenCode nodecode Warp LibreChat Open WebUI Raycast

Run on your computer in

Claude Goose LM Studio Msty Studio Cherry Studio Cursor VS Code + GitHub Copilot Visual Studio Windsurf (Devin Desktop)Zed Kiro Cline Continue JetBrains AI Assistant Claude Code Codex CLI Gemini CLI OpenCode nodecode Warp LibreChat Raycast

All apps, with pros and cons →

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 13, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain qase.io (the registry checks domain ownership)
✓ Pass
Still maintained
Code last changed 9 days ago
✓ Pass
Has a licence
Uses MIT
✓ Pass
Endpoint responds
Responded in 151 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

User reviews

No reviews yet

Compared with others in Otheri

More stars than 98% of the other 19476 servers in this category
Published to the registry more recently than 83% of the other 19476 servers in this category
Basic checks equal to or better than 100% of the other 19476 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Qase Test Management safe?

It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: QASE_API_TOKEN

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed 9 days ago, and the latest version (3.0.6) reached the registry 9 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).

What can I use instead?

In the same category: World Monitor, Claude Flow, Windmill

Others in the same category

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 104 tools.

by koala73Widely used★ 90.5KUpdated yesterday

Runs in the cloud✓ service owner · worldmonitor.app

How to connect

Claude Flow

AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.

by ruvnetWidely used↓ 13.5K/wk★ 81.5KUpdated 14 months ago

Runs on your computer

Install

Windmill

Run Windmill scripts and flows and manage jobs, schedules, resources and variables.

by windmill-labsWidely used★ 18.6KUpdated yesterday

Runs in the cloud

How to connect

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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
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](docs/connect.md).

Run it yourself

Works on every plan, including Free and dedicated instances. You need Node.js 20+ and a Qase API token; your MCP client starts the server for you. For example, in Claude Desktop's config:

"mcpServers": { "qase": { "command": "npx", "args": ["-y", "@qase/mcp-server"], "env": { "QASE_API_TOKEN": "your_api_token_here" } } } }

Step-by-step setup for Claude Desktop, Claude Code, Cursor, Codex and OpenCode, plus EU-region and custom-domain settings: [docs/self-run.md](docs/self-run.md). Running one server for a team over HTTP: [docs/hosting.md](docs/hosting.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:

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/integrations.md](docs/integrations.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](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](docs/tools.md).

Documentation

[docs/connect.md](docs/connect.md) — connect to the hosted Qase MCP (Claude, Cursor, Codex, other clients)
[docs/self-run.md](docs/self-run.md) — run the server yourself with your own API token, step by step per client
[docs/hosting.md](docs/hosting.md) — host a shared server: HTTP transports, security, multiple replicas, metrics
[docs/integrations.md](docs/integrations.md) — for integration authors: the integration marker
[docs/tools.md](docs/tools.md) — full tool reference, groups, and the discovery model
[docs/troubleshooting.md](docs/troubleshooting.md) — auth, OAuth/connector, and SSL issues
[docs/migration.md](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

Qase Test Management

What it does

Install

Open Claude’s Connectors page

Click “Add” → “Custom” → “Web” and fill in these 2 fields

Turn it on in a chat

Try it

Open ChatGPT’s add-MCP page on the web

Fill in the name and address

Pick Qase Test Management in a chat

Try it

Open Terminal

Paste this command and press Enter

Type /mcp in Claude Code

Try it

Click this button to open Cursor

Open the AI chat in Cursor in Agent mode

Try it

Click this button to open VS Code

Open the AI chat in VS Code in Agent mode

Try it

Over the web

Installed on your computer

Values you fill in

At a glance

Which apps can use it

Related guides

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Discussion

User reviews

Compared with others in Otheri

Common questions

Others in the same category

World Monitor

Claude Flow

Windmill

README from the maker

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