Qase Test Management MCP Server

Official MCP server for Qase - manage test cases, runs, suites, defects via AI tools.

People connecting this server to Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-08-21 · ★ 31 · #21 OF 848 MAINTAINED OTHER · VERIFIED 2026-08-25

MIT · TypeScript servers · how we verify → /methodology

01 · Install Qase Test Management

before you install - you'll need

Set QASE_API_TOKEN before connecting. QASE_MCP_INTEGRATION is optional or environment-specific per the README.

Claude Code

claude mcp add qase-tms-qase-mcp-server --transport http https://mcp.qase.io/mcp

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "qase-tms-qase-mcp-server": {
      "url": "https://mcp.qase.io/mcp"
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

https://mcp.qase.io/mcp

transport: streamable-http

endpoint alive - authentication required · probed 2026-08-25

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions · remote - your agent's requests go to mcp.qase.io

endpoint auth requires authentication - rejected our unauthenticated MCP initialize

license MIT - declared in the repository

npm package @qase/mcp-server - the @qase scope differs from the repo owner (qase-tms); confirm it's the project's official package

registry vendor namespace io.qase - domain-verified with the official MCP registry

03 · What Qase Test Management can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v2.2.2 · 2026-08-19

state that the hosted connector serves the main cloud only · use the api-<cluster>.qase.io form for dedicated instances · forward a client-supplied integration marker to the Qase API

v2.2.1 · 2026-08-18

allow overriding the API scheme via QASE_API_PROTOCOL (v2.2.1)

v2.2.0 · 2026-08-17

test case reviews, and make attachment upload reachable (v2.2.0)

04 · Who maintains Qase Test Management

Qase Test Management is maintained by qase-tms. It's the only MCP server we track from this author; the repo dates to Sep 2025.

05 · Facts

category
other - ranked #21 of 848 actively-maintained other servers as of 2026-08-25.
release cadence
10+ releases in the last 90 days (latest 2026-08-19)
registry
io.qase/mcp-server (active, first published 2026-03-17 · 16 versions)
packages
npm:@qase/mcp-server

06 · Qase Test Management FAQ

What is Qase Test Management?

Official MCP server for Qase - manage test cases, runs, suites, defects via AI tools.

Is Qase Test Management still maintained?

Yes - as of 2026-08-25, its last commit was 2026-08-21 and it shipped 10+ releases in the last 90 days. We re-verify nightly.

How do I install Qase Test Management?

Run `npx -y @qase/mcp-server`. The README documents 2 environment variables (QASE_API_TOKEN, QASE_MCP_INTEGRATION) to set first. Set QASE_API_TOKEN before connecting. QASE_MCP_INTEGRATION is optional or environment-specific per the README. You can also paste the ready-made client config above.

Does Qase Test Management require authentication?

Yes - when we probed the endpoint on 2026-08-25, it rejected an unauthenticated MCP initialize; you'll need credentials to connect.

07 · Alternatives to Qase Test Management