Claude Qase Test Management connectorWhat Claude can do in your Qase workspace.
The Claude Qase Test Management connector exposes 13 tools: 5 read, 7 write, 1 undocumented. Published by Qase, this desktop extension lets Claude search your test repository, draft and update test cases, set up runs, record results and log defects.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude works in Qase
Qase holds your test cases, suites, runs and defects, and keeping them current takes a lot of clicking between screens. With this extension, you describe what you need and Claude does the work in the conversation: it reads the project, finds the right cases with Qase's own query language, then creates or updates what you asked for.
Turn a spec into test cases. qase_project_context shows the project's suites, milestones and environments, then qase_case_upsert creates each new case or updates an existing one.
Prepare a regression campaign in one go. qase_regression_run opens a run and adds every case from the chosen suites or plan, instead of picking them one by one.
Report a CI pipeline's results. From a finished pipeline's results, qase_ci_report creates the run, records every result and closes it; a failure worth tracking becomes a defect through qase_triage_defect.
What it will not do: nothing starts on its own when a build fails or a run ends; Claude acts only while it answers you, in the desktop app where the extension is installed. Defects cannot be linked to runs or results through Qase's API either. We have no n8n, Make or Zapier page for Qase; our Integrations hub lists the platforms we cover, and the Claude connectors page gathers the others.
Five words before you install
The Claude vocabulary this page uses, in one minute.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do in that account. Claude chooses the tools it needs, and the directory sheet lists them by name.
- Authorization
- The access you give Claude through the service's own sign-in or permission screen, granted once per person and revocable the same way.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes the account, shown in the chat when it matters.
- MCP
- The common standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Qase.
Install the Claude Qase Test Management connector in three steps
- 01
Find Qase in the connector list
In Claude Desktop, open the settings, go to Customize then Connectors, and search for Qase Test Management. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization before each member can install it.
- 02
Start the install and sign in
Launch it from its row with Connect and complete the steps Qase asks for to reach your workspace. If the link breaks later, Disconnect then install again: that is the documented way to repair it.
- 03
Read what you are granting
Before you confirm, read the access screen: it is Qase's screen, not Claude's, and it decides what the access covers. Claude then works within those rights and never beyond what your own Qase account can reach.
The 13 tools of the Qase Test Management connector
Qase Test Management gives Claude 13 tools: 5 that read your account, 7 that change something in it, and 1 no official source describes.
Five tools read your workspace, seven change it, and one is not classified. Names stay exactly as Claude displays them.
- 5 read
- 7 write
- 1 not documented
What Claude reads (5)
5 toolsFive tools to explore a project, fetch any record and search across projects.
qase_discover_tools
Searches Qase's catalogue of additional tools, for needs such as deletions, test plans, milestone management or case reviews, and activates the ones it finds for the session. By default, only the core tools are visible.
qase_get
Retrieves one Qase entity by its type and ID, such as a case, suite, run, result, plan, defect, milestone or environment, and can return only the fields requested. A project code is needed for entities that belong to a project.
qase_project_context
Returns a project's details, suite tree, milestones, environments, custom fields and users in one call. Qase recommends it as the first step when starting work on a project.
qql_help
Fetches one section of the Qase Query Language reference. A topic must always be named, because the whole reference is large, and Qase advises reading the entities section before querying an unfamiliar entity.
qql_search
Searches Qase entities with Qase Query Language, with filters and queries that can span several projects. To count, it aggregates with a SELECT COUNT clause rather than paging through rows one by one.
What Claude changes (7)
7 toolsSeven tools that add or update test cases, runs, results and defects.
qase_case_upsert
Approval: see the ruleCreates a test case, or updates an existing one when its ID is given. Fields such as priority, severity or type accept either labels like high or blocker or numeric IDs, and the server normalises them.
qase_ci_report
Approval: see the ruleRecords a CI pipeline's results in one call: it creates a run, records all results and can complete the run. Batches above 200 are split automatically, up to 2000 results per report.
qase_defect_upsert
Approval: see the ruleCreates a defect, or updates an existing one when its ID is given, status changes included. Setting the status to resolved is how an existing defect gets resolved.
qase_regression_run
Approval: see the ruleSets up a regression run in one call: cases are selected by suite IDs, explicit case IDs or a plan ID, then the run is created with every matching case, instead of the usual sequence of separate steps.
qase_result_record
Approval: see the ruleRecords one or several test results into a run; each result needs a status, and linking the case is recommended. The bulk endpoint takes at most 200 results per request, and a longer list is refused before anything is written.
qase_run_upsert
Approval: see the ruleOpens a new test run, or edits an existing one when its ID is given. Qase's documentation of this tool says nothing more about the fields it accepts, so this page does not list any.
qase_triage_defect
Approval: see the ruleCreates a defect from a test failure. Title, actual result and severity are all required by Qase's API. Since that API cannot attach runs or results to a defect, the failing results are referenced in the actual result text instead.
Undocumented (1)
1 toolOne tool that Qase describes as raw API access, without saying whether it reads or writes.
qase_api
Qase describes it as a direct call to its REST API for endpoints the other tools do not cover: an HTTP method, a path and an optional body, in JSON only, so no file upload. No source says whether a given call reads or changes data, so this page leaves it unclassified.
What Claude asks before it acts
By default, Claude stops and asks before each action it carries out in an account on someone's behalf. Seven of the thirteen Qase tools change your workspace, a thirteenth gives raw API access, and no source describes a confirmation specific to any of them, so that default is what to expect.
On Team and Enterprise workspaces, owners decide whether a member may let certain actions through without being asked each time. They can also restrict what a connector may do for the whole organization, for instance keep reading and close writing, and no member can override that from their own account. Claude acts with the rights of the person who connected it and nothing more: what that person cannot see or edit in Qase stays out of Claude's reach too.
Which Claude plans include it
Anthropic's general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions such as this one install in Claude Desktop.
On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can use it. For this extension's current status, check its sheet in the official directory, linked from the button at the top of this page. No official source publishes plan availability connector by connector; that sheet remains the only place to verify it.
What the Qase Test Management connector does not do
Only Qase documents this extension, on the public repository of its server: neither the Claude help center nor Anthropic's developer docs have a page about it.
A connector is not an automation: Claude calls its tools during a reply, and nothing fires when a pipeline finishes or a test fails. The directory's verification badge is not a security audit, and Anthropic states on every sheet that it does not control the tools a publisher exposes. The thirteen tools on the sheet are a floor, not a ceiling: Qase's discovery tool can switch on others during a session.
Need help connecting Qase Test Management to Claude?
A person reads every message.
