Skip to main content

​
Overview

The Qovery MCP (Model Context Protocol) Server enables you to use Qovery AI Copilot directly in Claude Desktop and other MCP-compatible clients. This gives you natural language control over your entire Qovery infrastructure.
Early Access Required: The Qovery MCP Server is available online and on demand. Contact Qovery Support to request early access.
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 →

​
Operating Modes

The MCP Server’s operating mode is determined by your organization’s AI Copilot settings and your API token’s permissions:
Safe exploration - View-only accessIn read-only mode, the Copilot allows you to:
  • View information and status
  • Get help and recommendations
  • Troubleshoot issues
  • Monitor deployments
  • Analyze infrastructure
  • No changes to infrastructure
This ensures safe exploration without risk of accidental modifications.
Read-only mode is active when your organization has disabled AI write permissions, or when your API token has viewer-level permissions.
Permission Hierarchy: The MCP Server operates at the highest level of access available based on:
  • Your organization’s AI Copilot authorization settings (read-only or read-write)
  • Your API token’s role permissions
The most restrictive setting takes precedence. For example, if your organization enables AI write access but your token has viewer permissions, the Copilot will operate in read-only mode.Note: The operating mode applies to all your conversations. If you have read-write access, your conversations will operate in read-write mode.

​
Prerequisites

Before using the MCP Server:
  • MCP-Compatible Client: Claude Desktop, or any other MCP-compatible application
  • Qovery Account: Active account with infrastructure
  • API Token: Generate from Qovery Console (Settings → API Tokens)

​
Setup

​
1. Generate Your Qovery API 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
Save this token securely. You won’t be able to see it again!

​
2. Configure Your MCP Client

The Qovery MCP Server is accessible via the following URL: 
https://p8081-api-ai-dev.qovery.com/mcp
Add the Qovery MCP Server to your MCP client’s configuration using: 
Server URL: https://p8081-api-ai-dev.qovery.com/mcp
Refer to your specific MCP client’s documentation for detailed setup instructions on how to add a custom MCP server.

​
Usage

​
Authentication with API Token

The Qovery MCP Server requires authentication via your API token. There are two ways to provide it:
Start your conversation naturally, and Claude will request the token when needed:You:
Can you list my Qovery environments?
Claude:
I'll need your Qovery API token to access your infrastructure. 
Please provide your API token.
You:
Here's my token: xxxxxxxxxxxxx
Claude:
[Returns your environments list]
Token Persistence: Once you provide your API token in a conversation, it will be remembered for the duration of that conversation. However, when you start a new conversation, you’ll need to provide the token again.

​
Usage Examples

Once authenticated, you can interact with your infrastructure naturally:

​
Check Status

"Show me all my environments"
"What's the status of production?"
"List applications in the staging environment"

​
Deploy Applications

"Deploy the latest version of my-api to production"
"Restart the frontend application"
"Scale the API service to 5 replicas"

​
Troubleshoot Issues

"Why is my deployment failing?"
"Show me error logs from the last hour"
"Debug the connection timeout in staging"

​
Manage Infrastructure

"Create a new environment called feature-test"
"Clone production to staging"
"Stop all services in the dev environment"

​
Troubleshooting

​
MCP Server Not Connecting

Issue: Client doesn’t show Qovery tools or cannot connect Solutions:
  1. Verify the MCP Server URL is correct: https://p8081-api-ai-dev.qovery.com/mcp
  2. Check your internet connection
  3. Restart your MCP client
  4. Contact Qovery Support if the issue persists

​
Authentication Errors

Issue: “Authentication failed” or “Invalid token” errors Solutions:
  1. Verify your API token is correct (check for copy-paste errors)
  2. Ensure the token hasn’t been revoked or expired
  3. Verify the token has the necessary permissions for the requested operation
  4. Generate a new API token if needed from Qovery Console

​
Token Not Persisting

Issue: Need to re-enter token for each question Solutions:
  1. Ensure you’re staying in the same conversation
  2. Provide the token at the beginning of new conversations
  3. Check if your client is maintaining the conversation context

​
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

Console Copilot

Use the built-in Console Copilot for quick help
https://mintcdn.com/qovery/bC94RbU5OE288_w9/images/logos/slack-icon.svg?fit=max&auto=format&n=bC94RbU5OE288_w9&q=85&s=1cb84849542ddf53fa8fac6e3789e2a0

Slack Bot

Set up the Slack Bot for team collaboration

View Capabilities

Explore everything Copilot can do

Common Tasks

Practical examples and use cases

​
Resources