mcpbeat Sign in

Qase Test Management MCP Server

by qase Your server? Claim it
answering

Qase Test Management is answering right now. Last checked 10 min ago. 3 791 installs a week from npm. Last commit 17 Sep 2026.

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

Installs per day peak 3 141 · avg 901 · -30% w/w
a month agotoday
Uptime history 47 days of history · worst day 87%
47 days agonow
96.7%
Uptime 24h
88 of 91 checks
—
Tools
hidden behind auth
506 ms
Response time
average over 24h
3 791
Installs / week
npm and PyPI

Qase Test Management does not always answer

Over the last week it answered 96.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 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 one needs environment variables set before it will start: QASE_API_TOKEN (Qase API token from app.qase.io > Settings > API Tokens), QASE_API_DOMAIN (Custom API domain for enterprise (default: api.qase.io)), QASE_API_PROTOCOL (Scheme used to reach the API domain: http or https. Use http only for self-hosted deployments served without TLS (default: https)). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.qase.io/mcp streamable-http sign-in 483 ms 10 min ago

Alternatives to Qase Test Management

same job, measured the same way
Testiny Test Management
by testiny

An MCP server that provides access to Testiny projects, test cases and test runs

answering
Qatouch
by qatouch

MCP Server for software testing, test case management, test execution, and defect tracking.

113 installs/wk local only
Apidog Tests MCP
by acabala

MCP server for managing Apidog test cases, scenarios, suites, and test data

41 installs/wk local only
Qtm4j MCP Server
by salehrifai42

MCP server for QMetry Test Management for Jira (QTM4J): test cases, cycles, executions, plans.

45 installs/wk local only
Tasks Example
by alpic-tasks-example-ca49f0f6

A test MCP server for task management

2 tools answering
QTM4J
by denis-platonov

MCP server for QMetry Test Management for Jira (QTM4J) Open API.

26 installs/wk local only
Test Case Generator AI MCP
by csoai-org

AI-powered test case generator ai MCP server for agents. Supports generate test cases, generate

167 installs/wk local only
Testkube MCP
by kubeshop

MCP server for Testkube - Manage test workflows, executions, and artifacts via AI assistants

local only

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: 96.7% 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 88 of 91 checks got a reply (96.7%), average response time 506 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 sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Qase Test Management?
No API key is involved. Qase Test Management answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Qase Test Management?
It answers our handshake in 506 ms on average, which is faster than 28% of all working MCP servers we measure. 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 3 791 times in the last week. Week over week that is -30%. 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, 32 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.