Qase Test Management

Name: Qase Test Management
Author: qase-tms

by qase-tmsversion 3.0.6i★ –iComputer or cloud

Registry nameio.qase/mcp-server

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Other
You need to fill in: QASE_API_TOKEN

Install

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

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: QASE_API_TOKEN, QASE_API_DOMAIN, QASE_API_PROTOCOL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.qase.io/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into 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"
      }
    }
  }
}

Run this in your terminal

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

Or run it on your computer

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

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.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"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "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"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.qase.io/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

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.

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 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain qase.io (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 327 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

Compared with others in Otheri

More stars than 0% of the other 32509 servers in this category
Published to the registry more recently than 93% of the other 32509 servers in this category
Basic checks equal to or better than 100% of the other 32509 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 3 of 3 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 –, and the latest version (3.0.6) reached the registry 2 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 in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Fomu MCP

Alternatives

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

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Fomu MCP

by gabrielmahia

Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.

Runs on your computerUpdated today

Install

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

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

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

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Fomu MCP

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