Daytona

Created By
Daytonaa year ago
Run code in secure remote sandboxes
Overview

what is Daytona?

Daytona is a platform that allows users to run code in secure remote sandboxes, enabling AI agents to execute commands and manage files in a controlled environment.

how to use Daytona?

To use Daytona, you need to install the Daytona CLI, log in to your Daytona account, and initialize the Daytona MCP server with a compatible AI agent. You can then execute various commands to manage sandboxes and files.

key features of Daytona?

  • Sandbox management (create and destroy sandboxes)
  • Execute commands in a secure environment
  • File operations including upload, download, and delete
  • Generate preview links for web applications running in sandboxes

use cases of Daytona?

  1. Running isolated code for testing and development.
  2. Managing files and executing commands in a secure environment.
  3. Collaborating with AI agents for enhanced productivity.

FAQ from Daytona?

  • What is required to use Daytona?

You need a Daytona account, the Daytona CLI installed, and a compatible AI agent.

  • Can I run any code in Daytona?

Yes, you can execute shell commands in the Daytona sandbox environment.

  • How do I troubleshoot issues with Daytona?

Check your authentication, ensure proper configuration, and verify sandbox status using the CLI.

Server Config

{
  "mcpServers": {
    "daytona-mcp": {
      "command": "daytona",
      "args": [
        "mcp",
        "start"
      ],
      "env": {
        "HOME": "${HOME}",
        "PATH": "${HOME}:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/homebrew/bin"
      },
      "logFile": "${HOME}/Library/Logs/daytona/daytona-mcp-server.log"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Daytona
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

8 hours ago