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 CrewAI 10 tools — connect in under 2 minutes

Name: Qovery
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Qovery through Vinkius, pass the Edge URL in the `mcps` parameter and every Qovery tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

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

from crewai import Agent, Task, Crew

agent = Agent(
    role="Qovery Specialist",
    goal="Help users interact with Qovery effectively",
    backstory=(
        "You are an expert at leveraging Qovery tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Qovery "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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.

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.

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 CrewAI 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 CrewAI via MCP

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

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Qovery

Why Use CrewAI with the Qovery MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Qovery through the Model Context Protocol.

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 `mcps` parameter 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 + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Qovery for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Qovery, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Qovery tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Qovery against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Qovery MCP Tools for CrewAI (10)

These 10 tools become available when you connect Qovery to CrewAI 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 CrewAI

Ready-to-use prompts you can give your CrewAI 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 CrewAI

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

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.

Qovery + CrewAI FAQ

Common questions about integrating Qovery MCP Server with CrewAI.

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.