Bring Sandboxes
to Cursor
Learn how to connect Daytona (Dev Workspaces) to Cursor 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 Cursor?
Cursor's Agent mode turns Daytona (Dev Workspaces) into an in-editor superpower. Ask Cursor to generate code using live data from Daytona (Dev Workspaces) and it fetches, processes, and writes. all in a single agentic loop. 28 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Daytona (Dev Workspaces) in Cursor
Daytona (Dev Workspaces) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Daytona (Dev Workspaces) to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Bloomerang
10 toolsManage donors and donations via Bloomerang — list constituents, transactions, and campaigns directly from any AI agent.
Fax.Plus
8 toolsSend and receive faxes digitally through a modern API without physical machines, keeping your business compliant and paperless.
Scispot
12 toolsAutomate cannabis laboratory testing via Scispot LIMS — manage samples, track analytical results, issue Certificates of Analysis, and monitor lab workflows from any AI agent.
Paycove
17 toolsAutomate smart quotes, invoice generation, and CPQ workflows directly from your CRM using AI agents.