4,000+ servers built on vurb.ts
Vinkius

Daytona (Dev Workspaces) MCP Server for VS Code CopilotGive VS Code Copilot instant access to 28 tools to Activate Snapshot, Archive Sandbox, Create Api Key, and more

MCP Inspector GDPR Free for Subscribers

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Ask AI about this MCP Server for VS Code Copilot

The Daytona (Dev Workspaces) MCP Server for VS Code Copilot 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.

GitHub Copilot Agent mode brings Daytona (Dev Workspaces) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 28 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot

When VS Code Copilot 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 VS Code Copilot via MCP

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

01

Create MCP config

Create a .vscode/mcp.json file in your project root
02

Add the server config

Paste the JSON configuration above
03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
04

Start using Daytona (Dev Workspaces)

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

Why Use VS Code Copilot with the Daytona (Dev Workspaces) MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Daytona (Dev Workspaces) through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Daytona (Dev Workspaces) + VS Code Copilot Use Cases

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

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Daytona (Dev Workspaces) in VS Code Copilot

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

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

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Daytona (Dev Workspaces) + VS Code Copilot FAQ

Common questions about integrating Daytona (Dev Workspaces) MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Explore More MCP Servers

View all →