Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP Server for software testing, test case management, test execution, and defect tracking.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
QATOUCH_DOMAIN, QATOUCH_API_TOKENValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"qatouch": {
"command": "npx",
"args": [
"-y",
"qatouch-mcp-server"
],
"env": {
"QATOUCH_DOMAIN": "your-value",
"QATOUCH_API_TOKEN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add qatouch --env QATOUCH_DOMAIN=your-value --env QATOUCH_API_TOKEN=your-value -- npx -y qatouch-mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"qatouch": {
"command": "npx",
"args": [
"-y",
"qatouch-mcp-server"
],
"env": {
"QATOUCH_DOMAIN": "your-value",
"QATOUCH_API_TOKEN": "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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"qatouch": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"qatouch-mcp-server"
],
"env": {
"QATOUCH_DOMAIN": "your-value",
"QATOUCH_API_TOKEN": "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.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account qatouch, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 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.
You need to fill in: QATOUCH_DOMAIN, QATOUCH_API_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.1.8) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, SSTracker free youth training
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
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.
Free youth sports drills, practice plans and age-group answers for parents and coaches.
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.
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.