Qovery

MCP Server

Connect any MCP-compatible client to your Qovery infrastructure

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.

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 →

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.

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

The devops_copilot tool 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=true URL parameter)

Enable write mode only when needed. Prefer read-only mode to limit the blast radius of unintended AI actions.

Security Best Practices

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

Use the built-in Console Copilot for quick help

Set up the Slack Bot for team collaboration

Explore everything Copilot can do

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.

Try Qovery free →

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.

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:**

```bash theme={null}
# 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 4242

Refer to your MCP client's documentation for how to configure OAuth with a custom server URL.

 
 
 If your MCP client doesn't support OAuth, generate a Qovery API token and pass it via the URL.

Step 1 — Generate a token:

Go to console.qovery.com

Click on the settings icon in your organization

Go to API Tokens section

Click "Generate Token" and copy it

Save this token securely. You won't be able to see it again!

Step 2 — Configure your MCP client:

Use the following URL format, replacing your_qovery_token with your token:

# Read-only (default)
https://mcp.qovery.com/mcp?token=your_qovery_token

# Read/write
https://mcp.qovery.com/mcp?token=your_qovery_token&read_write=true

You can also pass the token via an Authorization header instead:

If you want to use a Qovery API token, for example to be able to limit the permission of what can be done. You can create a token with read/view only permission so you are guaranteed no destructive action can be taken.

Configure claude code to add your Qovery token in the HTTP headers

claude mcp add --transport http qovery https://mcp.qovery.com/mcp --header 'Authorization: Token qov_xxxx'

Authorization: Token your_qovery_token

 
 
 
 The Qovery MCP Server is also available through the [MCP Registry](https://registry.modelcontextprotocol.io/v0.1/servers?search=com.qovery).

## 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