Does Qase have an MCP server?

Yes Official

Qase maintains an official MCP server.

The hosted endpoint is Enterprise-plan only; other plans run the npm package with an API token.

Verified 2026-09-29 against vendor docs
Access
Remote server
Endpoint
https://mcp.qase.io/mcp
Maintainer
Qase TMS
License
MIT
Language
TypeScript
Stars
32
Last commit
today
What it does
An official Qase MCP server
— how qase-tms/qase-mcp-server describes itself
The receipts
Vendor-hosted https://mcp.qase.io/mcp

A remote server run by Qase itself — nothing to install. Documented at docs.qase.io.

Official package @qase/mcp-server

Published on npm. The package page carries the exact launch arguments and required credentials.

Official repository qase-tms/qase-mcp-server

An official Qase MCP server

★ 32 pushed 2026-09-29 MIT Active
Connect it

Hosted by the vendor — no install, connect over HTTP with OAuth or a token.

Add it from the terminal, then restart your session:

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

Add --scope user to make it available in every project.

Setup sponsor · open Put your product right here, under the setup steps of all 645 verdict pages. One sponsor at a time. $149 first month, then $399/mo →
Questions
Does Qase have an official MCP server?

Yes. Qase maintains an official MCP server, hosted at https://mcp.qase.io/mcp, distributed as @qase/mcp-server on npm. The source lives at qase-tms/qase-mcp-server on GitHub.

How do I connect Qase to Claude?

Add https://mcp.qase.io/mcp as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http qase https://mcp.qase.io/mcp" in Claude Code.

Do I need to install anything to use the Qase MCP server?

No. It is a remote server hosted by Qase, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.

How is this verdict verified?

Published to the MCP Registry under Qase's verified namespace io.qase; the hosted endpoint mcp.qase.io/mcp answers MCP initialize (401) and is documented at docs.qase.io, with source in the qase-tms/qase-mcp-server repo and the @qase/mcp-server npm package published by the qaseio account. GitHub metadata is refreshed every six hours.

How we know

Published to the MCP Registry under Qase's verified namespace io.qase; the hosted endpoint mcp.qase.io/mcp answers MCP initialize (401) and is documented at docs.qase.io, with source in the qase-tms/qase-mcp-server repo and the @qase/mcp-server npm package published by the qaseio account.

  • github data refreshed 2026-09-29, then every 6 hours
  • vendor docs verified on 2026-09-29

Spotted something out of date? Tell us — corrections ship same-day.

Also in Developer Tools

See all Developer Tools servers →