4,000+ servers built on vurb.ts
Vinkius

Daytona (Dev Workspaces) MCP Server for Claude DesktopGive Claude Desktop instant access to 28 tools to Activate Snapshot, Archive Sandbox, Create Api Key, and more

MCP Inspector GDPR Free for Subscribers

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Ask AI about this MCP Server for Claude Desktop

The Daytona (Dev Workspaces) MCP Server for Claude Desktop is a standout in the Developer Tools category — giving your AI agent 28 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "daytona-dev-workspaces": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Daytona (Dev Workspaces) and 4,000+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
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

About 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.

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.

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.

The Daytona (Dev Workspaces) MCP Server exposes 28 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 28 Daytona (Dev Workspaces) tools available for Claude Desktop

When Claude Desktop connects to Daytona (Dev Workspaces) through Vinkius, your AI agent gets direct access to every tool listed below — spanning sandboxes, dev-environments, workspace-automation, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

activate

Activate snapshot on Daytona (Dev Workspaces)

Activate a snapshot

archive

Archive sandbox on Daytona (Dev Workspaces)

Archive a sandbox

create

Create api key on Daytona (Dev Workspaces)

Create a new Daytona API key

create

Create sandbox on Daytona (Dev Workspaces)

Create a new Daytona sandbox

create

Create snapshot on Daytona (Dev Workspaces)

Create a new snapshot

create

Create volume on Daytona (Dev Workspaces)

Create a new volume

deactivate

Deactivate snapshot on Daytona (Dev Workspaces)

Deactivate a snapshot

delete

Delete api key on Daytona (Dev Workspaces)

Delete an API key by name

delete

Delete sandbox on Daytona (Dev Workspaces)

Delete a sandbox

delete

Delete snapshot on Daytona (Dev Workspaces)

Delete a snapshot

delete

Delete volume on Daytona (Dev Workspaces)

Delete a volume

fork

Fork sandbox on Daytona (Dev Workspaces)

Fork an existing sandbox

get

Get api key on Daytona (Dev Workspaces)

Get details of a specific API key by name

get

Get current api key on Daytona (Dev Workspaces)

Get details of the currently authenticated API key

get

Get sandbox on Daytona (Dev Workspaces)

Get details of a specific sandbox

get

Get sandbox preview url on Daytona (Dev Workspaces)

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

get

Get snapshot on Daytona (Dev Workspaces)

Get details of a specific snapshot

get

Get volume on Daytona (Dev Workspaces)

Get details of a specific volume by ID

get

Get volume by name on Daytona (Dev Workspaces)

Get details of a specific volume by name

list

List api keys on Daytona (Dev Workspaces)

List Daytona API keys

list

List sandboxes on Daytona (Dev Workspaces)

List all Daytona sandboxes

list

List sandboxes paginated on Daytona (Dev Workspaces)

List all Daytona sandboxes (paginated)

list

List snapshots on Daytona (Dev Workspaces)

List all Daytona snapshots

list

List volumes on Daytona (Dev Workspaces)

List all Daytona volumes

recover

Recover sandbox on Daytona (Dev Workspaces)

Recover a sandbox from an error state

resize

Resize sandbox on Daytona (Dev Workspaces)

Resize sandbox resources

start

Start sandbox on Daytona (Dev Workspaces)

Start a stopped sandbox

stop

Stop sandbox on Daytona (Dev Workspaces)

Stop a running sandbox

Connect Daytona (Dev Workspaces) to Claude Desktop via MCP

Follow these steps to wire Daytona (Dev Workspaces) into Claude Desktop. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json
02

Add the MCP Server

Paste the configuration above into the mcpServers section
03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server
04

Start using Daytona (Dev Workspaces)

Look for the 🔌 icon in the chat. your 28 tools are now available

Why Use Claude Desktop with the Daytona (Dev Workspaces) MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Daytona (Dev Workspaces) through the Model Context Protocol.

01

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

02

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

03

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

04

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

Daytona (Dev Workspaces) + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Daytona (Dev Workspaces) MCP Server delivers measurable value.

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Example Prompts for Daytona (Dev Workspaces) in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Daytona (Dev Workspaces) immediately.

01

"List all my current Daytona sandboxes."

02

"Create a new sandbox with 2 CPUs and 4GB of RAM using the node:20 image."

03

"Stop the sandbox named 'dev-environment-1'."

Troubleshooting Daytona (Dev Workspaces) MCP Server with Claude Desktop

Common issues when connecting Daytona (Dev Workspaces) to Claude Desktop through Vinkius, and how to resolve them.

01

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).
02

Authentication error

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

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.

Daytona (Dev Workspaces) + Claude Desktop FAQ

Common questions about integrating Daytona (Dev Workspaces) MCP Server with Claude Desktop.

01

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.
02

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.
03

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.
04

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.
05

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.

Explore More MCP Servers

View all →