API & MCP
How Qualflare's API and MCP server authenticate: project access tokens, connecting an AI coding agent, and the MCP server's tools and permissions.
Last updated
Qualflare's API and MCP server authenticate with a project access token: one token gives the qf CLI, a script or an AI coding agent access to one project, and a new token starts with qfp_.
Access Tokens
Create, use and revoke project access tokens, and decide when a token needs Allow writes.
Connect a coding agent (MCP)
Connect Claude Code, Cursor or any MCP client to a Qualflare project with an access token.
MCP server reference
The endpoint, the permissions and all 17 read and 8 write tools an AI coding agent can call.
Related
- CLI Configuration: save a token under an identifier with
qf login. - CI/CD Integration: store the token as a CI secret.
Webhooks
Set up Qualflare project webhooks to get a signed HTTP POST when test results are uploaded or a defect is created, with payloads, headers and retries.
Access Tokens
Create, use and revoke Qualflare project access tokens (qfp_), the API keys of the qf CLI, scripts and MCP agents. New tokens expire after at most 90 days.