Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
MCP Server for software testing, test case management, test execution, and defect tracking.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
QATOUCH_DOMAIN, QATOUCH_API_TOKEN标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"qatouch": {
"command": "npx",
"args": [
"-y",
"qatouch-mcp-server"
],
"env": {
"QATOUCH_DOMAIN": "your-value",
"QATOUCH_API_TOKEN": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add qatouch --env QATOUCH_DOMAIN=your-value --env QATOUCH_API_TOKEN=your-value -- npx -y qatouch-mcp-server运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"qatouch": {
"command": "npx",
"args": [
"-y",
"qatouch-mcp-server"
],
"env": {
"QATOUCH_DOMAIN": "your-value",
"QATOUCH_API_TOKEN": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"qatouch": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"qatouch-mcp-server"
],
"env": {
"QATOUCH_DOMAIN": "your-value",
"QATOUCH_API_TOKEN": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 qatouch 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:QATOUCH_DOMAIN, QATOUCH_API_TOKEN
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.1.8)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, dotnet-mcp
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Official Model Context Protocol (MCP) server for QA Touch.
QA Touch is a modern test management platform for organizing projects, test cases, test runs, execution results, defects, requirements, releases, and QA reporting. This MCP server lets MCP-compatible AI assistants interact with QA Touch through a secure, tool-based interface.
QA Touch - Claude Skills Repository - https://github.com/qatouch/qatouch-claude-skills
Run directly with npx:
npx -y qatouch-mcp-server
Or install globally:
npm install -g qatouch-mcp-server
qatouch-mcp-server
The server requires these environment variables:
QATOUCH_DOMAIN=yourdomain
QATOUCH_API_TOKEN=yourtoken
Add this server to your Claude Desktop MCP configuration.
Windows config location:
%APPDATA%\Claude\claude_desktop_config.json
macOS config location:
~/Library/Application Support/Claude/claude_desktop_config.json
Linux config location:
~/.config/Claude/claude_desktop_config.json
Configuration:
{
"mcpServers": { "qatouch": { "command": "npx", "args": [ "-y", "qatouch-mcp-server" ], "env": { "QATOUCH_DOMAIN": "yourdomain", "QATOUCH_API_TOKEN": "yourtoken" } } } }
Restart Claude Desktop after saving the file.
| Tool | Description |
|---|---|
count_all_projects | Get the total number of QA Touch projects available for the domain |
count_defects | Get the total number of defects available for a QA Touch project |
count_modules | Get the total number of modules available for a QA Touch project |
count_releases | Get the total number of releases available for a QA Touch project |
count_requirements | Get the total number of requirements available for a QA Touch project |
count_test_cases | Get the total number of test cases available for a QA Touch project |
count_test_runs | Get the total number of test runs available for a QA Touch project |
create_bulk_test_cases | Create multiple QA Touch test cases from a scenario |
create_defect | Create a QA Touch defect with priority and issue summary |
create_exploratory_test_case | Create a QA Touch exploratory-session test case without structured steps |
create_module | Create a module in a QA Touch project |
create_project | Create a new QA Touch project |
create_release | Create a new release or milestone in a QA Touch project |
create_requirement | Create a requirement in a QA Touch project requirement document |
create_requirement_document | Create a requirement document in a QA Touch project |
create_test_run_with_modules | Create a new test run by selecting one or more module keys |
create_test_case | Create a QA Touch test case with structured steps |
create_text_test_case | Create a QA Touch test case using the text template endpoint |
import_test_cases | Import test cases into a QA Touch project using a CSV file |
list_defect_environments | List all environments available for QA Touch defects |
list_defect_issue_types | List all issue types available for QA Touch defects |
list_defect_severities | List all severities available for QA Touch defects |
list_defect_statuses | List all statuses available for QA Touch defects |
list_defects | Get all defects from a project |
list_modules | Get all modules from a project |
list_projects | Retrieve all QA Touch projects |
list_releases | Get all releases from a project |
list_requirement_documents | List requirement documents for a QA Touch project |
list_requirements | Get all requirements from a project |
list_test_cases | Get all test cases from a project |
list_test_run_available_users | List users available for testing in a QA Touch project |
list_test_run_result_history | List history for a QA Touch test run result |
list_test_run_results | List all results for a QA Touch test run |
list_test_run_statuses | List all statuses available for QA Touch test runs |
list_test_runs | Get all test runs from a project |
list_workspace | List all QA Touch workspaces available for the domain |
search_defects | Fetch defects for a project and search issue summary |
search_modules | Fetch modules for a project and search module name |
search_project | Search test cases, modules, requirements, defects, and releases in a project |
search_releases | Fetch releases for a project and search milestone name |
search_requirements | Fetch requirements for a project and search title and description |
search_test_cases | Fetch all test cases for a project and search test case title and description |
update_test_run_result_status | Update the status of a single QA Touch test run result |
update_test_run_results_by_code | Batch update QA Touch test run result statuses by test case code |
/path/to/testcases.csv into project ABCInstall dependencies:
npm install
Run the MCP server locally:
npm start
Environment variables are required when running locally:
QATOUCH_DOMAIN=yourdomain QATOUCH_API_TOKEN=yourtoken npm start
This repository currently defines only the start script in package.json.
src/
api/ QA Touch API client config/ Environment variable validation tools/ MCP tool definitions and handlers index.js MCP server entry point and tool registration examples/ Prompt and client setup examples
Contributions are welcome. See CONTRIBUTING.md for development workflow, coding standards, and pull request guidance.
This project is licensed under the MIT License.