Qovery MCP Server

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 →](https://modelcontextprotocol.io) **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](/getting-started/quickstart/ai-agent) 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.

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

<Steps>
  <Step title="Open Qovery Console">
    Go to [console.qovery.com](https://console.qovery.com)
  </Step>

  <Step title="Navigate to Settings">
    Click on the settings icon in your organization
  </Step>

  <Step title="Access API Tokens">
    Go to **API Tokens** section
  </Step>

  <Step title="Generate Token">
    Click "Generate Token" and copy it

    <Warning>
      Save this token securely. You won't be able to see it again!
    </Warning>
  </Step>
</Steps>

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

<Tabs>
  <Tab title="Claude Code">
    Configure claude code to add your Qovery token in the HTTP headers

    ```bash theme={null}
    claude mcp add --transport http qovery https://mcp.qovery.com/mcp --header 'Authorization: Token qov_xxxx'
    ```

    ```
    Authorization: Token your_qovery_token
    ```
  </Tab>
</Tabs>

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

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:

1. Copilot must be enabled — if disabled, the tool will not be accessible at all, regardless of your MCP configuration
2. 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.

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:

1. Verify the MCP Server URL is correct: https://mcp.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. Generate a new API token if needed from Qovery Console

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