mcpbeat

Qase Test Management MCP Server

io.qase/mcp-server
answering

Qase Test Management is answering right now. Last checked 14 min ago. 2 838 installs a week from npm. Last commit 29 Jul 2026.

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

Installs per day peak 1 355 · avg 333 · -15% w/w
a month agotoday
Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
483 ms
Response time
average over 24h
2 838
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add mcp-server --transport http https://mcp.qase.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.qase.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-server]
url = "https://mcp.qase.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.qase.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.qase.io/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.qase.io/mcp streamable-http needs key 458 ms 14 min ago

Qase Test Management — questions

Answers built from our own checks of this server.

Why is there no tool list for Qase Test Management?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Qase Test Management working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 483 ms. The bar chart above shows every period we have measured.
How do I connect Qase Test Management?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Qase Test Management need an API key?
Yes. Every time we knock, Qase Test Management answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Qase Test Management?
It answers our handshake in 483 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Qase Test Management?
The npm package @qase/mcp-server was installed 2 838 times in the last week. Week over week that is -15%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Qase Test Management open source?
Yes — it is published under the MIT licence, written in TypeScript, 31 stars on GitHub and 6 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.