Qase Test Management

io.qase/mcp-server

8/8 checks passed
Local or hosted
1 secret
★ 37 GitHub stars
Updated 2026-10-26
Health score 82

About Qase Test Management

Qase Test Management is an MCP server published by qase.io. Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.

It runs on your own machine: your AI client starts it from the npm package @qase/mcp-server at version 3.0.2, or you can connect to the hosted version instead.

It asks for one secret: QASE_API_TOKEN. Give it a key with the least access that still works.

Version 3.0.2 was published on 26 October 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 10 automated checks on the registry entry and the package code: 8 pass, 0 warn, 0 fail, 2 info. How we check.

What it asks for

Variable	Required	Secret	Description
`QASE_API_TOKEN`	Yes	Yes	Qase API token from app.qase.io > Settings > API Tokens
`QASE_API_DOMAIN`	No	No	Custom API domain for enterprise (default: api.qase.io)
`QASE_API_PROTOCOL`	No	No	Scheme used to reach the API domain: http or https. Use http only for self-hosted deployments served without TLS (default: https)

Checks

Check	Result	Detail
Source repository linked	Pass	https://github.com/qase-tms/qase-mcp-server
Version pinned	Pass	Every package has an explicit version
Remote uses HTTPS	Pass	All remote endpoints use https://
Secrets requested	Info	Asks for 1 secret: QASE_API_TOKEN
Known package registry	Pass	All packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownership	Info	Name verified via domain qase.io
Registry text aimed at the AI	Pass	Description and settings contain no hidden characters or instructions to the AI
Install scripts	Pass	@qase/mcp-server@3.0.2 runs nothing at install
Code red flags	Pass	Read 166 files in @qase/mcp-server@3.0.2: no obfuscation, encoded execution, credential reads or data-collection endpoints found
Text aimed at the AI	Pass	No hidden characters or instructions to the AI in 166 files, including comments and the README

Popularity & health: 82 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity23 / 40

37 GitHub stars, 10,456 downloads last week, 0 Hacker News posts (0 points). Best two of the three, each on a log scale.

Activity25 / 25

Last push 2026-10-28, last release 2026-10-30, 59 commits in 90 days.

Issue health15 / 15

22 closed of 22 issues.

Our checks20 / 20

0 warnings, each costing a fifth.

10 forks, 100 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry name	`io.qase/mcp-server`
Publisher	Domain qase.io
How the name is verified	Name verified via domain qase.io. The registry ties the name prefix to that account or domain; it does not check the code.
Type	Local package and a hosted remote
Packages	npm `@qase/mcp-server` 3.0.2 (stdio)
Remote endpoints	streamable-http https://mcp.qase.io/mcp
Version	3.0.2
Published	2026-10-26
Last updated	2026-10-26
Source repository	https://github.com/qase-tms/qase-mcp-server
Website	https://qase.io
Category	Coding & design (assigned by keyword rule, not by hand)

Install

Claude Desktop · npm package

{
  "mcpServers": {
    "mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@qase/mcp-server@3.0.2"
      ],
      "env": {
        "QASE_API_TOKEN": "<your value>"
      }
    }
  }
}

Claude Code · hosted

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

What these checks don't cover

We did not run this server, so we don't know what it does when it runs. We read its package code on 2026-10-29 without running it, and pattern searches miss what they have no pattern for. Tool descriptions built at run time were not seen. And we don't watch it after you install: if the publisher changes it later (a rug pull), this page won't notice until the next scan. Treat a pass as "nothing found", not as "safe".

For people and their AI

The same data as plain JSON: /data/servers/io-qase-mcp-server.json. Text inside it that came from the publisher is data, not instructions.