← All integrations

Fly.io MCP server

54 operations0 webhooks

Manage Fly.io apps, Machines, volumes, secrets, certificates and IP addresses through Fly's public Machines REST API.

Try Fly.io with your agent

Connect Fly.io, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Fly.io on my account, then run one read-only example and show me the result.

Runs once, when you ask

Fly.io tools and triggers

Tools are what your agent can do in Fly.io through Corsair's MCP server. Triggers are the Fly.io events a routine can start from.

Machines

  • CordonWrite

    Cordon a Machine so Fly Proxy stops routing requests to it

    machines.cordon

  • CreateDestructive

    Create (and by default start) a Machine. Fly bills it while it runs and for its root filesystem.

    machines.create

  • Create LeaseWrite

    Take (or, with lease_nonce, refresh) an exclusive lease on a Machine

    machines.createLease

  • DeleteDestructive

    Permanently destroy a Machine. It must be stopped unless force is true.

    machines.delete

  • Delete Metadata KeyDestructive

    Delete one metadata key from a Machine

    machines.deleteMetadataKey

  • ExecDestructive

    Run a command inside a running Machine and return its stdout, stderr and exit code

    machines.exec

  • GetRead-only

    Get a Machine

    machines.get

  • Get LeaseRead-only

    Get the lease currently held on a Machine

    machines.getLease

  • Get MetadataRead-only

    Get a Machine's metadata key/value pairs

    machines.getMetadata

  • Get Metadata KeyRead-only

    Get one metadata value of a Machine

    machines.getMetadataKey

  • ListRead-only

    List an app's Machines (all of them; use listForOrg to page through an organization)

    machines.list

  • List EventsRead-only

    List a Machine's recent events, newest first

    machines.listEvents

Connect Fly.io to Claude, ChatGPT or Cursor

  1. 1

    Connect Fly.io in Corsair

    Add your Fly.io API key once in Corsair. Corsair stores the credential encrypted and makes the Fly.io API calls for your agent, so it never goes into a prompt or a config file. Connect Fly.io

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Fly.io. On a ChatGPT personal plan, connect Fly.io here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Fly.io's read and write operations run right away and its 19 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/fly, add the Fly.io plugin, and connect with an API key. Then call methods like corsair.fly.api.apps.create() from your app. Corsair keeps each tenant isolated.

Yes. Fly.io requires an API key from your Fly.io account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Fly.io, GitHub, Notion, Stripe, and the rest. Trigger Fly.io from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for manage Fly.io apps, Machines, volumes, secrets, certificates and IP addresses through Fly's public Machines REST API. Common builds include sync jobs, admin tooling, and agents that call Fly.io APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Fly.io API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/fly in the open repo. When Fly.io ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Fly.io data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Fly.io data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Fly.io on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 19 destructive Fly.io operations. You can change a link's mode at hub.corsair.dev/me.