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 athttps://mcp.qovery.com/mcp. Choose one of the two authentication methods below to connect your MCP client.
- OAuth (recommended)
- API Token
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:Refer to your MCP client’s documentation for how to configure OAuth with a custom server URL.
The Qovery MCP Server is also available through the MCP Registry.
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=trueURL parameter)
Usage Examples
Once connected, you can interact with your infrastructure naturally: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
Security Best Practices
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
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
- MCP Protocol: modelcontextprotocol.io
- Claude: claude.ai
- Technical Blog: How We Built an Agentic DevOps Copilot