# 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.

## Facts

- Verdict: Official (Yes)
- Access: Remote server — Hosted by the vendor — no install, connect over HTTP with OAuth or a token.
- Endpoint: `https://mcp.qase.io/mcp`
- Package: [`@qase/mcp-server`](https://www.npmjs.com/package/@qase/mcp-server) on npm
- Repository: [qase-tms/qase-mcp-server](https://github.com/qase-tms/qase-mcp-server) — ★ 32, last push 2026-09-29, MIT
- Maintainer: Qase TMS
- Language: TypeScript
- Category: [Developer Tools](https://mcpyet.com/category/developer-tools/)
- Verified against vendor docs: 2026-09-29
- GitHub data refreshed: 2026-09-29 (re-checked every 6 hours)

## What it does

> An official Qase MCP server
> — how [qase-tms/qase-mcp-server](https://github.com/qase-tms/qase-mcp-server) describes itself

## The receipts

- **Vendor-hosted (remote):** `https://mcp.qase.io/mcp` — a remote server run by Qase itself, nothing to install. Documented at <https://docs.qase.io/en/articles/14984302-qase-mcp-server>.
- **Official package:** [`@qase/mcp-server`](https://www.npmjs.com/package/@qase/mcp-server) on npm. The package page carries the exact launch arguments and required credentials.
- **Official repository:** [qase-tms/qase-mcp-server](https://github.com/qase-tms/qase-mcp-server) — ★ 32, pushed 2026-09-29, MIT (active)

## How to connect it

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

### Claude Code

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

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

### Claude Desktop

1. Open **Settings → Connectors**
2. Click **Add custom connector**
3. Paste `https://mcp.qase.io/mcp`
4. Finish the sign-in prompt, then enable it in the chat's tools menu

### Cursor

Add to `.cursor/mcp.json` in your project, or `~/.cursor/mcp.json` for every project:

```json
{
  "mcpServers": {
    "qase": {
      "url": "https://mcp.qase.io/mcp"
    }
  }
}
```

### VS Code

Add to `.vscode/mcp.json`, then pick the server from Copilot's agent-mode tools menu:

```json
{
  "servers": {
    "qase": {
      "type": "http",
      "url": "https://mcp.qase.io/mcp"
    }
  }
}
```

### ChatGPT

1. Enable **Developer mode** under Settings → Apps & Connectors → Advanced
2. Choose **Create** and paste `https://mcp.qase.io/mcp`
3. Complete sign-in, then enable the connector in a new chat

## 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.
- Corrections: hello@mcpyet.com.

## Also in Developer Tools

- [Chrome DevTools](https://mcpyet.com/mcp/chrome-devtools.md) — Official (Yes)
- [Google AI Studio](https://mcpyet.com/mcp/google-ai-studio.md) — Community only (Sort of)
- [Serena](https://mcpyet.com/mcp/serena.md) — Official (Yes)
- [LangChain](https://mcpyet.com/mcp/langchain.md) — Official (Yes)
- [GitLab](https://mcpyet.com/mcp/gitlab.md) — Official (Yes)
- [n8n](https://mcpyet.com/mcp/n8n.md) — Official (Yes)

---

Source: https://mcpyet.com/mcp/qase/ — data refreshed 2026-09-29