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.

Can it restart specific microservices?

Yes. Once you identify the `app_id` using the list components tools, 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.

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.

Is this tool safe to run on production?

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

Qovery MCP Server for AutoGen 10 tools — connect in under 2 minutes

Name: Qovery
Availability: InStock
Author: Vinkius

microsoft.github.io/autogen/docs/tools/mcp-tools

Built by Vinkius GDPR 10 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Qovery as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="qovery_agent",
            tools=tools,
            system_message=(
                "You help users with Qovery. "
                "10 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Qovery MCP Server

Connect your Qovery infrastructure to any AI agent and bring DevOps execution directly into your coding environment.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Qovery tools. Connect 10 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

What you can do

Map your Infrastructure — Traverse effortlessly through your Qovery Organizations, Projects, and Environments to build a complete mental map of your deployments
Monitor Applications — Inspect individual microservices, check active replica counts, verify auto-deploy settings, and get real-time status updates without switching contexts to the Qovery dashboard
Take Action via Chat — Trigger zero-downtime rolling restarts to cycle Kubernetes pods and refresh environment variables directly inside Claude or Cursor
Targeted Deployments — Issue a fast-track deploy of a specific Git commit SHA for hotfixes or localized feature testing, all handled friction-free by the LLM

The Qovery MCP Server exposes 10 tools through the Vinkius. Connect it to AutoGen in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Qovery to AutoGen via MCP

Follow these steps to integrate the Qovery MCP Server with AutoGen.

Install AutoGen

Run pip install "autogen-ext[mcp]"

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

Explore tools

The workbench discovers 10 tools from Qovery automatically

Why Use AutoGen with the Qovery MCP Server

AutoGen provides unique advantages when paired with Qovery through the Model Context Protocol.

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Qovery tools to solve complex tasks

Role-based architecture lets you assign Qovery tool access to specific agents. a data analyst queries while a reviewer validates

Human-in-the-loop support: agents can pause for human approval before executing sensitive Qovery tool calls

Code execution sandbox: AutoGen agents can write and run code that processes Qovery tool responses in an isolated environment

Qovery + AutoGen Use Cases

Practical scenarios where AutoGen combined with the Qovery MCP Server delivers measurable value.

Collaborative analysis: one agent queries Qovery while another validates results and a third generates the final report

Automated review pipelines: a researcher agent fetches data from Qovery, a critic agent evaluates quality, and a writer produces the output

Interactive planning: agents negotiate task allocation using Qovery data to make informed decisions about resource distribution

Code generation with live data: an AutoGen coder agent writes scripts that process Qovery responses in a sandboxed execution environment

Qovery MCP Tools for AutoGen (10)

These 10 tools become available when you connect Qovery to AutoGen via MCP:

deploy_application

Triggers an immediate deployment of a specific Git commit SHA

get_application

Retrieves details for a specific Qovery application

get_environment

Retrieves details for a specific Qovery environment

get_organization

Retrieves details for a specific Qovery organization

get_project

Retrieves details for a specific Qovery project

list_applications

Lists all applications running in a specific environment

list_environments

Lists all environments (Production, Staging, etc.) in a project

list_organizations

Lists all Qovery organizations associated with the token

list_projects

Lists all projects within a Qovery organization

restart_application

Performs a zero-downtime rolling restart of a Qovery application

Example Prompts for Qovery in AutoGen

Ready-to-use prompts you can give your AutoGen agent to start working with Qovery immediately.

"List all Qovery projects and tell me how many there are."

"Check the health and limits of the application in my staging environment."

"Deploy commit 7a8f9b2 to the backend application immediately."

Troubleshooting Qovery MCP Server with AutoGen

Common issues when connecting Qovery to AutoGen through the Vinkius, and how to resolve them.

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Qovery + AutoGen FAQ

Common questions about integrating Qovery MCP Server with AutoGen.

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Qovery tools during their conversation turns.

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.