Qase

What it is

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 can be created, read and updated, not only looked up.

What you get

• Projects listed, fetched by code and created — list_projects, get_project, create_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 and updated — get_plans, create_plan, update_plan, get_suites, create_suite, update_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

Requirements

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.

Setup effort

Build from source

Tools you get

26 tools when we connected; the project documents 30. The four missing tools are the deletes: delete_project, delete_plan, delete_suite and delete_shared_step. No documented switch enables them.

Requires

QASE_API_TOKEN in your environment