What it does

Reads and writes Qase test cases, suites, and runs. The realistic use is turning a bug fix into a regression case in the same session, which is exactly the step people skip. Watch for case sprawl — an agent will happily create forty near-duplicate tests.

Install

Terminal

npx -y @qase/mcp-server

Client configuration

Paste this into your MCP client config (Claude Desktop, Cursor, or any client that reads mcpServers), then restart the client.

mcp.json

{
  "mcpServers": {
    "qase": {
      "command": "npx",
      "args": [
        "-y",
        "@qase/mcp-server"
      ]
    }
  }
}

Use it for

Creating and updating test cases while fixing a bug

Skip it if

Replacing a QA process; agents write plausible cases, not coverage

When to use it

Reach for this when the task needs testing inside the agent loop. Skip it if a plain shell command or a one-off script is enough — every server you add costs context and adds a failure mode.

Other TypeScript servers

Filesystem — Gives an agent scoped read, write, and search access to directories you explicitly allow
Memory — A persistent knowledge graph stored in a local JSON file, exposed through entities, relations, and observations
Sequential Thinking — Gives the model a scratchpad for structured, revisable reasoning: numbered thoughts that can branch, revise, and conclude

Qase MCP