Claude Code How to use Fly.io with Claude Code
You want Fly.io inside Claude Code so it can inspect unhealthy deployments, roll out a new container image, rotate application secrets, and clean up unused infrastructure — without you copy-pasting between tabs. Here is the whole setup, once.
Create your Fly.io gateway
The gateway is the thing Claude Code connects to, and it is where you decide which Fly.io 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 Fly.io tools
In the dashboard, create a gateway and pick the Fly.io 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 Fly.io tools.
Full Claude Code guide in the docs steps verified 2026-08-13
Try these Fly.io prompts
Claude Code can now act on your Fly.io account. Click a prompt to copy it.
Use a credential with only the Fly.io access the agent needs, and require approval before deploying, changing secrets, scaling, or destroying Machines and volumes. Pair it with Contextual Access policies so read-only troubleshooting does not grant permission to make production changes.
