Qovery MCP. Manage deployments and environments conversationally
Qovery brings Kubernetes and cloud deployment management right into your chat client. List every environment, check application health, trigger zero-downtime restarts, or deploy a precise Git commit SHA—all without leaving your coding workflow.
Give Claude and any AI agent real-world access
List and navigate through every Qovery Organization, Project, and Environment associated with your account.
Retrieve real-time status details for specific applications, including replica counts and auto-scaling settings.
Execute a zero-downtime rolling restart on an application to refresh variables or cycle out old Kubernetes pods.
Force a targeted deployment of any precise Git commit SHA, perfect for localized hotfixes or feature testing.
Ask an AI about this
Waiting for input…
What AI agents can do with Qovery: Deployment & Environment Ops (9 Tools)
Use these tools to list organizations, fetch application details, manage environment states, trigger deployments, and restart services across Qovery.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Qovery MCPGet Environment
Retrieves specific details and status information for one Qovery environment.
Get Organization
Retrieves details for a specific Qovery organization
List Organizations
Retrieves a list of all Qovery organizations connected to the provided API token.
List Projects
Lists all projects that belong within a specific Qovery organization.
Restart Application
Performs an immediate, zero-downtime rolling restart of the target application's...
List Applications
Shows all running applications deployed inside a specified environment.
List Environments
Lists all active environments (like Production or Staging) within a given project.
Deploy Application
Triggers a fast deployment using a precise Git commit SHA to update the running code.
Get Application
Fetches deep details about a single Qovery application instance.
Get Project
Retrieves comprehensive details for one specific Qovery project.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Qovery, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Qovery. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Status Quo: Jumping Between Tabs to Check App Health
Today, checking if an application is healthy means jumping between the Qovery dashboard, the Kubernetes logs, and sometimes even a separate monitoring tool. You click on the Project, then select the Environment, then drill down to the Application's replica count, hoping you haven't missed any warning lights or stale status messages.
With this MCP, all that data is available in chat. Your agent pulls the exact application details using `get_application` and shows you the health report immediately. You get a single source of truth without ever leaving your conversation.
Qovery MCP: Deployments on Demand
The manual process for deploying a hotfix is painful: find the commit SHA, remember which branch it belongs to, navigate to the right environment, and click 'Deploy'. One wrong click or forgotten variable breaks your flow.
Now you just tell your agent to deploy using `deploy_application`. It handles the targeted deployment of that specific Git commit SHA. The control is immediate, accurate, and conversational.
What Qovery MCP does for your AI
Stop context switching between your IDE and the cloud dashboard just to run basic devops tasks. This MCP connects your Qovery infrastructure directly into any AI client. Instead of navigating through multiple tabs to map out your Organization structure, check specific Project details, or verify an Environment's current status, you talk to your agent.
You can ask it to list all applications in a staging environment, grab the replica count for a microservice, or restart pods with a single command. When you need a hotfix deployed—say, testing a new Git commit SHA against development sandboxes—it handles that targeted deployment instantly. Because this MCP lives on Vinkius, your agent gets access to thousands of other tools too.
It’s pure infrastructure control, conversationalized.
019d75fb-5ff8-70bf-b45b-2d8e52fd1da4 How to set up Qovery MCP
The bottom line is you control your production environment using natural chat conversation, not complex CLI commands or web dashboards.
Subscribe to this MCP and supply your Qovery Organization API Token.
Your AI agent uses the token to read the structure of your cloud deployments (Organizations, Projects, Environments).
You prompt the agent with an action (e.g., 'Restart the Payment Gateway app in staging'), and it executes the command directly against Qovery.
Who uses Qovery MCP
The platform engineer who hates context switching between their terminal and the cloud dashboard. It's for anyone whose job requires constant visibility into multiple staging environments, needing to verify a microservice is properly scaled and healthy without leaving their IDE.
Checking cluster configurations or verifying staging environment status while writing infrastructure-as-code.
Pushing a quick fix to a branch, copying the commit SHA, and telling their agent to deploy it immediately to the dev sandbox for testing.
Checking if the latest mission-critical app is correctly scaled and healthy across multiple availability zones after a major release.
Benefits of connecting Qovery MCP
Stop clicking through dashboards. Instead of manually navigating to check application states, your agent gets the details instantly using get_application.
No more guessing if a fix deployed correctly. You can issue a fast-track deploy of any specific Git commit SHA directly via deploy_application.
Need to cycle pods for variable changes? Running an app restart is simple: just use restart_application and watch the agent handle the zero-downtime process.
Mapping your infrastructure used to be a multi-step nightmare. Now, you can list all organizations (list_organizations) and projects (list_projects) in a single chat query.
Your team saves time by eliminating context switching. You stay in your IDE while performing critical actions like listing environments (list_environments) or checking project details (get_project).
This MCP gives you full visibility, allowing you to verify the scaling and health of mission-critical apps across all zones without leaving your desk.
Qovery MCP use cases
The Hotfix Scenario
A developer finds a bug in production. Instead of SSHing into a server or manually triggering a deployment, they copy the commit SHA and ask their agent to use deploy_application on the specific app in the Production environment. It's instant verification.
The Scaling Check
An engineering lead needs to confirm if the Payment Gateway is properly scaled after a peak traffic event. They ask their agent, which uses list_applications and get_application, to report on replica counts across all active environments.
The Environment Audit
A platform engineer needs to build a map of the company's services. They prompt their agent, which first uses list_organizations and then cascades down through list_projects, providing a full structural overview.
The Variable Refresh
A service needs its environment variables refreshed without downtime. The engineer simply tells the agent to run a restart using restart_application on the affected microservice, and it handles the rolling update automatically.
Qovery MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Manual Dashboard Refreshing
Opening the Qovery web dashboard multiple times to check if an environment status has updated or if a pod is stuck in 'pending' state.
Instead, ask your agent to use get_environment or list_applications. It fetches the current, definitive status and reports it back immediately.
Copying CLI Commands
Finding a deployment command in documentation, copying it into a terminal, and hoping all environment variables are set correctly.
Use the deploy_application tool. You just give your agent the commit SHA and tell it where to deploy; it handles the rest of the complex infrastructure logic.
Confusing Scope
Trying to list projects across unrelated organizations, leading to fragmented results or needing multiple API calls.
Start by listing all available organizations using list_organizations. Then, drill down project-by-project using list_projects to stay focused.
When to use Qovery MCP
Use this MCP if your current workflow requires constant interaction with cloud deployment details—checking status, restarting services, or triggering deployments across multiple environments. If you spend more than five minutes clicking through dashboards or writing complex CLI scripts just to get a basic status report, this is for you. Don't use it, however, if you only need general architectural knowledge; simply reading the documentation might suffice. Also, don't use it if your primary goal is code generation; that’s better handled by pure coding assistants. This MCP is purely about operations and state management.
Frequently asked questions about Qovery MCP
How do I list all my Qovery organizations with the Qovery MCP? +
You use the list_organizations tool to get a full catalog of all connected organizations. This is your first step when mapping out your entire infrastructure.
Can I restart an application using the restart_application tool? +
Yes, running restart_application triggers a zero-downtime rolling restart across the specified pods and environment. It's perfect for refreshing variables without service interruption.
What information does get_project provide about my Qovery project? +
The get_project tool retrieves all key details about a specific project, including its associated environments and applications. It gives you the full context for that development silo.
How do I deploy a specific version using the Qovery MCP? +
Use deploy_application and pass in the precise Git commit SHA. This ensures you are deploying exactly what was tested, eliminating guesswork from manual deployments.
Does this MCP help with checking environment status? +
Absolutely. You can use get_environment to retrieve detailed status checks for any specific environment in your project, confirming its readiness for deployment.
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.