4,000+ servers built on vurb.ts
Vinkius
Claude DesktopIDE
Daytona (Dev Workspaces) MCP Server

Bring Sandboxes
to Claude Desktop

Learn how to connect Daytona (Dev Workspaces) to Claude Desktop and start using 28 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Activate SnapshotArchive SandboxCreate Api KeyCreate SandboxCreate SnapshotCreate VolumeDeactivate SnapshotDelete Api KeyDelete SandboxDelete SnapshotDelete VolumeFork SandboxGet Api KeyGet Current Api KeyGet SandboxGet Sandbox Preview UrlGet SnapshotGet VolumeGet Volume By NameList Api KeysList SandboxesList Sandboxes PaginatedList SnapshotsList VolumesRecover SandboxResize SandboxStart SandboxStop Sandbox

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Daytona (Dev Workspaces)

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_snapshot and activate_snapshot.
  • API Key Control — Manage your authentication keys directly, including listing and creating new access tokens via list_api_keys and create_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

  1. Subscribe to this server
  2. Enter your Daytona API Key
  3. 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_snapshot

Activate a snapshot

archive_sandbox

Archive a sandbox

create_api_key

Create a new Daytona API key

create_sandbox

Create a new Daytona sandbox

create_snapshot

Create a new snapshot

create_volume

Create a new volume

deactivate_snapshot

Deactivate a snapshot

delete_api_key

Delete an API key by name

delete_sandbox

Delete a sandbox

delete_snapshot

Delete a snapshot

delete_volume

Delete a volume

fork_sandbox

Fork an existing sandbox

get_api_key

Get details of a specific API key by name

get_current_api_key

Get details of the currently authenticated API key

get_sandbox

Get details of a specific sandbox

get_sandbox_preview_url

Get a signed preview URL for a specific port on a sandbox

get_snapshot

Get details of a specific snapshot

get_volume

Get details of a specific volume by ID

get_volume_by_name

Get details of a specific volume by name

list_api_keys

List Daytona API keys

list_sandboxes

List all Daytona sandboxes

list_sandboxes_paginated

List all Daytona sandboxes (paginated)

list_snapshots

List all Daytona snapshots

list_volumes

List all Daytona volumes

recover_sandbox

Recover a sandbox from an error state

resize_sandbox

Resize sandbox resources

start_sandbox

Start a stopped sandbox

stop_sandbox

Stop a running sandbox

Why Claude Desktop?

Claude Desktop is the definitive way to connect Daytona (Dev Workspaces) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 28 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

  • Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

  • Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

  • Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

  • Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

See it in action

Daytona (Dev Workspaces) in Claude Desktop

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Daytona (Dev Workspaces) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Daytona (Dev Workspaces) to Claude Desktop 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Daytona (Dev Workspaces) in Claude Desktop

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 Claude Desktop 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.

Daytona (Dev Workspaces)
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

The Vinkius Advantage

How Vinkius secures Daytona (Dev Workspaces) for Claude Desktop

Every tool call from Claude Desktop to the Daytona (Dev Workspaces) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

05

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

06

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

07

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

08

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

09

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

10

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

11

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Explore More MCP Servers

View all →