Qase Test Management

Name: Qase Test Management
Author: qase-tms

作者：qase-tms版本 3.0.6i★ –i电脑或云端

注册名称io.qase/mcp-server

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i3 项中通过 3 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 电脑或云端
传输方式: stdio, Streamable HTTP
分类: 其他
你需要填写：QASE_API_TOKEN

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：3 项中通过 3 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
需要你自己填写： QASE_API_TOKEN, QASE_API_DOMAIN, QASE_API_PROTOCOL

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

在云端运行无需安装任何东西，通过互联网连接
npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

打开 Settings → Connectors
点击 Add custom connector
粘贴下面的地址，然后点击 Add
如果要求登录，请登录作者的服务

https://mcp.qase.io/mcp

或者在你的电脑上运行

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 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"
      }
    }
  }
}

在终端中运行这条命令

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

或者在你的电脑上运行

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

或者在你的电脑上运行

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.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 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

或者在你的电脑上运行

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

打开网页版 ChatGPT → Settings → Connectors (Apps)
点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
粘贴下面的地址，起个名字，然后保存
如果要求登录，请登录作者的服务

https://mcp.qase.io/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

QASE_API_TOKEN 机密必填 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)

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

服务器要求先登录，才会列出它的工具。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过域名 qase.io 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
✓ 通过
端点有响应
在 327 毫秒内响应（HTTP 401）
✓ 通过
使用 OAuth 登录
声明支持 OAuth 登录，你的 AI 应用可以带你去登录
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32520 个服务器的 0%
发布到注册中心的时间比此分类中其他 32520 个服务器的 93% 更新
基础检查结果等于或优于此分类中其他 32520 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Qase Test Management 安全吗？

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：QASE_API_TOKEN

它在我的电脑上运行还是在云端？

两种方式都可以：安装在你的电脑上，或者连接云端版本。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（3.0.6）于前天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Toggl 2.0

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

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

在云端运行★ 211昨天更新

安装

Toggl 2.0

作者：toggl

Toggl 2.0 MCP server for tasks, projects, time entries, and workspace operations.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

Toggl 2.0

作者的 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