Let AI agents
manage your infrastructure.
The Qovery MCP Server connects any MCP-compatible client to the infrastructure you already run. Query environments, inspect service state, tail logs, and trigger deployments by conversation. Read-only by default, so the interface is safe before you have configured anything.
What you get.
Standard MCP protocol
Implements the open Model Context Protocol over remote streamable HTTP at https://mcp.qovery.com/mcp. Published in the MCP registry as com.qovery. No custom integration code required.
Read-only by default
The server connects read-only unless you add read_write=true to the URL and separately enable write access in the Console. Two deliberate switches, neither of which a model can talk its way past.
OAuth or API token
Clients that support OAuth authenticate with no token handling at all. Otherwise pass a Qovery API token via the URL or an Authorization header -- including a view-only token, which guarantees no destructive action is possible.
Your RBAC, your audit trail
A token carries the permissions of the role it was issued under and can only reach resources in your organization. Every action is recorded in the Qovery Console audit trail.
What you can do.
Infrastructure Q&A
"Show me all my environments", "what services are running in production?" -- answered from live state rather than from whatever is in the model's context.
AI-assisted debugging
"Why is the payment service failing?" -- the agent checks deployment status, tails logs, inspects configuration, and proposes a fix. All of it possible in read-only mode.
Day-2 operations
With write access explicitly enabled, trigger deployments and update configuration by conversation. The skills handle going from code to running; the MCP Server handles everything after.
Connect your MCP client
- 01Find the server URL and manage access under Settings > MCP Server in the Console
- 02Add https://mcp.qovery.com/mcp to your client -- OAuth if it supports it, otherwise an API token
- 03Start read-only, which is the default
- 04Add read_write=true and enable write access in the Console only when you need it
# Claude Code, OAuth, read-only (default)
$ claude mcp add --transport http qovery \
https://mcp.qovery.com/mcp --callback-port 4242
# Read/write, when you explicitly want it
$ claude mcp add --transport http qovery \
"https://mcp.qovery.com/mcp?read_write=true" --callback-port 4242
# Any other client: use the server URL directly
# https://mcp.qovery.com/mcp?token=YOUR_QOVERY_TOKENOperate by
conversation.
The skills deploy. The MCP Server operates what is already running. Connect your client in one command and start read-only.