# Qovery MCP for AI Agents AI Agent Connect > Qovery lets you manage Kubernetes deployments and cloud environments directly from your IDE. You can list environments, monitor microservices, restart pods, and trigger specific Git commit deployments through your AI agent. It puts your DevOps workflow into a single chat interface. ## Overview - **Category:** developer-tools - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_TO2qfcTL6CfQKOXfGLBnMgWFpOD49hykqaFBjirY/ai-agent-connect - **Tags:** kubernetes, deployment-automation, infrastructure-management, microservices, cloud-ops ## Description This Connector lets you manage your Kubernetes deployments and cloud environments directly from your coding environment. When you're trying to manage a complex setup, you're usually jumping between multiple dashboard tabs, terminal windows, and cloud consoles just to see if a rollout finished or to check why a microservice is acting up. It's a fragmented process that breaks your flow and makes it easy to miss a critical status update. This tool changes that by bringing your entire infrastructure into your workspace. Instead of hunting for the right dashboard, you can just ask your agent to show you the status of your production environment or check the replica counts for a specific service. You can even handle urgent tasks like rolling back a deployment or cycling pods for a hotfix without ever leaving your editor. It's about moving from manual clicking to conversational execution. By connecting your infrastructure to the Vinkius catalog, you turn your AI agent into a DevOps teammate that knows your specific projects and can execute deployments on your command. It's a much faster way to keep your systems healthy while you stay focused on writing code. You'll find that having this level of access means you can verify auto-deploy settings or get real-time status updates without the friction of context-switching. It basically turns your chat interface into a command center for your cloud ops. ## Tools ### list_applications See all apps running in a specific environment. Use this to quickly audit which services are currently live. ### list_environments List all environments like production or staging in a project. This helps you navigate through different deployment tiers. ### restart_application Perform a zero-downtime rolling restart for a Qovery app. This is perfect for refreshing environment variables or clearing cache. ### get_environment Get the specific details for a Qovery environment. This helps you see the configuration of a specific staging or production area. ### get_organization Pull the details for your Qovery organization. Use this to see high-level account information. ### list_organizations See all organizations linked to your API token. This is useful for managing multiple company accounts. ### list_projects Show all projects within a specific organization. You can use this to find the right workspace for your deployment. ### deploy_application Trigger an immediate deployment for a specific Git commit SHA. Use this to push hotfixes or test specific code versions. ### get_application Get the details for a specific Qovery application. This provides deep insights into a single microservice's status. ### get_project Pull the details for a specific Qovery project. Use this to understand the scope of a project's resources. ## Prompt Examples **Prompt:** ``` List all my Qovery projects and tell me how many there are. ``` **Response:** ``` I've checked your Qovery organization and found 3 active projects: 1. **E-commerce Monolith** (ID: prj-abc123x) 2. **Payment Gateway** (ID: prj-xyz789y) 3. **Internal Tools** (ID: prj-def456z) Would you like to see the environments for one of these? ``` **Prompt:** ``` Check the health and limits of the web-frontend in my staging environment. ``` **Response:** ``` I've looked into the staging environment. The 'web-frontend' app is currently **HEALTHY**. It's running with 2 replicas and has the following limits: * **CPU:** 2000m * **RAM:** 1024MB It is actively running and stable. ``` **Prompt:** ``` Deploy commit 7a8f9b2 to the backend-api immediately. ``` **Response:** ``` I've triggered the deployment for commit `7a8f9b2` on the 'backend-api' application. The status is now **DEPLOYING**. I'll let you know if you need me to check the status in a few minutes. ``` ## Capabilities ### View your full infrastructure map See all your organizations, projects, and environments in one place. ### Check real-time app health Get live status updates and replica counts for your microservices. ### Trigger rolling restarts Perform zero-downtime restarts to refresh pods or environment variables. ### Deploy specific Git commits Push specific commit SHAs to your environments for fast-track hotfixes. ### Inspect environment settings Verify auto-deploy settings and environment configurations via chat. ## Use Cases ### Rapid Hotfix Deployment A developer finds a bug, grabs the commit SHA, and tells their agent to deploy it to the dev sandbox using `deploy_application`. ### Instant Health Audit An engineer asks the agent to check the CPU and RAM limits for the web-frontend in staging using `get_application`. ### Production Rollout Verification A lead wants to see every app running in production and uses `list_applications` to verify the rollout succeeded. ### Zero-Downtime Pod Refresh A service is acting weird, so the user tells the agent to run `restart_application` to cycle the pods without taking the app offline. ## Benefits - Stop switching tabs by getting real-time app status and replica counts directly in your chat using `list_applications`. - Execute zero-downtime rolling restarts using `restart_application` to refresh your pods instantly without downtime. - Push hotfixes faster by using `deploy_application` to target specific Git commit SHAs without manual steps. - Gain a complete map of your infrastructure by listing organizations and projects with `list_projects`. - Audit your live services quickly using `list_applications` to see exactly what's running in any environment. - Manage multiple environments easily with `list_environments` to keep your staging and production workflows organized. ## How It Works The bottom line is you get to manage your entire cloud deployment lifecycle through a simple chat interface. 1. Subscribe to the Connector and grab your Qovery Organization API Token. 2. Connect the token to your AI client through the Vinkius dashboard. 3. Ask your agent to list projects or deploy a specific commit. ## Frequently Asked Questions **What does the Qovery MCP do for my Kubernetes setup?** It lets you manage your Qovery-hosted Kubernetes environments through your AI client. You can check app health, list environments, and trigger deployments without leaving your IDE. **Can I use the Qovery MCP to deploy specific code versions?** Yes, you can tell your agent to deploy a specific Git commit SHA to your Qovery applications. This is great for pushing quick hotfixes to specific environments. **How does the Qovery MCP help with rolling restarts?** It allows your agent to perform zero-downtime rolling restarts of your Qovery applications. This is perfect for refreshing environment variables or clearing cache issues. **Does the Qovery MCP work with Cursor or VS Code?** Yes, it works with any MCP-compatible client, including Cursor, Windsurf, and VS Code. You just connect it via Vinkius and start managing your infrastructure. **Can I see the health of my microservices with the Qovery MCP?** Yes, your agent can inspect individual microservices, check replica counts, and verify auto-deploy settings across your Qovery projects. **How do I connect my Qovery account to the Connector?** You'll need to provide your Qovery Organization API Token. Once connected through Vinkius, your agent can access your projects, environments, and applications. **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.