qTest MCP Server
This server allows AI assistants to interact with qTest Manager for managing test projects, test design, and test execution through natural language.
Projects
List all qTest projects or fetch a specific project by ID.
Test Design
Modules: List root-level modules, children of a module, or search by name; create new modules or sub-modules; delete modules (cascades to child modules and test cases).
Test Cases: Fetch test cases from a module with optional filters (Type, Status, Priority, etc.); list field definitions and allowed values for a project; update test case properties (Status, Type, Priority, etc.) using human-readable labels.
Test Execution
Test Cycles: List root-level cycles, children of a cycle, or filter by name/ID; create new cycles or sub-cycles; delete cycles (cascades to child cycles, suites, and runs).
Test Runs: Add existing test cases as test runs into a test execution suite.
Integrates with qTest Manager (a Tricentis product) to browse projects, manage test design modules, and build test execution cycles programmatically.
qtest-mcp-server
Disclaimer: This is an unofficial, community-built MCP server for qTest Manager. Not affiliated with or endorsed by Tricentis.
An MCP (Model Context Protocol) server that lets codebase or AI assistants (Claude, etc.) interact with qTest Manager — browse projects, manage test design modules, and build test execution cycles — all through natural language.
Available on npm : qtest-mcp-server
Available on glama : glama.ai
Prerequisites
Node.js 18+
A qTest Manager account with API access
Your qTest base URL and API token
Related MCP server: TestRail MCP Server
Installation & Setup
1. Clone and build
git clone https://github.com/your-username/qtest-mcp-server.git
cd qtest-mcp-server
npm install
npm run build2. Configure your MCP client
Add the server to your .mcp.json. A ready-to-copy example is provided in .mcp.example.json at the root of this repo.
{
"mcpServers": {
"qtest": {
"command": "node",
"args": ["dist/index.js"],
"env": {
"QTEST_BASE_URL": "https://your-org.qtestnet.com",
"QTEST_TOKEN": "your-personal-access-token"
}
}
}
}Copy
.mcp.example.jsonto.mcp.json, fill in your values, and place it in your project root (for project-scoped access).Your API token can be generated from qTest Manager under Profile > API & SDK.
Available Tools
Projects
Tool | Description |
| List all qTest projects, or fetch a single project by ID |
Test Design
Tool | Description |
| List root-level modules, children of a module, or search by name |
| Create a new module (or sub-module) in Test Design |
| Delete a module — cascades to all child modules and test cases |
| Fetch test cases from a module with optional filters (Type, Status, Priority, etc.) |
| List all field definitions for test cases in a project, including allowed values for each field |
| Update properties of a test case (Status, Type, Priority, Test Suite) using human-readable labels |
Test Execution
Tool | Description |
| List root-level test cycles, children of a cycle, or filter by name/ID |
| Create a test cycle (or sub-cycle) in Test Execution |
| Delete a test cycle — cascades to all child cycles, suites, and runs |
| Add test cases as test runs into a test execution suite |
Tool Usage Examples
list-projects
List all projects or get a specific one.
list all projectsget project with ID 100001list-modules
List root-level modules, children, or search by name.
list modules for project 100001list child modules of module 60000001 in project 100001search for modules named "Login" in project 100001create-module
Create a module at root or nested under a parent.
create a module named "Sprint 12 Tests" in project 100001create a sub-module named "Smoke Tests" under module 60000001 in project 100001delete-module
Delete a module and all its contents permanently.
delete module 60000099 in project 100001Warning: this cascades — all child modules and test cases are deleted.
list-test-cases
Fetch test cases from a module, optionally filtered.
list all test cases in module 60000001 of project 100001list test cases of type "Manual" in module 60000001 of project 100001list test cases with status "Approved" in module 60000001 of project 100001Available filter fields: Type, Status, Priority, version, etc.
list-test-case-fields
List all field definitions for test cases in a project, including each field's allowed values. Call this first to discover what values you can pass to update-test-case-properties.
list test case fields for project 100001what values are allowed for the Status field in project 100001?update-test-case-properties
Update one or more properties of a test case using human-readable labels. Use list-test-case-fields first to see valid values.
update test case 130000001 in project 100001 to set Status to "In Progress"set the Type to "Automated" and Priority to "High" for test case 130000001 in project 100001assign test case 130000001 in project 100001 to the "Regression" and "Smoke" test suitesNote: Values are validated dynamically against the project's field definitions — pass the exact label as shown by
list-test-case-fields(case-insensitive).
list-test-cycle
List test cycles at root, under a parent, or by name/ID.
list all test cycles in project 100001list child cycles of test cycle 19000001 in project 100001find test cycle named "Regression" in project 100001create-test-cycle
Create a test cycle at root or nested under a parent.
create a test cycle named "Release 3.0" in project 100001create a sub-cycle named "Week 1" under test cycle 19000001 in project 100001delete-test-cycle
Delete a test cycle and all its contents permanently.
delete test cycle 19000099 in project 100001Warning: this cascades — all child cycles, test suites, and test runs are deleted.
add-test-cases
Add test cases as test runs into a test execution suite.
Note: The target is a test suite (inside a test cycle), not the cycle itself. You must supply test case IDs and names explicitly — use
list-test-casesfirst to retrieve them.
add the following test cases to suite 88000001 in project 100001:
- ID 130000001: "Verify login with valid credentials"
- ID 130000002: "Verify error on invalid password"Development
# Run in dev mode (no build needed)
npm run dev
# Build for production
npm run build
# Run tests
npm testLicense
MIT
Available Tools
9 toolsadd-test-casesB
Test Execution — add test cases as test runs into a qTest Test Execution suite (inside a test cycle)
Inputs: projectId (required), suiteId (required), testCases (required).
create-moduleC
Test Design — create a new module in qTest Test Design to organise test cases
Inputs: projectId (required), name (required), parentId.
create-test-cycleC
Test Execution — create a test cycle (execution folder) in qTest Test Execution to group test runs for a sprint, release, or regression campaign
Inputs: projectId (required), name (required), parentId.
delete-moduleA
Test Design — delete a qTest test module by numeric id. Cascades to all child modules and test cases automatically.
Inputs: projectId (required), id (required).
delete-test-cycleA
Test Execution — delete a qTest test cycle by numeric id. Cascades to all child test cycles, test suites, and test runs automatically.
Inputs: projectId (required), id (required).
list-modulesA
Test Design — list qTest Test Design modules. Pass query to search by name, parentId to list children, or neither for root-level listing
Inputs: projectId (required), parentId, query.
list-projectsA
Projects — list all qTest projects, or fetch a single project by ID
Inputs: projectId.
list-test-casesA
Test Design — fetch test cases from a qTest module with optional property filters (Type, Status, Priority, version, etc.). Requires moduleId (numeric).
Inputs: projectId (required), moduleId (required), filters.
list-test-cycleA
Test Execution — list qTest test cycles. Omit all optional args for root-level listing, provide id for a single cycle, or provide name to filter by name (case-insensitive exact match)
Inputs: projectId (required), id, name, parentId.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Every tool has a clearly distinct purpose within the qTest domain. The tools are separated by functional area (Test Design, Test Execution, Projects) and there is no overlap in their operations.
All tool names follow a consistent verb-noun pattern using kebab-case (e.g., create-module, list-test-cases). The naming is predictable and unambiguous.
With 9 tools, the set is well-scoped for a test management server. It covers essential create, delete, and list operations for modules and test cycles, plus a few specialized actions, without being excessive or insufficient.
The tool set covers core operations for modules, test cycles, projects, and test case execution. Minor gaps exist: no update tools for modules or test cycles, and no tool to individually create a test case (only add as test run).
Maintenance
Related MCP Connectors
Free test management over MCP: projects, test cases, plans, runs, environments and tasks.
Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.
Official Todoist MCP server. Manage tasks and projects. Hosted, no API key needed.
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
Related MCP Servers
- AlicenseCqualityFmaintenanceA TypeScript-based MCP server that provides integration with the Qase test management platform, allowing you to manage projects, test cases, runs, results, plans, suites, and shared steps.2612MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for TestRail that enables AI assistants to interact with TestRail's test management platform. It can query and manage projects, test cases, runs, results, plans, milestones, and more.MIT
- AlicenseBqualityDmaintenanceMCP server to interact with the QMetry for Jira API, enabling management of test cases, test cycles, test plans, and more through well-defined tools.9388 npmApache 2.0
- AlicenseAqualityDmaintenanceMCP server for QTM4J (QMetry Test Management for Jira) Open API, enabling test case and cycle management via natural language.2139 npmMIT