Reading test cases from a chat is convenient; pushing a whole run's results back in one call is what removes a manual step from a CI or exploratory-testing loop. Delete tools cover projects, plans, suites and shared steps, so the token you supply should belong to an account whose reach you have thought about. The README itself flags an official Qase server as the production choice.
An MCP server over the Qase test management API, covering the entities a QA workflow actually moves between: projects, test cases, runs, results, plans, suites and shared steps. Most entities support the full create, read, update and delete cycle rather than read-only lookup.
- Projects listed, fetched by code, created and deleted — `list_projects`, `get_project`, `create_project`, `delete_project`
- Test cases listed for a project, fetched individually, created and updated — `get_cases`, `get_case`, `create_case`, `update_case`
- Test runs listed and read — `get_runs`, `get_run`
- Results read for a project or by code and hash, created one at a time or many in a single bulk call, and updated afterwards — `get_results`, `get_result`, `create_result`, `create_result_bulk`, `update_result`
- Test plans and test suites listed, read, created, updated and deleted — `get_plans`, `create_plan`, `update_plan`, `delete_plan`, `get_suites`, `create_suite`, `update_suite`, `delete_suite`
- Shared steps managed the same way, so a step reused across cases is edited once — `get_shared_steps`, `get_shared_step`, `create_shared_step`, `update_shared_step`, `delete_shared_step`
A Qase API token in `QASE_API_TOKEN`. The npm package name is `mcp-qase` (0.1.0) and it is marked private, so build from a clone with `npm install` and `npm run build`, then have your client run the built `index.js`. Note that Qase now publishes an official MCP server of its own, which the README points to for production use — worth comparing before you commit to this one.
One command plus a key — npx -y github:rikuson/mcp-qase, then supply credentials