get_projectsLABSCO SUMMARY
The bulk tool is the reason to install it.
Writing test cases one at a time in a web UI is why test plans stay in documents. Handing over a described plan and getting a suite of cases with their steps created in one call is a different workflow, and it is the one call here that does not have an easy manual equivalent. The reads are minimal — projects and cases — so treat this as an authoring tool rather than a way to browse results.
What it is
An MCP server for the Qase test management platform. It covers the write-heavy part of test management: creating cases with steps and preconditions, organising them into suites, and opening test runs — plus the reads needed to know where to put things.
What you get
- Your projects listed, and the test cases in one, optionally narrowed to a single suite —
get_projects,get_test_cases - A test case created with title, description, preconditions, postconditions, a suite, and steps carrying an action and an expected result —
create_test_case - Many cases created in one call, each with its own steps and suite, which is what turns a written test plan into a populated project —
create_test_cases_in_bulk - A test suite created, nested under a parent when you want a hierarchy —
create_suite - A test run opened with a title, description and the case IDs to include —
create_test_run - An existing case updated, including severity, priority, type, layer, the flaky flag, suite and steps —
update_test_case
Requirements
A Qase API token, passed as QASE_API_TOKEN. Node.js v22.17.0 and TypeScript. There is no published package: clone, npm install, npm run build, and point your client at build/index.js. Tools identify a project by its project code rather than a numeric ID, so start from the project list. The README is written in Japanese.
Setup effort
Build from source — git clone https://github.com/raksul/qase-mcp-server.git
USE CASES
01
Turning a written test plan into a populated project
Hand over the plan and create the cases in bulk, each with its steps and its suite, instead of typing them in one by one.
02
Adding coverage for a feature you just built
Create the case with preconditions and steps that carry expected results, so it is runnable rather than a title.
03
Setting up a regression run before a release
Pull the case IDs from the suite, then open a run containing exactly those.
04
Cleaning up cases that have drifted
Update severity, priority and the flaky flag on the existing case rather than creating a replacement.
7 tools
Listed in project docs. Your client may show a different list.
get_test_casescreate_test_casecreate_suitecreate_test_runcreate_test_cases_in_bulkupdate_test_caseBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
- node on PATH
- Node.js v22.17.0
- QASE_API_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/raksul/qase-mcp-server.git
cd qase-mcp-server
npm install
npm run buildMCP Clients
Cline
CLINE · JSON
{
"mcpServers": {
"qase": {
"command": "node",
"args": [
"<YOUR_PATH_TO_QASE_MCP_SERVER>/build/index.js"
],
"env": {
"QASE_API_TOKEN": "<YOUR_QASE_API_TOKEN>"
},
"disabled": false,
"autoApprove": []
}
}
}Use a full path here: <YOUR_PATH_TO_QASE_MCP_SERVER> is the absolute path of the qase-mcp-server folder you cloned (npm run build writes build/index.js there) — a relative path is resolved against the client's own working folder and fails.
