Documentation Index

Fetch the complete documentation index at: https://www.qovery.com/docs/llms.txt Use this file to discover all available pages before exploring further.

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
• API Token: Generate from Qovery Console (Settings -> API Tokens) (only needed if you don't use OAuth)

Setup

1. Generate Your Qovery API Token (if not using OAuth)

Go to [console.qovery.com](https://console.qovery.com) Click on the settings icon in your organization Go to **API Tokens** section Click "Generate Token" and copy it

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

2. Configure Your MCP Client

The Qovery MCP Server is accessible at:

https://mcp.qovery.com/mcp

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

Authentication

The Qovery MCP Server supports 2 authentication methods:

OAuth

The easiest method to authentificate, it will open a page in your browser to authentificate

Use the MCP Server URL and configure an OAuth callback port

```bash theme={null}
claude mcp add --transport http qovery https://mcp.qovery.com/mcp --callback-port 4242
```

At the root of your `.codex/config.toml` add this settings.

```toml theme={null}
mcp_oauth_callback_port = 4242
```

After you can add Qovery MCP Server with this command

```bash theme={null}
codex mcp add qovery --url https://mcp.qovery.com/mcp
```

Qovery API Token

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.

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'
```

In your `.codex/config.toml` add this settings to the Qovery MCP server section

```
[mcp_servers.qovery]
url = "https://mcp.qovery.com/mcp"
http_headers = { "Authorization" = "Token qov_xxxx" }
```

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