Qase MCP Server: Setup for Claude, Cursor and Other Apps

• Fetches one Qase item by type and ID

  Reads a single case, suite, run, result, plan, defect, milestone, environment, shared step, review, user or similar item. You can ask for only some fields.

  Try: “Show me test case 42 in project DEMO.”

  Read · qase_get

• Gives the full layout of a project in one call

  Returns a project's details, suite tree, milestones, environments, custom fields and users, first 100 of each by default, and caches it for 5 minutes. Best first call when you start work on a project.

  Try: “Show me the structure of project DEMO.”

  Read · qase_project_context

• Searches with Qase's query language

  Runs a Qase Query Language search across cases, runs, results, defects and plans, including counts and cross-project queries.

  Try: “Find all failed results from the last 7 days in project DEMO.”

  Read · qql_search

• Explains the query language

  Returns one section of the QQL reference, such as syntax, entities or examples, so the assistant can write a correct query.

  Try: “Show me the QQL operators.”

  Read · qql_help

• Creates or updates a test case

  Creates a test case, or updates it when you give an ID. Priority, severity and other fields accept labels like "high" and are matched to your workspace settings.

  Try: “Create a high-priority smoke test titled "Login with valid credentials" in DEMO.”

  Write · qase_case_upsert

• Creates up to 100 test cases at once

  Creates many cases in one request, for imports or generated suites. It only creates, and returns the new IDs in order.

  Try: “Create these 20 login test cases in DEMO.”

  Write · qase_case_bulk_create

• Deletes a test case

  Deletes one case and its execution history. It cannot be undone, and each call asks you to confirm.

  Try: “Delete case 17 in DEMO.”

  Delete · qase_case_delete

• Creates or updates a defect

  Creates a defect, or updates one by ID, including setting its status to resolved.

  Try: “Resolve defect 8 in DEMO.”

  Write · qase_defect_upsert

• Deletes a defect

  Deletes one defect by project code and ID, after asking you to confirm.

  Try: “Delete defect 8 in DEMO.”

  Delete · qase_defect_delete

• Creates or updates a test run

  Creates a run, or updates one by ID. You can set its cases, environment, milestone, plan, tags and times.

  Try: “Create a run called "Sprint 12 smoke" in DEMO with cases 1 to 10.”

  Write · qase_run_upsert

• Marks a test run as complete

  Closes a run so no more results are expected.

  Try: “Complete run 42 in DEMO.”

  Write · qase_run_complete

• Deletes a test run

  Deletes one run, after asking you to confirm.

  Try: “Delete run 42 in DEMO.”

  Delete · qase_run_delete

• Records test results into a run

  Adds one or more results (passed, failed, blocked, skipped, invalid) to a run, up to 200 per call. Results are append-only, so a long list is refused rather than split.

  Try: “Record case 1 as passed and case 2 as failed with "timeout" in run 42.”

  Write · qase_result_record

• Deletes a test result

  Deletes one result by run ID and result hash, after asking you to confirm.

  Try: “Delete the last result in run 42.”

  Delete · qase_result_delete

• Creates or updates a test suite

  Creates a suite, or updates one by ID. A parent suite ID nests it.

  Try: “Create a suite called "Checkout" in DEMO.”

  Write · qase_suite_upsert

• Deletes a test suite

  Deletes a suite. If you set delete_cases, every case in it is deleted too. Otherwise the cases move to the parent suite.

  Try: “Delete the Legacy suite in DEMO and keep its cases.”

  Delete · qase_suite_delete

• Creates or updates a milestone

  Creates a milestone, or updates one by ID, with status and due date.

  Try: “Create a milestone "Release 4.2" due on December 1.”

  Write · qase_milestone_upsert

• Deletes a milestone

  Deletes one milestone by project code and ID, after asking you to confirm.

  Try: “Delete milestone 3 in DEMO.”

  Delete · qase_milestone_delete

• Creates or updates a test plan

  Creates a plan from a list of case IDs, or updates one by ID.

  Try: “Create a plan "Regression" with the cases in the Checkout suite.”

  Write · qase_plan_upsert

• Deletes a test plan

  Deletes one plan by project code and ID, after asking you to confirm.

  Try: “Delete plan 5 in DEMO.”

  Delete · qase_plan_delete

• Creates or updates a reusable step

  Creates a shared step that many test cases can include, or updates one by its hash.

  Try: “Create a shared step "Log in as admin".”

  Write · qase_shared_step_upsert

• Deletes a shared step

  Deletes one shared step by its hash, after asking you to confirm.

  Try: “Delete the shared step "Log in as admin".”

  Delete · qase_shared_step_delete

• Creates or updates a test environment

  Creates an environment with a slug and host, or updates one by ID.

  Try: “Create a staging environment at staging.example.com.”

  Write · qase_environment_upsert

