Qase MCP Server

Official

by qase-tms

Overview Schema Source Related Servers Discussions(1)Admin

TypeScript

Remote

Create or update test case

qase_case_upsert

Create or update a single test case in Qase. Provide an ID to update an existing case, or omit it to create a new one.

Instructions

Create or update a single test case. With id it updates that case, without id it creates a new one. Enum fields (priority, severity, type, layer, behavior, automation, is_flaky) accept either a label such as "high" or "blocker" or the project's numeric ID — the server normalizes both. Steps can be classic action/expected pairs or Gherkin, and may reference shared steps by hash. Writing more than one case? Use qase_case_bulk_create instead: it takes a list and sends one request. If the project has "Test case review" enabled, direct writes may need to go through a review — run qase_discover_tools with "review" for those tools. Cost: one API call, about 0.6s to create and 0.4s to update. Ten sequential calls measured 5.6s against 1.2s for one qase_case_bulk_create writing the same ten, so a loop is roughly four times slower.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Case ID — if provided, updates the case; if omitted, creates a new one
`code`	Yes	Project code (2-10 uppercase letters, numbers, or underscores)
`tags`	No	Tag names, e.g. ["smoke", "billing"]
`type`	No	Type label or numeric ID
`layer`	No	Layer label or numeric ID
`steps`	No	Ordered test steps; omit for a case without steps
`title`	Yes	Test case title
`status`	No	Status label or numeric ID
`behavior`	No	Behavior label or numeric ID
`is_flaky`	No	Is flaky label or numeric ID (0=No, 1=Yes). A boolean is accepted too.
`priority`	No	Priority label or numeric ID (0=not set, 1=high, 2=medium, 3=low)
`severity`	No	Severity label or numeric ID
`suite_id`	No	ID of the suite that holds the case
`automation`	No	Automation status (label, slug, or numeric ID: 0=Manual / is-not-automated, 1=To be automated, 2=Automated)
`steps_type`	No	How steps are written: "classic" action/expected pairs, or "gherkin" scenario text
`attachments`	No	Attachment hashes from qase_attachment_upload
`description`	No	Free-form description of what the case covers
`custom_field`	No	Custom field values keyed by field ID, e.g. { "12": "value" }
`milestone_id`	No	ID of the milestone the case belongs to
`preconditions`	No	State the system must be in before the steps run
`postconditions`	No	State to restore or verify after the steps run

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv2.5.1Sep 19, 2026

addedInput schema / properties / custom_field / description

Added value: +"Custom field values keyed by field ID, e.g. { \"12\": \"value\" }"

addedInput schema / properties / description / description

Added value: +"Free-form description of what the case covers"

addedInput schema / properties / milestone_id / description
```
Added value: +"ID of the milestone the case belongs to"
```

addedInput schema / properties / postconditions / description

Added value: +"State to restore or verify after the steps run"

addedInput schema / properties / preconditions / description

Added value: +"State the system must be in before the steps run"

addedInput schema / properties / steps / description

Added value: +"Ordered test steps; omit for a case without steps"

addedInput schema / properties / steps_type / description

Added value: +"How steps are written: \"classic\" action/expected pairs, or \"gherkin\" scenario text"

addedInput schema / properties / suite_id / description
```
Added value: +"ID of the suite that holds the case"
```

addedInput schema / properties / tags / description

Added value: +"Tag names, e.g. [\"smoke\", \"billing\"]"

Changed2 schema fields changedv2.5.0Sep 17, 2026
- addedInput schema / properties / is_flaky / description
```
Added value: +"Is flaky label or numeric ID (0=No, 1=Yes). A boolean is accepted too."
```
- changedInput schema / properties / is_flaky / type
```
Previous value: -"boolean"New value: +"string"
```
Changed3 schema fields changedv2.2.1Aug 19, 2026
- addedInput schema / properties / attachments / description
```
Added value: +"Attachment hashes from qase_attachment_upload"
```
- changedInput schema / properties / steps / items / properties / attachments / description
```
Previous value: -"Attachment hashes"New value: +"Attachment hashes from qase_attachment_upload"
```
- changedInput schema / properties / steps / items / properties / steps / items / properties / attachments / description
```
Previous value: -"Attachment hashes"New value: +"Attachment hashes from qase_attachment_upload"
```

Changed6 schema fields changedv2.0.3Aug 12, 2026

changedInput schema / properties / steps / items / properties / action / description

Previous value: -"Step action (classic steps)"New value: +"Step action (classic steps). Not needed when `shared` is set."

addedInput schema / properties / steps / items / properties / shared

Added value: +{
+  "description": "Hash of an existing shared step to insert at this position, from `qase_shared_step_upsert`. The step then reuses that shared step instead of defining its own content, so `action` can be omitted. Reading the case back reports the link as `shared_step_hash`.",
+  "type": "string"
+}

addedInput schema / properties / steps / items / properties / shared_step_hash

Added value: +{
+  "description": "Alias for `shared` — the name used when reading a case. Sent to the API as `shared`.",
+  "type": "string"
+}

changedInput schema / properties / steps / items / properties / steps / items / properties / action / description

Previous value: -"Step action (classic steps)"New value: +"Step action (classic steps). Not needed when `shared` is set."

addedInput schema / properties / steps / items / properties / steps / items / properties / shared

Added value: +{
+  "description": "Hash of an existing shared step to insert at this position, from `qase_shared_step_upsert`. The step then reuses that shared step instead of defining its own content, so `action` can be omitted. Reading the case back reports the link as `shared_step_hash`.",
+  "type": "string"
+}

addedInput schema / properties / steps / items / properties / steps / items / properties / shared_step_hash

Added value: +{
+  "description": "Alias for `shared` — the name used when reading a case. Sent to the API as `shared`.",
+  "type": "string"
+}

Addedv2.0.0Jul 29, 2026

TDQS

A5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds substantive behavior: enum labels and numeric IDs are normalized by the server, steps support classic/Gherkin/shared-hash references, and direct writes may be gated by 'Test case review.' It even discloses measured latency and cost tradeoffs, which no annotation captures.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core create/update behavior, then moves through enum normalization, steps, bulk alternative, review caveat, and cost data. Every sentence carries distinct information; there is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 21-parameter nested-object tool with no output schema, the description covers the operational decisions an agent actually needs: when to create vs. update, when to switch to bulk, how enum values are normalized, how shared steps are referenced, and how review may block writes. The tradeoff of not stating the success return payload is minor against the richness of the schema and the behavioral guidance provided.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% parameter description coverage, so the baseline is 3, but the description adds genuinely useful cross-cutting semantics: the label-or-ID normalization rule, the boolean-accepted-for-is_flaky behavior, and the classic-vs-Gherkin step distinction. This goes well beyond restating individual parameter schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear verb-resource pair: 'Create or update a single test case.' It immediately explains the id-based branch that selects create vs. update, and it explicitly distinguishes itself from qase_case_bulk_create. An agent can tell what this tool does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit routing guidance: 'Writing more than one case? Use qase_case_bulk_create instead.' It also explains when to consult qase_discover_tools for review-enabled projects. This is direct when-to-use and when-not-to-use guidance, not just implied context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Create or update test case

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools