Publish from Claude and ChatGPT

Flowershow has an MCP server, so chat apps that can't run the fl CLI can still publish. Add it as a connector, then ask your AI to "publish this" or "put this online". It sends the page or small site it made to Flowershow and gives you back a live link.

The connector URL is https://flowershow.app/api/mcp. You don't need an account to start:

	What you get
Without an account	Each new site gets a random `…-anon.flowershow.me` address and a claim link. Open the claim link and sign in (or sign up) to keep the site; otherwise it expires after 7 days.
Signed in	You sign in to Flowershow once. Your AI publishes new sites to your account, lists your sites, and updates them in any conversation.

Your AI asks you to sign in the first time it needs your account: when you ask it to keep a site, or to find or change one of your sites.

What you can do

Share what you just made. A report, a one-pager, an HTML page: ask your AI to publish it and get a link you can send.
Change it as you go. Ask for edits and they go live at the same address. Signed in, you can come back to a site in a new conversation.
Keep it. Sites you publish signed in are normal Flowershow sites in your dashboard: rename them, add a custom domain, or keep editing them with the fl CLI or GitHub.

Add it to Claude

Works in claude.ai, Claude Desktop and Claude mobile, on every plan (the Free plan allows one custom connector).

Open Settings → Connectors and choose Add custom connector.
Name it Flowershow and enter the URL https://flowershow.app/api/mcp. Leave the advanced settings (OAuth client ID and secret) empty.
In a chat, make sure the Flowershow connector is turned on in the tools menu.

When your AI first needs your account, Claude shows a Connect button in the chat. A Flowershow window opens: sign in (or sign up) with GitHub, Google or an email link, check that the account shown is yours, and choose Allow. Claude then carries on with what you asked.

If you added Flowershow with https://flowershow.app/api/mcp/account before, remove it and add https://flowershow.app/api/mcp instead.

Add it to ChatGPT

Custom connectors need ChatGPT Plus, Pro, Business, Enterprise or Edu, on the web.

Open Settings → Security and login and turn on Developer mode.
Add a new app (connector) with the URL https://flowershow.app/api/mcp and authentication set to OAuth.
A Flowershow window opens: sign in, check that the account shown is yours, and choose Allow.
In a chat, enable the Flowershow app from the tools menu. ChatGPT asks you to confirm before each publish.

To publish without an account, set authentication to No authentication instead.

Use it

Ask in your own words, for example:

Make a one-page site about our team offsite with the agenda and a map, and publish it.

Publish this report as a website.

Add a page with last week's numbers to my team site.

When it publishes, your AI tells you which files it is sending and to which site. It stops to check with you first if a file looks private (drafts, personal notes, keys, data with names or emails), if the publish would delete files you didn't ask it to remove, if it would create a new site when you meant to update one, or if the files differ from what you asked for. If you've already named the files or said to go ahead, it publishes straight away.

Your AI replies with the live link. To change the site, ask it to update the page: it republishes to the same address. An update sends only the files that changed and keeps the rest of the site as it is. To remove a page, ask your AI to delete it; to start the site over, ask it to replace the whole site (it checks with you first if that would remove existing files).

Signed in, your AI can find your sites in any conversation, including sites shared with you as an editor. Before changing a site it sees which files the site has and reads a page's current text, so it adds or edits pages and leaves the rest as it was.

Without an account, your AI also gives you a claim link. A new conversation creates a new site, and once you've claimed a site with the claim link your AI can update it only after you sign in. So make your changes first, then claim the site when you're happy with it, or ask your AI to keep it.

If the site was published from the CLI, Obsidian or GitHub, pages your AI adds through the connector are removed the next time you publish from that source, because it publishes your folder or repo as the whole site.

What you can publish

Markdown (.md) pages, rendered with a theme and navigation, and HTML (.html) pages served as they are. See Supported file types.
Supporting files such as CSS, JavaScript, JSON and images.
Up to 50 files and about 3 MB per publish. For bigger sites, use the fl CLI.
Hidden files and folders (names starting with .) aren't published.

Keep a site published without an account

Open the claim link the AI gave you, sign in or sign up, and choose Add to my account. The site is then permanent and appears in your dashboard, where you can rename it, add a custom domain and change its settings. The claim link is a secret: anyone who has it can take or overwrite the site until it's claimed.

You can also ask your AI to keep the site: it asks you to sign in, then moves the site into your account.

Disconnect

Open Access tokens in your dashboard and choose Revoke next to the app under Connected apps. The app can no longer reach your account; to use it again, connect it and allow it again.

Other MCP clients

MCP clients that support sign-in, such as Claude Code, can use https://flowershow.app/api/mcp the same way (in Claude Code, run /mcp to sign in). From clients that only let you set request headers, use a personal access token instead. For example, in Claude Code's .mcp.json:

{
  "mcpServers": {
    "flowershow": {
      "type": "http",
      "url": "https://flowershow.app/api/mcp",
      "headers": { "Authorization": "Bearer fs_pat_…" }
    }
  }
}

With a token, the connector works as if you were signed in. In local agents with a terminal, the Flowershow skill and fl are usually the better fit.

Tools

"Signed in" means you signed in through the connector or use a personal access token. The tools marked "Signed in" ask you to sign in first.

Tool	What it does
`publish`	Publishes files (text, or base64 for binary). Without `siteId`: creates a new site, in your account when signed in; otherwise it returns `liveUrl`, `claimUrl`, `claimToken` and `expiresAt`. With `siteId` (plus `claimToken` when not signed in): adds or updates the files sent and keeps the others. `delete` lists paths to remove; `replaceWholeSite: true` makes the files sent the whole site, removing everything else. If that would remove existing files, the call is refused with the count and paths, and goes ahead only when repeated with `confirmDeleteCount` set to that count.
`list-sites`	Signed in: lists your sites, and sites shared with you as an editor, with their `siteId`, URL, `role` (`owner` or `editor`) and `owner` username.
`list-files`	Signed in: lists the files on one of your sites or a site shared with you (`siteId`) with their size and last change. Returns up to 1,000 paths; `folder` lists one folder.
`read-file`	Signed in: returns the current text of one file (`siteId`, `path`), so the AI can change a page without losing what's on it. Text files only (Markdown, HTML, CSS, JSON, …), up to 256 KB.
`claim-site`	Signed in: moves a site published without an account earlier in the conversation (`siteId` and `claimToken`) into your account, so it no longer expires.