Deploy from a chat app

flypod is also a remote MCP server. Add it to an AI app as a connector and the app can publish what it just made to a live URL, with no terminal and no account.

https://flypod.dev/mcp

Add the connectorCopy Anchor Link

Then ask for what you want: "publish this page", "put this report online and give me the link".

ToolsCopy Anchor Link

That is everything the CLI and the account page can do to a site. Two things are left out on purpose, because a tool call is the wrong place for them: deleting your account and changing its password.

The tools marked "No" work on temporary sites with the site_id and manage_token that deploy_site returned. The ones marked "Yes" act as your flypod account, so the connector has to be signed in.

deploy_site takes files, a map from path to text content, and optionally binary_files, a map from path to base64 for small images:

{
  "files": {
    "index.html": "<!doctype html><title>Report</title><h1>Q3 report</h1>",
    "css/site.css": "body { font-family: system-ui }"
  }
}

It returns the URL plus a site_id and a manage_token. The other site tools need both while the site is temporary, so the app keeps them for the conversation. A site made in one conversation cannot be changed from another unless you carry those two values over.

What to expectCopy Anchor Link

• Temporary by default. A site made this way is public and is removed after 14 days, like any deploy without an account. See Keep a site.
• Limits. 200 files and 4 MB per deploy through the connector. The model writes every byte as tool input, so one self-contained HTML file is the most reliable thing to publish.
• The same rules as the CLI. Deploys through the connector go through the same rate limit and content screening as any other.
• Static files only. No build step and no server code.

Keep a siteCopy Anchor Link

A site published from a chat is temporary. The result of deploy_site includes a keep_url, and the app will usually show it to you:

https://flypod.dev/keep#a3f1c2d4e5b60789.…

Open it, sign in, and press Keep this site. The expiry is removed, the address stays the same, and the site appears on your account page. No terminal is involved.

The part after # is what proves the site is yours to keep, so treat the link like a password until you have used it. Browsers never send that part to a server.

Make every deploy yours, with a tokenCopy Anchor Link

To make deploys through the connector belong to your account and never expire, configure the connector to send your flypod session token (the same login session the CLI uses as FLYPOD_TOKEN; there are no separate API keys):

claude mcp add --transport http flypod https://flypod.dev/mcp \
  --header "Authorization: Bearer $FLYPOD_TOKEN"

This works in clients that let you set a request header. Apps that only offer "no sign in" create temporary sites, and each one can still be kept with its keep link.

Signed in, a site needs only its site_id: the account is what authorizes changes, and a site you keep with keep_site stops accepting its old manage_token. Signed-in deploys are owned from the start, so their result has no keep_url. The connector only ever forwards the Authorization header you configure, never browser cookies, so being signed in to flypod.dev in a browser does not sign the connector in.

Comments from a chatCopy Anchor Link

With the connector signed in as a site's owner, an AI app can run the review loop on a deployed page:

1. configure_comments turns comments on, in anonymous, passcode (with a passcode) or approved mode.
2. Reviewers comment on the page itself.
3. list_comments returns each thread with the passage it is attached to. With status: "pending" it returns the moderation queue.
4. The app fixes what was asked, calls update_site, replies with reply_to_comment, and closes the thread with update_comment_thread (action: "resolve"). In approved mode, the same tool's approve and reject actions decide the queue.

Next stepsCopy Anchor Link

• Deploy from an AI agent for agents that have a terminal.
• The HTTP API.