How to use Fly.io with Copilot Studio
You want Fly.io inside Copilot Studio 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 Copilot Studio 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 Copilot Studio
Needs a Microsoft 365 subscription with access to Copilot Studio, plus an Arcade API key.
-
Add an MCP tool to your agent
In Copilot Studio, open your agent → Tools → Add a tool → Model Context Protocol → New tool.
-
Point it at your gateway
Give the server a name and description, put your gateway URL in Server URL, set Authentication to OAuth 2.0 and Type to Dynamic discovery.
-
Authorize and try it out
Saving redirects you to Arcade to approve access. Then start a conversation and use your Fly.io tools — Arcade authorizes each service just in time.
Full Copilot Studio guide in the docs steps verified 2026-08-13
Try these Fly.io prompts
Copilot Studio 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.