Bring Sandboxes
to CrewAI
Learn how to connect Daytona (Dev Workspaces) to CrewAI and start using 28 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 Daytona (Dev Workspaces) MCP Server?
Connect your Daytona account to any AI agent to orchestrate cloud-based development environments through natural language. Daytona provides standardized, ephemeral sandboxes that can be provisioned and managed on demand.
What you can do
- Sandbox Orchestration — List, create, start, stop, and delete sandboxes with specific CPU, memory, and disk configurations.
- Snapshot Management — Create and manage snapshots to preserve environment states or activate them for new sandboxes using
create_snapshotandactivate_snapshot. - API Key Control — Manage your authentication keys directly, including listing and creating new access tokens via
list_api_keysandcreate_api_key. - Resource Scaling — Dynamically resize sandbox resources (vCPU, RAM, Disk) to match your workload requirements using
resize_sandbox. - Volume & Storage — Inspect and manage persistent volumes and snapshots for your dev environments.
How it works
- Subscribe to this server
- Enter your Daytona API Key
- Start managing your dev infrastructure from Claude, Cursor, or any MCP client
Who is this for?
- DevOps Engineers — Automate the lifecycle of test environments and sandboxes.
- Software Developers — Spin up fresh coding environments without leaving the chat or IDE.
- QA Teams — Quickly recover sandboxes from error states or fork existing environments for debugging.
Built-in capabilities (28)
Activate a snapshot
Archive a sandbox
Create a new Daytona API key
Create a new Daytona sandbox
Create a new snapshot
Create a new volume
Deactivate a snapshot
Delete an API key by name
Delete a sandbox
Delete a snapshot
Delete a volume
Fork an existing sandbox
Get details of a specific API key by name
Get details of the currently authenticated API key
Get details of a specific sandbox
Get a signed preview URL for a specific port on a sandbox
Get details of a specific snapshot
Get details of a specific volume by ID
Get details of a specific volume by name
List Daytona API keys
List all Daytona sandboxes
List all Daytona sandboxes (paginated)
List all Daytona snapshots
List all Daytona volumes
Recover a sandbox from an error state
Resize sandbox resources
Start a stopped sandbox
Stop a running sandbox
Why CrewAI?
When paired with CrewAI, Daytona (Dev Workspaces) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Daytona (Dev Workspaces) 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
Daytona (Dev Workspaces) in CrewAI
Daytona (Dev Workspaces) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Daytona (Dev Workspaces) 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 Daytona (Dev Workspaces) in CrewAI
The Daytona (Dev Workspaces) 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 28 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
Daytona (Dev Workspaces) for CrewAI
Every tool call from CrewAI to the Daytona (Dev Workspaces) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I change the resources of an existing sandbox?
Yes, you can use the resize_sandbox tool to update the CPU, memory, or disk size of a specific sandbox by providing its ID or name.
How do I create a new environment with a specific Docker image?
Use the create_sandbox tool and provide the image parameter with the desired Docker or OCI image name.
What should I do if a sandbox is in an error state?
You can use the recover_sandbox tool to attempt to restore a sandbox from an error state back to a functional one.
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 →
Humaans
10 toolsManage employees, leaves, and organization data via Humaans HRIS API.
Sentinel Hub
14 toolsAccess and process satellite imagery from Sentinel, Landsat, and other Earth observation missions through a powerful cloud API.
CHATFLY
8 toolsManage AI chatbots and knowledge bases via CHATFLY — train bots on custom data and track conversations directly from any AI agent.
PushEngage
7 toolsRe-engage website visitors with browser push notifications that increase traffic, recover abandoned carts, and boost retention.