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

Q: How do I connect Daytona (Dev Workspaces) to Windsurf?

Open your mcpconfig.json file in the .codeium/windsurf directory. Add the server URL under the mcpServers section and hit refresh in your MCP panel. Cascade will auto-discover the sandbox tools immediately.

Give Cascade the power to spin up, resize, and tear down ephemeral development environments directly inside Windsurf.

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 Windsurf

Create your Vinkius account to connect Daytona (Dev Workspaces) to Windsurf 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 Windsurf

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous Sandbox Management in Windsurf

Cascade doesn't wait for you to provision infrastructure. When a task requires a clean environment, your agent uses `create_sandbox` to spin up a fresh workspace. It pulls the repository, sets up the dependencies, and gets straight to work without asking for permission. You just set the goal. The agent chains these operations naturally, calling `start_sandbox` if an existing environment went to sleep. Once the code runs successfully, it can even trigger `archive_sandbox` to keep your resource usage low.

Persistent Volumes and Snapshots

Ephemeral environments usually lose state, but this MCP server changes that rule. Cascade calls `create_volume` to attach persistent storage before running heavy database migrations or caching large npm modules. State recovery happens automatically. If your agent breaks something during a test run, it fires `activate_snapshot` to roll the workspace back to a known good state. It handles the `get_snapshot` checks in the background while you review the code changes.

Dynamic Resource Scaling

Sometimes a build needs more RAM than your default template provides. Instead of failing the task, Cascade detects the memory error and calls `resize_sandbox` to allocate more CPU or memory on the fly. Everything happens within the IDE context. Your agent grabs a signed URL via `get_sandbox_preview_url` to verify the frontend render, confirms the build passes, and scales the resources back down using `stop_sandbox` when the job finishes.

Setup guide

Set up Daytona (Dev Workspaces) MCP in Windsurf

Prerequisites

Windsurf IDE installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Click the Cascade assistant icon in the sidebar, then click the hammer icon (🔨) at the top of the panel. Select "Configure" to open ~/.codeium/windsurf/mcp_config.json.
2

Add the Daytona (Dev Workspaces) MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Refresh MCPs

Go back to the hammer icon (🔨) in Cascade and click "Refresh". Windsurf will detect the new server. No full restart is needed — the connection is hot-reloaded.
4

Verify in Cascade

Start a new Cascade conversation and ask something like "Show my Daytona (Dev Workspaces) payment history." If connected, Cascade will call the Daytona (Dev Workspaces) tools directly. You will see a green dot next to the server name in the MCP panel.

mcp_config.json

{
  "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 Windsurf

Open your mcp_config.json file in the .codeium/windsurf directory. Add the server URL under the mcpServers section and hit refresh in your MCP panel. Cascade will auto-discover the sandbox tools immediately.

Yes. Cascade excels at multi-step planning. It will create a volume, attach it to a new sandbox, and start the environment without needing a prompt for each step.

Your AI client monitors the environment state. If it detects a failure, it triggers `recover_sandbox` to pull the workspace out of the error state and resume the task.

It handles previews perfectly. The agent generates a secure link using `get_sandbox_preview_url` so you can see the running application on a specific port before approving the code changes.

Vinkius runs the server inside a zero-trust V8 Isolate. The connection only passes API keys, volume IDs, and sandbox metadata required to manage your ephemeral environments. No raw code or database contents route through the transport layer.

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