• Deletes a test environment

  Deletes one environment by project code and ID, after asking you to confirm.

  Try: “Delete environment 2 in DEMO.”

  Delete · qase_environment_delete

• Uploads files and returns their hashes

  Uploads up to 20 files (32 MB each) and returns hashes that other tools accept in attachment fields. Local servers can read a file path; the hosted server takes base64 content.

  Try: “Upload screenshot.png and attach it to defect 8.”

  Write · qase_attachment_upload

• Deletes an attachment

  Deletes one attachment by its hash, after asking you to confirm.

  Try: “Delete attachment abc123.”

  Delete · qase_attachment_delete

• Links or unlinks cases and runs to Jira issues

  Attaches test cases or runs to Jira Cloud or Jira Server issues, or detaches them. A run can have only one link, and a new one replaces the old.

  Try: “Link case 17 to Jira issue PROJ-1234.”

  Delete · qase_external_issue_link

• Proposes a new case or a change for review

  Opens a review for a new case, or for edits to an existing one, and can assign reviewers. Approving and merging are only possible in the Qase web app.

  Try: “Open a review for the new login case and assign Dana.”

  Write · qase_review_create

• Changes a review proposal or its reviewers

  Edits the proposal, reassigns reviewers, or both. Changing the proposal resets approvals already given.

  Try: “Add Sam as a reviewer on review 9.”

  Write · qase_review_update

• Lists reviews

  Lists reviews filtered by status, type, case, author or reviewer, with per-reviewer approval status.

  Try: “List open reviews in DEMO.”

  Read · qase_review_list

• Deletes a review

  Removes a review proposal. It does not decline it, and merged reviews cannot be deleted.

  Try: “Delete review 9.”

  Delete · qase_review_delete

• Opens several reviews at once

  Opens many reviews in one request. One invalid item rejects the whole batch.

  Try: “Open reviews for these five new cases.”

  Write · qase_review_bulk_create

• Reports a whole CI run in one call

  Creates a run, records all results (up to 2000, split automatically) and by default completes the run.

  Try: “Report these CI results for DEMO: case 1 passed, case 2 failed.”

  Write · qase_ci_report

• Sets up a regression run in one call

  Creates a run and adds cases chosen by suite IDs, case IDs or a plan.

  Try: “Create a regression run from the Checkout and Login suites.”

  Write · qase_regression_run

• Creates a defect from a test failure

  Creates a defect from a failure. Title, actual result and severity are required, and failing results are described in the text.

  Try: “Create a critical defect for the login timeout in run 42.”

  Write · qase_triage_defect

• Calls any Qase REST endpoint

  Sends a GET, POST, PUT, PATCH or DELETE to a /v1/ path for things no other tool covers. A DELETE asks you to confirm.

  Try: “Call GET /v1/project/DEMO/run.”

  Delete · qase_api

• Searches the tool list by task

  Finds the right tool by what you want to do, by name or category.

  Try: “Which tool creates a milestone?”

  Read · qase_discover_tools

• Shows the full docs for one tool

  Returns the argument details, limits and warnings for a named tool before it is used.

  Try: “Show help for qase_run_upsert.”

  Read · qase_tool_help

• Creates or updates a custom field

  Creates a workspace-wide custom field for cases, runs or defects, or updates one. The entity and type cannot change after creation.

  Try: “Create a "Browser" dropdown field for cases.”

  Write · qase_custom_field_upsert

• Deletes a custom field everywhere

  Deletes a field from every project, with the values entered in it. It cannot be undone and asks you to confirm.

  Try: “Delete the "Browser" custom field.”

  Delete · qase_custom_field_delete

• Creates a new project

  Creates a project with a unique code of 2 to 10 characters. Title, code and access cannot be changed through the API afterwards.

  Try: “Create a project SMOKE_01 called "Smoke tests".”

  Write · qase_project_create

• Deletes a whole project

  Deletes a project with every case, suite, run, result, defect and milestone in it. It cannot be undone and asks you to confirm.

  Try: “Delete project SMOKE_01.”

  Delete · qase_project_delete

Watch out for

• It can delete cases, runs and whole projects

  Thirteen tools delete data, and qase_project_delete removes a project with every case, run and result, with no trash. The docs say each delete asks you to confirm first, so read each prompt before approving. github.com

• qase_api can call any Qase endpoint

  This tool sends any method to any /v1/ path, so it reaches things the dedicated tools do not. A DELETE through it asks for confirmation like the other delete tools. github.com

• The local token has full access to your account

  The self-run server uses one Qase API token for every call. Use a token from an account that can only reach the projects you want the assistant to touch. github.com

• Hosted server needs a paid plan

  The hosted server rejects tool calls on the Free plan. Run the server yourself with an API token on Free, or on a dedicated instance. github.com

• Local file upload reads files from your machine

  On a local server, qase_attachment_upload can take a file path and send that file to Qase. The hosted server takes base64 content only. github.com

Security advisories