Bring Kubernetes
to CrewAI
Create your Vinkius account to connect Qovery to CrewAI and start using all 10 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Qovery MCP Server?
Connect your Qovery infrastructure to any AI agent and bring DevOps execution directly into your coding environment.
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
How it works
- Subscribe to this server
- Supply your Qovery Organization API Token
- Start managing your clusters and triggering deploys across your environments within seconds
Who is this for?
- Platform Engineers — easily check staging environments and cluster configs while writing infrastructure-as-code paradigms
- Full-stack Developers — push a fix to a branch, copy the commit SHA, and just tell your agent to deploy it instantly to the dev sandbox
- Engineering Leads — check if the latest mission-critical app is properly scaled and healthy across multiple availability zones
Built-in capabilities (10)
Triggers an immediate deployment of a specific Git commit SHA
Retrieves details for a specific Qovery application
Retrieves details for a specific Qovery environment
Retrieves details for a specific Qovery organization
Retrieves details for a specific Qovery project
Lists all applications running in a specific environment
Lists all environments (Production, Staging, etc.) in a project
Lists all Qovery organizations associated with the token
Lists all projects within a Qovery organization
Performs a zero-downtime rolling restart of a Qovery application
Why CrewAI?
When paired with CrewAI, Qovery becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Qovery tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Qovery in CrewAI
Why run Qovery with Vinkius?
The Qovery connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 10 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.
* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.
Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Qovery using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Qovery and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Qovery to CrewAI through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Qovery for CrewAI
Every request between CrewAI and Qovery is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
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.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Brex
10 toolsEquip your AI to navigate your Brex suite. Spin up virtual cards, route new team members, and check daily cash allocations through natural chat.
Mem0
4 toolsGive your AI agent persistent memory — store, search, and recall facts, preferences, and context across sessions using the leading agent memory platform.
EOSDA Agriculture Satellite Data
6 toolsPrecision agriculture satellite intelligence — access NDVI, soil moisture, and crop health via AI.
Withings
10 toolsAccess comprehensive health and fitness data — track weight, blood pressure, sleep cycles, steps, workouts, and heart rate directly from Withings devices.