The Qase MCP Server connects AI assistants: Claude, Cursor, Codex, and any other MCP-compatible client, directly to your Qase workspace.

Using natural-language prompts, your AI tool can read and write test cases, runs, results, defects, suites, milestones, environments, and more, with no custom integration code.

It also supports QQL (Qase Query Language) for advanced searches across cases, runs, results, defects, and plans.

ℹ️ Official repository and full documentation: github.com/qase-tms/qase-mcp-server

Two ways to connect

Option	Best for	What you need
Hosted MCP(recommended)	Enterprise plan users who want zero setup	Just your Qase login (OAuth) – no install, no API token
Self-run	All other plans, or local/custom setups	Node.js + your own Qase API token

Option 1: Hosted Qase MCP (recommended)

The fastest way to get started. Connect to the Qase-hosted server at https://mcp.qase.io/mcp and sign in with your Qase account — no installation and no API token required. The client handles the OAuth flow for you.

Note: The hosted Qase MCP is available on the Enterprise plan. On other plans, use Option 2: Self-run below.

Claude

Qase publishes an official Qase Test Management connector in Claude's directory.

In Claude, open Settings → Connectors and find Qase Test Management.
Click Connect and complete the Qase sign-in when prompted.

❗ we're updating the official Claude connector. In the meantime, here are the instructions to create a custom connector.

Cursor

Add the server by URL in ~/.cursor/mcp.json (global) or .cursor/mcp.json(project). Cursor opens your browser to sign in; the tools appear once you authorize.

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

Codex

ChatGPT / Codex app: open Settings → MCPs → Add server, enter https://mcp.qase.io/mcp, and click Authenticate.

Codex CLI: add to ~/.codex/config.toml, then run codex mcp login qase and sign in via your browser.

[mcp_servers.qase] url = "https://mcp.qase.io/mcp" auth = "oauth"

Tip: Enter the URL exactly as shown, without surrounding quotes. A stray quote (or its encoded form %22) in the URL breaks OAuth. If a connection fails to authenticate, remove the server entry and re-add it, typing the URL by hand.

Any MCP client that supports remote servers with OAuth 2.1 connects the same way — just point it at https://mcp.qase.io/mcp.

Full per-client steps: docs/connect.md.

Active workspace

The connector operates on the workspace currently selected in your Qase UI. To work in a different workspace, just switch it in Qase, subsequent requests route to the new workspace automatically, with no need to reconnect or re-authorize.

Option 2: Run it yourself

Install the package and provide your own API token:

npm install -g @qase/mcp-server export QASE_API_TOKEN=your_api_token_here

Then point your MCP client's stdio config at the @qase/mcp-server binary.

Full install options, client configs (Claude Desktop, Cursor, Claude Code, Codex, OpenCode), environment variables, and transports (stdio / SSE / streamable-HTTP) are at docs/self-run.md.

What you can do with it

Once connected, ask your AI assistant to work with Qase in plain language. A few examples:

Task	Example prompt
Bootstrap project context	"Show me the structure of project DEMO — suites, milestones, environments."
Create or update a test case	"Create a high-priority smoke test case in project DEMO titled 'Login with valid credentials'."
Report CI results	"Report these CI results for project DEMO: case 1 passed, case 2 failed with 'timeout error'."
Triage a failed test	"Create a critical defect for the login timeout failure in run #42."
Search with QQL	"Find all failed test results from the last 7 days in project DEMO."

Tools

v2 ships 30 tools (29 task-oriented, plus qase_discover_tools for activating secondary tools on demand), consolidated from v1's 83 tools for lower token usage and better accuracy. Secondary tools stay hidden until needed, keeping the default list small.

Group	Count	Description
Read	2	Fetch any entity by type/ID, or bootstrap full project context in one call
QQL	2	Search cases, runs, results, defects, and plans with Qase Query Language
Write	21	Create, update, and delete cases, runs, results, defects, suites, milestones, plans, shared steps, environments, and attachments
Composite	3	Multi-step workflows in one call: CI reporting, defect triage, regression run setup
Escape hatch	1	Direct REST API access for any endpoint not covered above
Meta	1	`qase_discover_tools` — find and activate secondary tools on demand

Full tool-by-tool reference with parameters: docs/tools.md.

Upgrading from v1

v2 renames tools and changes response shapes as part of consolidating the 83 v1 tools into 29. If you're moving from v1, follow the complete tool-mapping table and before/after examples in the migration guide: MIGRATION.md.

Troubleshooting & support

Connector not appearing, empty tool list, or OAuth failing? See docs/troubleshooting.md.
Report issues: GitHub Issues, via our live-chat, or at [email protected]