Compatible with every major AI agent and IDE
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 VS Code Copilot?
GitHub Copilot Agent mode brings Daytona (Dev Workspaces) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 28 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Daytona (Dev Workspaces) in VS Code Copilot
Daytona (Dev Workspaces) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Daytona (Dev Workspaces) to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
RMSE & MAE Calculator
1 toolsCompute exact Root Mean Square Error (RMSE) and Mean Absolute Error (MAE) for regression models. Stop hallucinating model validation metrics.

Pingdom
10 toolsMonitor website uptime and performance via Pingdom — list checks, track response times, and manage alerts directly from any AI agent.

Healthchecks.io
13 toolsMonitor cron jobs and background tasks via Healthchecks.io — list checks, track pings, and manage alerts directly from any AI agent.

PostHog
10 toolsAnalyze product data via PostHog — list insights, track persons, inspect feature flags, and monitor experiments directly from any AI agent.
