Qovery
An MCP server for Qovery AI Copilot that enables deploying apps and managing Kubernetes on AWS, GCP, Azure, and On-Premise infrastructure with natural language
Documentation
MCP Server
Set up the Qovery MCP Server so Claude, ChatGPT, or another MCP-compatible client can manage your existing Qovery infrastructure in natural language.
Overview
The Qovery MCP Server lets you interact with your Qovery infrastructure from any MCP-compatible client (Claude, Claude Code, ChatGPT, etc.) using natural language.
[!NOTE]
What is MCP? The Model Context Protocol is an open standard developed by Anthropic that allows AI assistants to interact with external tools and systems. Learn more →
[!TIP]
Want to deploy a new application from source code? The MCP Server is for managing existing infrastructure. To deploy a new application from your codebase using an AI agent, install the Qovery Agent Skill instead — it works with Claude Code, Cursor, OpenCode, and 30+ AI coding tools. The skill and MCP Server complement each other: use the skill to deploy, then the MCP Server to manage.
Prerequisites
- MCP-Compatible Client: Any MCP-compatible application
- Qovery Account: Active account with infrastructure
Setup
The Qovery MCP Server is accessible at https://mcp.qovery.com/mcp. You can find this URL and manage your MCP access in the Console under Settings > MCP Server. Choose one of the two authentication methods below to connect your MCP client.
[tab] OAuth (recommended)
If your MCP client supports OAuth, this is the easiest option — no token generation required. The client will handle authentication automatically.
Example with Claude Code:
# Read-only (default) claude mcp add --transport http qovery https://mcp.qovery.com/mcp --callback-port 4242 # Read/write claude mcp add --transport http qovery "https://mcp.qovery.com/mcp?read_write=true" --callback-port 4242Refer to your MCP client's documentation for how to configure OAuth with a custom server URL.
[tab] API Token
If your MCP client doesn't support OAuth, generate a Qovery API token and send it in the
Authorizationheader. Never put a token in the MCP URL: URLs end up in client configuration files, shell history, and proxy logs.[!TIP]
Give an agent the least-privileged token that does the job, such as an API token with a read-only role. Avoid giving an agent a long-lived admin token. For agents that act through the CLI or the API, an API Policy Token (Preview) scopes access request by request.
Step 1 - Generate a token:
1. Open Qovery Console
Go to console.qovery.com
2. Navigate to Settings
Click on the settings icon in your organization
3. Access API Tokens
Go to API Tokens section
4. Generate Token
Click "Generate Token" and copy it
[!WARNING]
Save this token securely. You won't be able to see it again!
Step 2 - Configure your MCP client:
Point the client at
https://mcp.qovery.com/mcpand add this HTTP header:Authorization: Token your_qovery_token[tab] Claude Code (CI and headless runs)
Claude Code supports OAuth, so on a workstation use the OAuth tab instead. Use a token only where the browser sign-in cannot run, such as CI or a remote container, and prefer a short-lived, least-privileged token.
# Read-only (default) claude mcp add --transport http qovery https://mcp.qovery.com/mcp --header "Authorization: Token $QOVERY_TOKEN" # Read/write claude mcp add --transport http qovery "https://mcp.qovery.com/mcp?read_write=true" --header "Authorization: Token $QOVERY_TOKEN"Claude Code stores the header, token included, in its configuration (
~/.claude.json, or.mcp.jsonwith--scope project). Do not commit that file with a token in it.
[!NOTE]
The Qovery MCP Server is also available through the MCP Registry.
Access Modes
| Mode | Default | Description |
|---|---|---|
| Read-only | Yes | Can query and list resources (environments, services, deployments, etc.) |
| Read/write | No (read_write=true) | Can also trigger deployments, update configurations, and perform write operations |
[!NOTE]
The
devops_copilottool depends on two settings in your Qovery Console:
- Copilot must be enabled — if disabled, the tool will not be accessible at all, regardless of your MCP configuration
- Write access must be enabled — required to use the tool in read/write mode (in addition to the
read_write=trueURL parameter)
[!WARNING]
Enable write mode only when needed. Prefer read-only mode to limit the blast radius of unintended AI actions.
Usage Examples
Once connected, you can interact with your infrastructure naturally:
"Show me all my environments"
"What services are running in production?"
"List projects in my organization"
Troubleshooting
MCP Server Not Connecting
Issue: Client doesn't show Qovery tools or cannot connect
Solutions:
- Verify the MCP Server URL is correct:
https://mcp.qovery.com/mcp - Check your internet connection
- Restart your MCP client
- Contact Qovery Support if the issue persists
Authentication Errors
Issue: "Authentication failed" or "Invalid token" errors
Solutions:
- Verify your API token is correct (check for copy-paste errors)
- Ensure the token hasn't been revoked or expired
- Generate a new API token if needed from Qovery Console
Security Best Practices
[!WARNING]
API Token Security:
- Never share your API tokens publicly
- Don't commit tokens to version control
- Revoke tokens you no longer need from Qovery Console
- Use tokens with the minimum required permissions
- Rotate tokens regularly
Token Permissions
The API token has the same permissions as the role you selected during creation:
- Can only access resources within your organization
- Respects organization RBAC policies
- All actions are audited in Qovery Console
Next Steps
[card] Console Copilot
Use the built-in Console Copilot for quick help
[card] Slack Bot
Set up the Slack Bot for team collaboration
[card] View Capabilities
Explore everything Copilot can do
[card] Common Tasks
Practical examples and use cases
Resources
- MCP Protocol: modelcontextprotocol.io
- Claude: claude.ai
- Technical Blog: How We Built an Agentic DevOps Copilot
Manage your infrastructure and applications with natural language
Ask Claude to list environments, check application status, tail logs, or trigger a deploy. All through Qovery's MCP Server. No kubectl needed.
Related topics
- Qovery Slack Bot
- Qovery AI Copilot
- Qovery Console AI Copilot
- Delete an MCP server
- Edit an MCP server
This documentation is built and hosted on Mintlify, a developer documentation platform.