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 supports both operating modes:
  • Read-Only Mode (Default)
  • Read-Write Mode
Default behavior - Safe for explorationThe MCP Server starts in read-only mode by default, allowing 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.

​
Prerequisites

Before installing the MCP Server:
  • Claude Desktop: Download from claude.ai/download
  • Qovery Account: Active account with infrastructure
  • API Token: Generate from Qovery Console (Settings → API Tokens)
  • Node.js 18+ or Python 3.10+

​
Installation

  • NPM (Node.js)
  • Python
Install via NPM:
npm install -g @qovery/mcp-server
Verify installation:
qovery-mcp-server --version

​
Configuration

​
1. Get Your Qovery API Token

1

Open Qovery Console

Go to console.qovery.com
2

Navigate to Settings

Click on your organization → Settings → API Tokens
3

Generate Token

Click “Generate Token” and copy it
Save this token securely. You won’t be able to see it again!

​
2. Configure Claude Desktop

Add the Qovery MCP Server to Claude Desktop configuration:
  • macOS
  • Windows
  • Linux
Edit configuration file:
nano ~/Library/Application\ Support/Claude/claude_desktop_config.json
Add Qovery MCP Server:
{
  "mcpServers": {
    "qovery": {
      "command": "qovery-mcp-server",
      "env": {
        "QOVERY_API_TOKEN": "your-api-token-here"
      }
    }
  }
}

​
3. Restart Claude Desktop

Close and reopen Claude Desktop for changes to take effect.

​
Verify Setup

In Claude Desktop, start a new conversation and ask: 
"Can you list my Qovery environments?"
If configured correctly, Claude will use the Qovery MCP Server to retrieve and display your environments.

​
Usage Examples

Once configured, 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"

​
Advanced Configuration

​
Multiple Organizations

If you have multiple Qovery organizations: 
{
  "mcpServers": {
    "qovery-prod": {
      "command": "qovery-mcp-server",
      "env": {
        "QOVERY_API_TOKEN": "production-token",
        "QOVERY_ORG_ID": "org-id-1"
      }
    },
    "qovery-staging": {
      "command": "qovery-mcp-server",
      "env": {
        "QOVERY_API_TOKEN": "staging-token",
        "QOVERY_ORG_ID": "org-id-2"
      }
    }
  }
}

​
Custom Configuration

Additional environment variables: 
{
  "mcpServers": {
    "qovery": {
      "command": "qovery-mcp-server",
      "env": {
        "QOVERY_API_TOKEN": "your-token",
        "QOVERY_API_URL": "https://api.qovery.com",
        "LOG_LEVEL": "debug"
      }
    }
  }
}

​
Troubleshooting

​
MCP Server Not Connecting

Issue: Claude Desktop doesn’t show Qovery tools Solutions:
  1. Verify API token is correct
  2. Check configuration file syntax (valid JSON)
  3. Restart Claude Desktop
  4. Check Claude Desktop logs

​
Authentication Errors

Issue: “Authentication failed” errors Solutions:
  1. Verify API token hasn’t expired
  2. Check token has correct permissions
  3. Generate a new API token if needed

​
Command Not Found

Issue: qovery-mcp-server: command not found Solutions:
  1. Verify installation: npm list -g @qovery/mcp-server
  2. Check PATH includes npm global bin directory
  3. Reinstall: npm install -g @qovery/mcp-server

​
Security Best Practices

API Token Security:
  • Never commit configuration files with tokens to version control
  • Use environment variables for tokens in CI/CD
  • Rotate tokens regularly
  • Revoke unused tokens in Qovery Console

​
Token Permissions

The API token has the same permissions as your user account:
  • Can only access resources you have permission to
  • 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