Skip to main content
Use Qovery when you want a coding agent to deploy and operate apps on your own cloud account or Kubernetes cluster, but you do not want to hand it cloud admin credentials. Your cloud account is connected to Qovery once, by a human. The agent only receives a Qovery token, and that token can be limited to exactly what the agent needs, for example “deploy the staging environment, never delete anything”.

​
What the agent gets

The agent never needs AWS, GCP, or Azure credentials.

​
Prerequisites

A Qovery organization with a cluster on your cloud account. To create one, see Install Qovery on your cloud. The agent can also create the account itself with the qovery-signup skill, which authenticates with qovery auth --headless (the first login creates the account).
An organization Owner or Admin to create the API Policy Token. Custom roles cannot create one.
A coding agent that supports Agent Skills: Claude Code, Codex, Cursor, OpenCode, Gemini CLI, and others. See Compatible tools.

​
Steps

1

Install the Qovery Agent Skills and CLI

To install the skills for the current repository only, run curl -fsSL https://skill.qovery.com/install.sh | bash -s -- --project.
2

Create a scoped token for the agent

In a session authenticated as an organization Owner or Admin (qovery auth, or qovery auth --headless without a browser), ask the agent:
The qovery-policy-token skill turns this intent into an OPA/Rego policy, tests it locally and against the API, creates the token, and checks that it allows what you asked and denies everything else.
An API Policy Token authenticates as organization admin, and its policy is the only constraint: a policy that allows everything grants everything. Only allow the requests the agent needs. API Policy Tokens are in Preview; see Current limitations.
3

Give the token to the agent session

Set the token in the environment of the agent session. Do not paste it into the prompt.
The Qovery CLI, which the skills drive, reads QOVERY_CLI_ACCESS_TOKEN and sends it as Authorization: Token .... The policy also applies to the lookups the CLI makes to resolve organization, project, and environment names, so the policy must allow those reads.For read-only investigation from the same session, you can also add the MCP Server. It does not use the API Policy Token: give it an API token with a read-only role in the Authorization header. If you sign in to the MCP Server with OAuth instead, it acts with your own user permissions.
4

Restrict the commands the agent can run (optional)

The token is the guardrail that Qovery enforces. You can also restrict which qovery commands the agent runs without asking, with a permission file committed to the repository. See the Claude Code allowlist in Securing AI Agent Access.
5

Ask the agent to deploy

The agent picks qovery-deploy, qovery-preview, or qovery-troubleshoot from the prompt.

​
Check the result

  • The deployment reaches the DEPLOYED state. With the CLI, --watch exits with code 0 on success and 1 on failure:
  • A request outside the policy is refused with 401 Unauthorized. A denied request does not tell you which rule failed, so test the policy before you rely on it (the qovery-policy-token skill does this for you).
  • Changes the agent makes appear in the audit logs under the token name.

Qovery Agent Skills

All eleven skills and the prompts that trigger them.

API Policy Token (Preview)

Policy input contract, recipes, and limitations.

Securing AI Agent Access

Read-only MCP, CLI allowlist, and policy tokens compared.

Preview Environments

One environment per pull request, deleted when the PR closes.