Skip to main content

Documentation Index

Fetch the complete documentation index at: https://qovery-update-mcp-query.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

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 →

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. Choose one of the two authentication methods below to connect your MCP client.
The Qovery MCP Server is also available through the MCP Registry.

Access Modes

ModeDefaultDescription
Read-onlyYesCan query and list resources (environments, services, deployments, etc.)
Read/writeNo (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

Console Copilot

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

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