Your agent writes the code.Now it can ship it.

Connect Claude Code, Codex, Cursor or VS Code to Flux with one command and sign in once in your browser. Then ask for what you want: a site on Drop, an app on Orbit.

For you

Paste this into your agent

It connects itself, signs you in, and deploys the project you have open.

Connect to the Flux MCP server (setup guide: https://runonflux.com/apps/mcp.md), then deploy this project: a static site goes on Drop, anything with a server goes on Orbit. Give me the live link when it is up.

For your agent

A guide written for agents

How to connect, which product to choose, every tool and its rules. Agents read it from this address.

https://runonflux.com/apps/mcp.md
Open the guide

Connect in a minute

One address for every agent: https://runonflux.com/apps/mcp. No API key: you sign in through your browser.

  1. 1. Add the server

    One command or one click in your agent. No key to create, nothing to copy.

  2. 2. Sign in to Flux

    Your browser opens the Flux sign-in page on drop.app.runonflux.io. Sign in with Google or your email and check which agent is asking.

  3. 3. Allow it

    The agent can now work on your Orbit apps and Drop sites. Disconnect it here any time.

Terminal
claude mcp add --transport http flux https://runonflux.com/apps/mcp

Then run /mcp in Claude Code, pick flux and choose Authenticate. Your browser opens the Flux sign-in.

Then just ask

Click a prompt to copy it. Your agent picks the right tools and asks you before anything costs money or deletes something.

Drop: static sites

HTML, a built React or Vue app, a folder or a ZIP. Free, live in seconds.

Orbit: apps with a server

Node, Python, Go, PHP and more, built from your Git repository.

With Drop, it can

  • List and read your sites
  • Publish a page, a few files, or a ZIP of up to 50 MiB
  • Replace a site's content, keeping its link
  • Rename a site, make it private or public
  • Delete a site, after asking you

With Orbit, it can

  • Analyze a repository against Orbit's rules
  • List your apps, their nodes, status and logs
  • Validate and deploy an app
  • Build, restart, stop or redeploy instances
  • Change settings and resources, renew a subscription

And you stay in charge

  • Payments stay with you: the agent gets a Stripe checkout link and you pay in your browser.
  • It only sees apps and sites in your account.
  • Deleting a Drop site needs its exact name, so the agent has to ask you first.
  • Your password never reaches the agent, and you can disconnect it here at any time.

Your connected agents

Each one keeps working until you disconnect it, or after 30 days without use.

Manual setup, for agents without browser sign-in

This configuration carries a token that acts as you for about an hour, then stops. Treat it like a password and generate a new one when it expires. Browser sign-in above lasts and renews itself.

Questions

Which agents work?

Any MCP client that supports remote servers with sign-in: Claude Code, Codex, Cursor, VS Code, claude.ai and Claude Desktop, and others. They all use the same address.

Which account do I sign in with?

Your Flux account, with Google or a verified email and password. Drop's tools need a Google account; Orbit's work with either. Wallet-only accounts cannot connect an agent yet.

Why does sign-in open drop.app.runonflux.io?

Flux Drop runs the sign-in for every Flux agent: it keeps your connections and hands your agent short-lived access. It is the same Flux account as runonflux.com.

How long does the connection last?

As long as the agent keeps using it. It renews itself every hour, and lapses after 30 days without use, if you reset your password, or when you disconnect it.

What does it cost?

Connecting is free, and so is Drop. Orbit apps cost what their plan costs; the agent can prepare a checkout, but only you can pay it.

Which files can Drop host?

Static files only: HTML, CSS, JavaScript, JSON, images, fonts, audio, video, PDF and WebAssembly. Source maps, README files, hidden files and files without an extension are refused, and one of them fails the whole upload, so the agent leaves them out. Sites run sandboxed: no cookies or local storage, no pop-ups or downloads.

My agent cannot open a browser.

Run the add command again; most clients then print the sign-in link to open yourself. For a client without sign-in support, use the manual setup below.