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_projects` lists the projects available to your token
`get_test_cases` returns the cases for a project, optionally narrowed to one suite with `suite_id`
`create_test_case` adds a case from a `project_code` and a `title`, with an optional description
`create_test_cases_in_bulk` takes an array of cases, each with its own title, description and suite, so a whole set lands in one call
`create_suite` creates a test suite, with optional description, preconditions and a `parent_id` for nesting
`create_test_run` creates 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 — clone the repository and build it, then point your client at the binary