4,000+ servers built on vurb.ts
Vinkius

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

MCP Inspector GDPR Free for Subscribers

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Daytona (Dev Workspaces) through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

Ask AI about this MCP Server for Cline

The Daytona (Dev Workspaces) MCP Server for Cline 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": {
      "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.

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Daytona (Dev Workspaces) tool calls without waiting for prompts between steps. Connect 28 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

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 Cline 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 Cline

When Cline 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 Cline via MCP

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

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel
02

Add remote server

Click "Add MCP Server" and paste the configuration above
03

Enable the server

Toggle the server switch to ON
04

Start using Daytona (Dev Workspaces)

Ask Cline: "Using Daytona (Dev Workspaces), help me...". 28 tools available

Why Use Cline with the Daytona (Dev Workspaces) MCP Server

Cline provides unique advantages when paired with Daytona (Dev Workspaces) through the Model Context Protocol.

01

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

Daytona (Dev Workspaces) + Cline Use Cases

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

01

Autonomous feature building: tell Cline to fetch data from Daytona (Dev Workspaces) and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use Daytona (Dev Workspaces) tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from Daytona (Dev Workspaces) and generates snapshot tests or mocks based on actual payloads

04

Incident response: query Daytona (Dev Workspaces) for real-time status and let Cline generate hotfix patches based on the findings

Example Prompts for Daytona (Dev Workspaces) in Cline

Ready-to-use prompts you can give your Cline 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 Cline

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

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

Daytona (Dev Workspaces) + Cline FAQ

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

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Explore More MCP Servers

View all →