Qase MCP server

What the model can do

Qase test management: projects with case, run and defect counts, test cases by suite, milestone, severity, priority or status, test runs with pass and fail counts, individual test results, defects, milestones and test plans; when you ask, can create, edit or delete test cases, start, complete or delete runs, record results, file, edit, resolve, re-status or delete defects, and create milestones, suites and plans.

Reads

• qase_list_projectsQase projects the token can see: title, code (used by every other Qase tool) and counts of cases, suites, milestones, runs (active) and defects…
• qase_list_casesTest cases in a Qase project, filtered by title search, suite, milestone, severity, priority, status or automation: id, title, status, severity…
• qase_list_runsTest runs in a Qase project, newest as Qase orders them: id, title, status (in progress, passed, failed, aborted), start and end times…
• qase_list_resultsIndividual test results in a Qase project: result hash, run, case, status, when it ended and how long it took.
• qase_list_defectsDefects in a Qase project: id, title, status (open, in progress, resolved, invalid), severity, actual result, milestone, runs it was found in…
• qase_list_milestonesMilestones in a Qase project: id, title, status (active or completed), due date and description.
• qase_list_plansTest plans in a Qase project: id, title, how many cases each holds, and dates.

Acts, when you ask

These change something in Qase. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• qase_create_caseCreates a test case in a Qase project's repository, visible to everyone on the project; nobody is notified.
• qase_update_caseEdits a Qase test case; only the fields passed change, and steps passed replace all of its steps.
• qase_delete_casePermanently deletes a test case from a Qase project's repository.
• qase_create_runStarts a test run in a Qase project, of the cases you list, a plan's cases, or every case in the project (include_all_cases).
• qase_complete_runCompletes a Qase test run, fixing its outcome as passed or failed; the API cannot re-open it.
• qase_delete_runPermanently deletes a Qase test run and every result recorded in it.
• qase_add_resultRecords a test result for a case in a Qase run (passed, failed, blocked, skipped, invalid, or a custom status slug)…
• qase_create_defectFiles a defect in a Qase project with a title, the actual result and a severity, visible to the project team; nobody is notified.
• qase_update_defectEdits a Qase defect's title, actual result, severity, milestone or tags; only the fields passed change.
• qase_resolve_defectMarks a Qase defect resolved; project webhooks (defect.resolved) fire.
• qase_set_defect_statusSets a Qase defect's status to in_progress, resolved or invalid.
• qase_delete_defectPermanently deletes a Qase defect.
• qase_create_milestoneCreates a milestone in a Qase project, optionally with a due date.
• qase_create_suiteCreates a test suite (a folder of cases) in a Qase project, at the top level or inside parent_id.
• qase_create_planCreates a test plan in a Qase project holding the cases you list, for starting runs of them later.

Connect it

First connect Qase on Dashboard → Connections, then add Memtro to your client once. The Qase tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Qase connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which runs failed this week?
• › Which defects are still open on the mobile project?
• › Which critical test cases are in the checkout suite?
• › Which cases are in the release test plan?
• › Which milestones are due this month?

Questions

Is this an official Qase MCP server?

No. It is Memtro's MCP server with Memtro's Qase connector behind it: the connector reads Qase through its API with the credentials you connect on Dashboard → Connections, and Qase publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Qase?

Only when you ask, and only what it has been granted: create a test case; edit a test case; delete a test case; start a test run; complete a test run; delete a test run and its results; record a test result in a run; file a defect; edit a defect; resolve a defect; set a defect to in progress, resolved or invalid; delete a defect; create a milestone; create a test suite; create a test plan. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server