# API & MCP

Source: https://docs.qualflare.com/docs/api · Last updated: 2026-10-27

How Qualflare's API and MCP server authenticate: project access tokens, connecting an AI coding agent, and the MCP server's tools and permissions.

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](https://docs.qualflare.com/docs/api/access-tokens): Create, use and revoke project access tokens, and decide when a token needs Allow writes.
- [Connect a coding agent (MCP)](https://docs.qualflare.com/docs/api/mcp): Connect Claude Code, Cursor or any MCP client to a Qualflare project with an access token.
- [MCP server reference](https://docs.qualflare.com/docs/api/mcp-reference): The endpoint, the permissions and all 17 read and 8 write tools an AI coding agent can call.

## Related

* [CLI Configuration](https://docs.qualflare.com/docs/cli/configuration): save a token under an identifier with `qf login`.
* [CI/CD Integration](https://docs.qualflare.com/docs/cli/ci-cd): store the token as a CI secret.