Qase MCP Server
OfficialThe Qase MCP Server connects AI assistants to the Qase Test Management Platform, enabling full read/write access to test-related entities via the Model Context Protocol. Here's what you can do:
Project Management — List, get, create, and delete projects; grant/revoke access for users or groups.
Test Cases — List, get, create, update, delete, and bulk-create test cases; attach/detach external issues (e.g., Jira).
Test Suites — List, get, create, update, and delete test suites, including nested suites via parent ID.
Test Runs — List, get, create, delete, and complete (close) test runs; manage public shareable links.
Test Results — List, get, create, update, delete, and bulk-create test results.
Test Plans — List, get, create, update, and delete test plans.
Shared Steps — List, get, create, update, and delete reusable shared steps.
Shared Parameters — List and get shared parameters.
Milestones — List, get, create, update, and delete milestones for organizing tests by release or sprint.
Defects — List, get, create, update, delete, and resolve defects; update defect status (open, in_progress, resolved, invalid).
Environments — List, get, create, update, and delete test environments (e.g., staging, production).
Attachments — List, get, upload (base64), and delete attachments.
Custom & System Fields — List, get, create, update, and delete custom field definitions; list built-in system fields.
Configurations — List configuration groups and items; create and delete configuration groups.
Users & Authors — List/get workspace users and test case authors.
QQL (Qase Query Language) — Search across cases, runs, results, defects, and plans using powerful QQL queries; get syntax help and examples.
Tool Discovery — Use qase_discover_tools to find and activate secondary tools on demand.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Qase MCP Serverlist test cases in project 'Mobile App'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Qase MCP Server
Official Model Context Protocol (MCP) server for Qase Test Management Platform — connect AI assistants to your test cases, runs, defects, and more.
Table of Contents
Related MCP server: TestRail MCP Server
Overview
The Qase MCP Server lets AI assistants (Claude, Cursor, Codex, and any other MCP client) read and write Qase test cases, runs, results, defects, suites, milestones, and more — through a standardized protocol, with no custom integration code.
Features:
29 task-oriented tools (30 total, including
qase_discover_tools) — consolidated from 83 v1 tools for lower token usage and better LLM accuracyComposite tools — multi-step workflows in a single call: CI reporting, defect triage, regression run setup
QQL support — Qase Query Language for advanced searches across cases, runs, results, defects, and plans
Project context bootstrap — one call returns full project structure (suites, milestones, environments, users, custom fields)
Tool discovery — secondary tools stay hidden until needed, keeping the default tool list small
Hosted or self-run — connect to
https://mcp.qase.io/mcpwith just your Qase login, or run the server locally with your own API tokenTenant-safe caching & HTTP resilience — two-tier cache (in-memory + optional Redis), connection pooling, retry with backoff
Escape hatch — direct REST API access for any endpoint via
qase_api
Use Cases
Scenario | Example prompt | Tool |
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" |
|
See Tools and docs/tools.md for the full reference.
Quick Start
Use the hosted Qase MCP (recommended)
No install, no API token — connect to the Qase-hosted server and sign in with your Qase account.
Note: The hosted Qase MCP is available on the Enterprise plan in Qase. On other plans, run the server yourself with your own API token.
Claude — open Settings → Connectors, find Qase Test Management, click Connect.
Cursor — add
{"mcpServers": {"qase": {"url": "https://mcp.qase.io/mcp"}}}to.cursor/mcp.json.Codex — add the URL
https://mcp.qase.io/mcpin Settings → MCPs → Add server, or configure~/.codex/config.tomlfor the CLI.VS Code — add
{"servers": {"qase": {"type": "http", "url": "https://mcp.qase.io/mcp"}}}to.vscode/mcp.json, or run MCP: Add Server.
Full per-client steps, other clients, and the active-workspace model: docs/connect.md.
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_hereThen 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): docs/self-run.md.
Upgrading from v1
v2 consolidates 83 v1 tools into 29 task-oriented tools (30 total, including a discovery tool). Tool names and response shapes have changed. See MIGRATION.md for the complete tool mapping table, response format changes, and before/after examples.
Tools
30 tools across 6 groups (29 task-oriented tools plus qase_discover_tools for on-demand activation of secondary tools):
Group | Count | Description |
Read | 2 | Fetch any entity by type/ID, or bootstrap full project context in one call |
QQL | 2 | Search across 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 by the tools above |
Meta | 1 |
|
Full tool-by-tool reference with parameters and the discovery model: docs/tools.md.
Documentation
docs/connect.md — connect to the hosted Qase MCP (Claude, Cursor, Codex, other clients)
docs/self-run.md — install and run the server yourself (config, clients, transports)
docs/tools.md — full tool reference, groups, and the discovery model
docs/troubleshooting.md — auth, OAuth/connector, and SSL issues
MIGRATION.md — v1 → v2 tool mapping and migration guide
Contributing
Contributions are welcome! See CONTRIBUTING.md for development setup, testing, and linting guidelines.
License
MIT License — see LICENSE for details.
Support
Documentation: https://docs.qase.io/en/articles/14984302-qase-mcp-server
Email: support@qase.io
GitHub Issues: https://github.com/qase-tms/qase-mcp-server/issues
Links
Qase Platform: https://qase.io
Qase Documentation: https://help.qase.io
API Documentation: https://developers.qase.io
MCP Protocol: https://modelcontextprotocol.io
Issue Tracker: https://github.com/qase-tms/qase-mcp-server/issues
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/qase-tms/qase-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server