Claude Code How to use Daytona with Claude Code
You want Daytona inside Claude Code so it can run and inspect code in an isolated sandbox, review a repository change before pushing it, prepare a branch with a targeted fix, and run a long-lived development process — without you copy-pasting between tabs. Here is the whole setup, once.
Create your Daytona gateway
The gateway is the thing Claude Code connects to, and it is where you decide which Daytona tools an agent may use. You create it once and every client reuses it.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
Create an MCP Gateway and select your Daytona tools
In the dashboard, create a gateway and pick the Daytona tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.
-
Copy your gateway URL
Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
Connect the gateway to Claude Code
-
Add the gateway as a remote HTTP MCP server
claude mcp add arcade --transport http "<YOUR_ARCADE_GATEWAY_URL>"
-
Verify it was added
claude mcp get arcade claude mcp list
-
Try it out
Open Claude Code in your project and ask it to use one of your Daytona tools.
Full Claude Code guide in the docs steps verified 2026-08-13
Try these Daytona prompts
Claude Code can now act on your Daytona account. Click a prompt to copy it.
Running code, deleting files, and pushing commits can change a project or its remote repository. Use tool permissions with Contextual Access policies to limit which actions an agent can take and require approval for consequential changes.
