Skip to content
Daytona MCP Server

Daytona MCP Server

by Daytona
Released
10 views
Repository Docs
Developer Tools

Summary

Daytona's official MCP server: give an agent a disposable cloud sandbox with a file system, git, process execution, computer use and a live preview URL.

Features

  • Create and tear down isolated cloud sandboxes on demand
  • File system and git operations inside the sandbox
  • Run processes and code, and read back their output
  • Computer use for driving a GUI in the sandbox
  • Preview URLs so a human can see what the agent just started

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it, filling in the environment variables with your own values.
  3. Restart the agent — the "Daytona MCP Server" tools will be available.
{
  "mcpServers": {
    "daytona-mcp": {
      "command": "daytona",
      "args": [
        "mcp",
        "start"
      ],
      "env": {
        "HOME": "${HOME}",
        "PATH": "${HOME}:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
      }
    }
  }
}

Description

Daytona's official MCP server hands an AI agent its own isolated cloud sandbox — a real machine to run code on, rather than a description of one.

The tools cluster into six areas: sandbox management (create, list and tear down environments), file system operations (read, write and move files inside the sandbox), git operations (clone, branch, commit), process and code execution (run commands and scripts and read their output), computer use (drive a GUI inside the sandbox), and preview (get a public URL for a service the agent has just started, so a human can look at what was built).

The distinction that matters is where the code runs. Executing agent-written code on the developer's own laptop means the agent inherits the developer's credentials, SSH keys and file system. A Daytona sandbox is created for the task, has only what you put in it, and is thrown away afterwards — which makes it a reasonable place to run something you have not read yet.

Setup

Install the CLI (brew install daytonaio/cli/daytona on macOS and Linux, or irm https://get.daytona.io/windows | iex on Windows), authenticate with daytona login, then wire up your client with daytona mcp init claude, daytona mcp init cursor or daytona mcp init windsurf. daytona mcp config prints the JSON block if you would rather paste it yourself. A Daytona account is required.

Related MCP Servers

MCP: Mux MCP Server

by Mux

Featured

Official MCP server for the Mux video API, built on a code-execution scheme: the agent writes TypeScript against the SDK and runs it in a Deno sandbox.

Developer Tools
9 views

MCP: ripwire

by Red Hat

Featured

Red Hat's zero-dependency C++23 code-context engine — ranked call graphs and blast-radius analysis, indexing a repo in under half a second with no server and no database.

Developer Tools
10 views

MCP: Graft

by Trail

Featured

Builds a searchable markdown graph of your repo so coding agents stop re-exploring it on every task — reported 42% fewer tokens and 46% fewer tool calls.

Developer Tools
8 views

MCP: Expo MCP Server

by Expo

Featured

Expo's official remote MCP server — searches Expo docs, installs compatible SDK packages, triggers and monitors EAS builds, and drives iOS/Android simulators.

Developer Tools
7 views
Browse all MCP servers →