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.
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.
- 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`
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.
Build from source — clone the repository and build it, then point your client at the binary