MCP Server
The Qualflare MCP server — endpoint, authentication, permissions, and every tool an AI coding agent can call.
MCP Server
Qualflare exposes its public API over MCP at
https://api.qualflare.com/mcp, so an AI coding agent can work with your test data
directly. For setup instructions see
Connect a coding agent.
| Endpoint | https://api.qualflare.com/mcp |
| Transport | Streamable HTTP, stateless |
| Authentication | Authorization: Bearer <access token> |
| Project | Chosen by the token — no project argument exists on any tool |
Authentication and permissions
The MCP server takes the same access token as the CLI and the REST API, and applies the same rules. There is no MCP-specific key and no scope picker: what a token may do is decided by the current project role of the person who created it.
| Action | Requires |
|---|---|
| Any read tool | Creator is a Viewer or above |
| Any write tool | Creator is an Editor or above |
The role is resolved per request, so a demotion takes effect immediately on tokens that person created.
No tool accepts a workspace, project or user ID. Those come from the token, which is what keeps one project's agent out of another's data.
Read tools
| Tool | Returns |
|---|---|
list_test_suites | Test suites in the project, with paging and filters |
get_test_suite | One suite by its sequence number |
list_suite_cases | Test cases in a suite |
get_test_case | One test case |
list_case_steps | The steps of a test case |
list_launches | Test runs, newest first, with filters |
get_launch | One launch and its result counts |
list_defects | Defects, filterable by severity, status and environment |
get_defect | One defect |
list_milestones | Milestones |
get_milestone | One milestone |
list_test_plans | Test plans |
get_test_plan | One test plan |
list_test_plan_cases | The cases in a test plan |
list_failure_clusters | AI-grouped failure clusters |
get_failure_cluster | One cluster and its failures |
Write tools
All six are additive or partial updates. Nothing deletes.
| Tool | Does |
|---|---|
create_test_case | Adds a case to a suite, in draft state |
update_test_case | Changes a case's name, description, state or priority |
create_case_step | Adds a step to a case |
update_case_step | Changes a step's instruction, type or data |
create_defect | Files a defect |
update_defect | Changes a defect's fields, including its status |
Creating test cases counts against your plan's test-case limit, the same as creating them in the app. When the limit is reached the tool fails and nothing is created.
A tool call is not idempotent. If an agent retries a create_* call that already succeeded,
you get a second record — worth knowing if you ask an agent to create many cases at once.
Notes for client authors
- Tool results are returned as structured content with a JSON text fallback, so clients on older MCP revisions can still read them.
- Two list tools —
list_case_stepsandlist_test_plan_cases— wrap their results as{"items": [...]}rather than returning a bare array, because not every client accepts a top-level array. - Asking for something that does not exist returns a tool error saying so, not an empty success.
- Tool names are stable. They are frozen in the API's test suite, so an existing client will not break because a tool was renamed.
Claude Code Plugin Reference
Full reference for the Qualflare Claude Code plugin — slash commands, Stop hook behavior, state files, config fields, authentication, and supported frameworks.
Teams
Reference for Qualflare's project-level Teams feature. Manage teams, assign members, and filter test suites and defects by team responsibility.