Qase MCP Server
Official Qase MCP server with 42 tools: cases, runs, defects, CI reports and search in the QQL query language
- 37 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The tools create, change and delete cases, runs and defects in your Qase project
- The token reaches every project in the account, and direct REST access through `qase_api` goes around the limits of the ready-made tools
Install
- Works in
Manual install
{"mcpServers":{"qase":{"command":"npx","args":["-y","@qase/mcp-server"],"env":{"QASE_API_TOKEN":"your_api_token_here"}}}}Local run with your API token, works on any plan.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The tools create, change and delete cases, runs and defects in your Qase project
- The token reaches every project in the account, and direct REST access through `qase_api` goes around the limits of the ready-made tools
This is third-party code. Review the repository files before installing.
What it does
Qase is a test management platform. The server in this repository opens it to an agent over MCP: the agent sees and changes test cases, runs, results, defects, suites, milestones and plans, and links cases and runs to Jira issues. There are 42 tools: 40 task tools and two meta tools. `qase_discover_tools` finds the right tool from a task description, and `qase_tool_help` returns one tool's full documentation when the agent reaches for it. Three composite workflows are included: a CI results report, triage of a failed test with defect creation and regression run setup. `qase_project_context` returns the project structure in one call, and `qql_search` searches through Qase Query Language, QQL. Everything else is reachable through direct REST access with `qase_api`. There are two ways to run it. The hosted server at https://mcp.qase.io/mcp (https://mcp-eu.qase.io/mcp for the EU cluster) works on paid plans and signs in with your Qase account. Running locally with npx -y @qase/mcp-server uses your API token and works on any plan, Free included.
Who it is for. Testers and QA engineers who keep cases and runs in Qase and want an agent to handle routine work: creating cases, CI reports, failure triage.
Good fit when
- After a CI run the results must go into Qase: the agent calls `qase_ci_report`
- A test failed on a timeout and you need a defect tied to run 42
- A project needs up to a hundred test cases created at once from a feature description
- You want a query like "all failed results from the last week" through the QQL query language
- You are preparing a regression run and want to assemble it from existing cases
Not a fit when
- Tests live in another system: the server works only with Qase
- The agent must not be trusted with writes: the server has change and delete tools, and token permissions set the limits
- You need to approve and merge case changes: the README says approving and merging stay in the UI
Example request
Show the structure of project DEMO and create a high-priority test case titled "Login with valid credentials" in the authorization suite.MCP
- Transport
- stdio, http
- Authentication
- OAuth
Environment variables
QASE_API_TOKENsecret- Qase API token for the local run
Limitations
You need a Qase account. The hosted server is available on all paid plans; on the Free plan and on dedicated installations use a local run with your own API token and Node.js 20 or newer. The EU cluster has its own address and region settings.
Version 3.0.0 moved to the MCP 2026-07-28 protocol with no sessions, while tool names and arguments stayed the same. Moving from the first version affects names and response shapes: the 83 earlier tools were consolidated into a shorter set. Some tools write and delete project data, and case proposals go to review.
How to disable. Disconnect Qase in the client settings (in Claude open Settings, then Connectors). For a local run remove the qase block from the configuration and revoke the API token at app.qase.io.
FAQ
How do I connect Qase to Claude Code, Cursor or Codex?
For Cursor add a qase block with the url https://mcp.qase.io/mcp to .cursor/mcp.json. For Codex put this address in the MCP settings or in ~/.codex/config.toml. In Claude open Settings, then Connectors, and connect Qase Test Management.
Does the server work on the Free plan?
The hosted server does not; it comes with every paid plan. On Free run the server locally with npx -y @qase/mcp-server and your API token in QASE_API_TOKEN.
What is QQL?
Qase Query Language, a query language for searching cases, runs, results, defects and plans. The `qql_search` tool accepts such queries, and the agent builds them from a plain sentence.
How do I report CI results to Qase?
The composite tool `qase_ci_report` takes results by project case and records them in a run in one call. The README example: case 1 passed, case 2 failed with a timeout message.
What are `qase_discover_tools` and `qase_tool_help` for?
All tools are visible from the first request with short descriptions. `qase_discover_tools` finds the right one by task, and `qase_tool_help` returns its full documentation when the agent gets to it. That saves context tokens.
Discussion
No questions or reviews yet.
Related
MCP serverskogiQA MCP gives an agent a browser that finds page elements without selectors, for debugging web apps and writing e2e tests
The official MCP server debugger: web UI, automation CLI and terminal UI in one package
The QASkills.sh directory MCP server: an agent searches, reads and installs testing skills without leaving the conversation.
SonarSource's official MCP server: quality and security issues, quality gates and code analysis from SonarQube Server and Cloud
The SmartBear server gives the agent BugSnag, Swagger, Zephyr, QMetry and PactFlow: errors, API specs, test cases and contracts
MCP Interviewer checks an MCP server before an agent connects: provider limits, tool tests and a Markdown report.
README in short
The README covers a feature overview, example prompts, connecting the hosted server and running locally, notes for integration authors, upgrading from versions 1 and 2 and tool groups. Details live in docs/connect.md, docs/self-run.md, docs/hosting.md and docs/tools.md.