get_projectsLABSCO SUMMARY
The bulk create is the tool that changes the workflow.
Creating cases one at a time from a chat is slower than typing them, so the interesting call is the bulk one: a specification becomes a set of cases with their suites assigned in a single write. Suites nest through a parent ID, so a structure can be built the same way. Everything here writes to a live test management project, so aim it at the right project_code — there is no dry run.
What it is
An MCP server for the Qase test management platform. It reads projects and test cases, and writes new cases, suites and test runs, which is what makes 'turn this specification into test cases' something that ends in Qase rather than in a chat transcript.
What you get
get_projectslists the projects available to your tokenget_test_casesreturns the cases for a project, optionally narrowed to one suite withsuite_idcreate_test_caseadds a case from aproject_codeand atitle, with an optional descriptioncreate_test_cases_in_bulktakes an array of cases, each with its own title, description and suite, so a whole set lands in one callcreate_suitecreates a test suite, with optional description, preconditions and aparent_idfor nestingcreate_test_runcreates a run, optionally seeded with the case IDs it should include- Errors distinguish an invalid token, a missing or malformed parameter, and an error returned by Qase itself
Requirements
A Qase API token, set as QASE_API_TOKEN in the client's server configuration. Node.js v23.5.0 and TypeScript; npm install then npm run build, after which the client launches the built entry point with node.
Setup effort
Build from source — git clone https://github.com/RayYokoyama/qase-mcp-server.git
USE CASES
Turning a specification into test cases
Draft the cases in conversation, then write the whole set into the project in one call.
Organising cases as you create them
Create the suite first, nest it if needed, and assign cases to it as they are written.
Setting up a regression run
Create the run and seed it with the case IDs it should cover.
Seeing what already exists before adding more
List the projects and read the cases in a suite before writing duplicates.
6 tools
Listed in project docs. Your client may show a different list.
get_test_casescreate_test_casecreate_suitecreate_test_runcreate_test_cases_in_bulkBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
- Node.js (the README names v23.5.0)
- A Qase API token — QASE_API_TOKEN in the client configuration's env
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
git clone https://github.com/RayYokoyama/qase-mcp-server.git
cd qase-mcp-server
npm install
npm run buildMCP Clients
Cline
Add to Cline's cline_mcp_settings.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": []
}
}
}<YOUR_PATH_TO_QASE_MCP_SERVER> is the full path of the folder the clone step creates (build/index.js appears after npm run build).