An astronaut overseeing a futuristic data hub

Connect Qovery to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Run DevOps commands directly from your IDE chat.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 10 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 10 available through Qovery.

  1. 01

    Deploy application

    Triggers an immediate deployment of a specific Git commit SHA to your environment.

  2. 02

    Get application

    Retrieves detailed configuration and status for a specific Qovery application.

  3. 03

    Get environment

    Fetches details for a specific Qovery environment.

  4. 04

    Get organization

    Returns information regarding a specific Qovery organization.

Capability set02 / 03

05-07

3 capabilities in this set.

Part of 10 available through Qovery.

  1. 05

    Get project

    Retrieves data for a specific Qovery project.

  2. 06

    List applications

    Shows all applications currently running within a specific environment.

  3. 07

    List environments

    Provides a list of all environments, such as Production or Staging, inside a project.

Capability set03 / 03

08-10

3 capabilities in this set.

Part of 10 available through Qovery.

  1. 08

    List organizations

    Lists all Qovery organizations linked to your API token.

  2. 09

    List projects

    Returns a list of all projects contained within a Qovery organization.

  3. 10

    Restart application

    Executes a zero-downtime rolling restart for a Qovery application.

Real work

What teams actually run

01

Hotfix Deployment

You copy a commit SHA and tell your agent to deploy it to a dev sandbox immediately.

02

Environment Auditing

You ask your agent to list all environments in a project to verify your setup.

03

Service Recovery

You command a rolling restart when a microservice needs to refresh its configuration.

04

Resource Verification

You check if an application has the correct CPU and RAM limits assigned.

Automate a task

Put Qovery to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Qovery works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Qovery to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

934ms average. Fast in production.

Qovery is checked daily against the live service.

Daily averagePeak 1127ms
Oct 3Today
Fastest day
744ms
Slowest day
1127ms
14-day trend
Slowing+13%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 10 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Qovery, so you can see the experience inside your AI.

It does not authenticate your account with Qovery. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Qovery Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_TO2qfcTL6CfQKOXfGLBnMgWFpOD49hykqaFBjirY/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Qovery capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "qovery-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_TO2qfcTL6CfQKOXfGLBnMgWFpOD49hykqaFBjirY/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Qovery in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Qovery owners hand off.

This MCP is built for engineers who want to manage cloud resources without context switching.

  • 01

    Platform Engineers

    They use the agent to check staging environments and cluster configs while writing IaC.

  • 02

    Full-stack Developers

    They hand off deployment tasks to the agent after pushing a branch or commit.

  • 03

    Engineering Leads

    They use the agent to verify if mission-critical apps are scaled and healthy.

FAQ

Questions Qovery owners ask.

  • 01

    How do I connect this MCP to my workflow?

    Subscribe to the MCP on Vinkius and provide your Qovery Organization API Token. Once connected, you can use it in any compatible client like Claude or Cursor.

  • 02

    Can I deploy specific code versions?

    Yes, you can use the deploy_application capability to trigger a deployment for a specific Git commit SHA.

  • 03

    Does restarting an application cause downtime?

    No, the restart_application capability performs a zero-downtime rolling restart.

  • 04

    What kind of information can my agent see?

    Your agent can access details about your organizations, projects, environments, and individual applications, including their health and resource limits.

  • 05

    Which IDEs work with this MCP?

    This MCP works with any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

  • 06

    How do I securely obtain my Qovery API Token?

    Sign in to your Qovery Console. Navigate to your Organization Settings, then to the API Tokens section. Click Generate Token (or Add). Give it a brief name, select the desired roles, and click Create. Copy the static string immediately as it won't be shown again, and paste it to authenticate.

  • 07

    Can it restart specific microservices?

    Yes. Once you identify the app_id using the list components capabilities, you can instruct your agent to restart_application. This triggers a rolling restart exactly as if you clicked 'Restart' on the console. Traffic is routed seamlessly while pods re-initialize.

  • 08

    What does deploy specific Git commit do?

    Normally, Qovery auto-deploys a branch. With deploy_application you can force Qovery to pull a specific commit ID (SHA) and deploy it immediately to an environment. This is perfect for hotfixes, effectively circumventing prolonged CI loops while ensuring zero downtime.

  • 09

    Is this capability safe to run on production?

    Yes, but with caveats. Standard queries (like listing environments and getting stats) are entirely read-only. However, capabilities like restart and deploy are mutating operations. Always make sure you instruct your agent precisely and maintain manual approval checkpoints before executing deployment functions.

Connect Qovery to Claude, Cursor, ChatGPT & more