flyio logo VS Code

How to use Fly.io with VS Code

You want Fly.io inside VS 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 VS 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.

  1. Create an Arcade account

    Sign up and open the dashboard. The free tier is enough to follow this through.

  2. 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.

  3. Copy your gateway URL

    Every client below needs it.

    https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>

Create a Fly.io gateway Opens the gateway builder in your Arcade dashboard.

Connect the gateway to VS Code

  1. Add the server

    VS Code 1.107.0 or higher. Command Palette → MCP: Add Server… → choose HTTP, paste your gateway URL, and name it something like mcp-arcade.

  2. Start it and authenticate

    Click Start next to the server in mcp.json or under Extensions → MCP Servers - Installed, then approve the Arcade sign-in and consent screens.

  3. Try it out

    Open the chat pane, switch to Agent mode, and ask it to use one of your Fly.io tools.

Full VS Code guide in the docs steps verified 2026-08-13

Try these Fly.io prompts

VS 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.

Ready to actually ship your agent?

Free to start. Ready for enterprise when you are.