How to Use the Daytona (Dev Workspaces) MCP in Cline

Let Cline build, test, and destroy isolated development environments automatically via this MCP Server during your VS Code sessions.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Daytona (Dev Workspaces) MCP to Cline

Create your Vinkius account to connect Daytona (Dev Workspaces) to Cline and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Daytona (Dev Workspaces) with Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

End-to-End Environment Provisioning

Cline builds full features, and now it builds the infrastructure to run them. When you assign a backend ticket, the agent invokes `create_sandbox` to spin up a clean Daytona workspace. It configures the runtime, writes the code, and tests the endpoints in total isolation. You never leave your editor. The agent handles the tedious setup phases, firing `get_sandbox` to verify the container state. If the environment needs a reboot after a heavy dependency install, it executes `stop_sandbox` followed by `start_sandbox` without missing a beat.

Workspace Cloning via MCP Server

Debugging production issues requires exact replicas of the failing environment. Cline uses `fork_sandbox` to duplicate an existing workspace perfectly, giving it a safe place to reproduce the bug and write the patch. This integration turns infrastructure chores into simple commands. Once the fix is verified, the agent cleans up its own mess by calling `delete_sandbox`, leaving your main development environments completely untouched.

API Key and Volume Management

Managing authentication tokens manually slows down automated testing. Your VS Code agent handles credential rotation by calling `create_api_key` for temporary access, then running `delete_api_key` the second the test suite finishes. Storage works the exact same way. Cline provisions isolated databases by triggering `create_volume` and attaching it to the current sandbox. It pulls the necessary details via `get_volume_by_name` to ensure the connection strings match the newly generated infrastructure.

Setup guide

Set up Daytona (Dev Workspaces) MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type daytona-dev-workspaces-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest Daytona (Dev Workspaces) refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

{
  "mcpServers": {
    "daytona-dev-workspaces-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Daytona. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Daytona (Dev Workspaces) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Daytona (Dev Workspaces) MCP in Cline

Open the Cline sidebar and click the MCP Servers icon. You can use the Remote Servers tab to add the Vinkius endpoint URL directly via streamable HTTP transport.

Your agent only manages the environments it creates for specific tasks. It lists active workspaces using `list_sandboxes`, but you can strictly prompt it to only modify or destroy sandboxes matching a specific naming convention.

It handles them perfectly. The agent spins up a fresh sandbox, attaches a volume, runs the full test suite, and tears the environment down afterward. You get the final diff and test results without cluttering your local machine.

When a web server starts inside the workspace, the agent calls `get_sandbox_preview_url`. It outputs the signed link directly in your VS Code chat so you can click and view the live application.

All operations execute within an ephemeral sandbox on the Vinkius platform. The server only transmits workspace IDs, snapshot metadata, and temporary API keys. Your actual source code stays between your editor and the remote environment.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript