Bring Cloud Computing
to CrewAI
Learn how to connect Scaleway to CrewAI and start using 3 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Scaleway MCP Server?
Connect your Scaleway account to any AI agent to manage your cloud infrastructure through natural language. This server provides direct access to the Scaleway Instances API.
What you can do
- Instance Discovery — List all virtual machines across different availability zones (e.g., fr-par-1, nl-ams-1)
- Provisioning — Create new instances by specifying names, commercial types (like DEV1-S), and image IDs
- Power Management — Remotely power on, power off, or reboot your servers
- Lifecycle Control — Terminate instances that are no longer needed directly from the chat
How it works
- Subscribe to this server
- Enter your Scaleway Secret Key
- Start managing your cloud resources from Claude, Cursor, or any MCP-compatible client
Who is this for?
- DevOps Engineers — quickly check server status or reboot instances without leaving the terminal or IDE
- Developers — spin up new development environments using simple text commands
- Cloud Architects — audit active resources across multiple zones efficiently
Built-in capabilities (3)
Create a new Scaleway instance (server)
List Scaleway instances (servers) in a specific zone
Perform an action on a Scaleway instance (e.g., poweron, poweroff)
Why CrewAI?
When paired with CrewAI, Scaleway becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Scaleway 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
Scaleway in CrewAI
Scaleway and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Scaleway to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Scaleway in CrewAI
The Scaleway 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. All 3 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Scaleway for CrewAI
Every tool call from CrewAI to the Scaleway MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I see my servers in a specific region like Paris?
Use the list_instances tool and provide the zone parameter (e.g., 'fr-par-1'). The agent will return a list of all instances currently provisioned in that specific Scaleway zone.
Can I reboot or shut down a server using this integration?
Yes! The perform_instance_action tool allows you to send 'poweron', 'poweroff', 'reboot', or 'terminate' commands to any specific server ID within a zone.
What information is needed to create a new instance?
To use create_instance, you need to provide the zone, a name for the server, the commercial type (e.g., 'DEV1-S'), and the image ID or label you wish to deploy.
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 →
WHO GHO
3 toolsAccess 2,200+ health indicators from 194 countries — life expectancy, disease prevalence, mortality rates, immunization coverage, and environmental health data from the World Health Organization.
Simple Analytics
5 toolsPrivacy-first web analytics without cookies. Fetch aggregated stats, export raw data, and manage your websites directly from your AI agent.
BLS Jobs — Nonfarm Payrolls & Wages
2 toolsAccess the definitive source for US employment growth. Query Nonfarm Payrolls, private sector job creation, and average hourly earnings tracked by the BLS Current Employment Statistics (CES) program.
AccuWeather
10 toolsEnterprise-grade weather intelligence — current conditions, forecasts, alarms, and activity indices via AI.