Official MCP RegistryListed
Flowershow
Publish Markdown and HTML from your AI session as a live website. No account needed.
First seen 25 Oct 2026. Evidence as of 12 Nov 2026.
5
Tools
From an anonymous probe
1
Source listings
Each with its own history
10
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| claim-site | Move an anonymous site published earlier in this conversation into the signed-in user's Flowershow account, so it no longer expires and can be updated with publish using siteId alone. Use when the user wants to keep a site that was published without an account. Needs the siteId and claimToken returned by that earlier publish. If the user is not signed in yet, calling it asks them to sign in to Flowershow first. | Changes data |
| list-files | List the files currently on one of the signed-in user's Flowershow sites: each path, its size in bytes and when it last changed. Use it before updating a site in a new conversation, to see which pages exist, pick the right paths to update or delete, and avoid duplicating a page under a new name. Get siteId from list-sites. Returns up to 1000 paths; for bigger sites, pass folder to list one folder at a time. If the user is not signed in yet, calling it asks them to sign in to Flowershow first. | Read-only |
| list-sites | List the sites in the signed-in Flowershow account and sites shared with it (role editor), with their siteId (use it with list-files to see what a site has, and with publish to update it), URL and when each was last published. If the user is not signed in yet, calling it asks them to sign in to Flowershow first. | Read-only |
| publish | Publish files as a live website on Flowershow and get a shareable URL. Use when the user says "publish this", "put this online", "make this a website", "share this as a page" or "host this". Accepts Markdown (.md, rendered as a styled page with navigation), HTML (.html, served as-is) and supporting files such as CSS, JS, JSON and images: one page or a small site, up to 50 files and 3 MB per call. Name the home page index.md or index.html. Anyone with the link can see what you publish. When you publish, tell the user every path you are sending (and any paths in delete) and which site they go to: a new site, or the one being updated. Stop and ask before calling publish only when it matters: a file looks private or sensitive (drafts, personal notes, keys or passwords, data with people's names or emails), the call removes files (with delete or replaceWholeSite) the user didn't ask to remove, it would create a new site when the user meant to update one, or the set of files differs from what the user asked to publish. If the user already named the files, asked for the removal or said to go ahead, that is their yes. Without an account this creates a new site that expires in 7 days and returns a claim link: always show the user the live URL and the claim link exactly as returned, so they can keep the site. To update that site later in the conversation, call publish again with its siteId and claimToken and only the files you changed or added: files you don't send are kept as they are. To remove pages or files, list their paths in delete (files can then be empty). Only when the user explicitly asks to start the site over, set replaceWholeSite to true: the files you send become the whole site and every other file is removed. If that would remove existing files, the call is refused and tells you how many and which; ask the user, then call again with confirmDeleteCount set to that number. To keep a site in the user's Flowershow account, call claim-site; to work with sites already in their account, use list-sites, list-files and read-file. Those tools ask the user to sign in to Flowershow first; after that, publish goes into their account. | Destructive |
| read-file | Get the current text of one file on one of the signed-in user's Flowershow sites, e.g. index.md. Use it before changing a page that is already on the site, then publish the whole updated file, so the parts you didn't mean to change stay as they are. Text files only (Markdown, HTML, CSS, JS, JSON, ...), up to 256 KB. Get siteId from list-sites and paths from list-files. If the user is not signed in yet, calling it asks them to sign in to Flowershow first. | Read-only |
Change history
- read-file: tool added
- publish: description changed (+"To keep a site in the user's Flowershow account, call claim-site; to work with sites already in their account, use list-sites, list-files and read-file. Those tools ask the user to sign in to Flowershow first; after that, publish goes into their account.")
- list-sites: tool added
- list-files: tool added
- claim-site: tool added
- publish: description changed (-"For bigger sites, suggest the Flowershow CLI (fl).")
- publish: description changed (+"Anyone with the link can see what you publish. When you publish, tell the user every path you are sending (and any paths in delete) and which site they go to: a new site, or the one being updated. Stop and ask before calling publish only when it matters: a file looks private or sensitive (drafts, personal notes, keys or passwords, data with people's names or emails), the call removes files (with delete or replaceWholeSite) the user didn't ask to remove, it would create a new site when the user meant to update one, or the set of files differs from what the user asked to publish. If the user already named the files, asked for the removal or said to go ahead, that is their yes.")
- publish: input schema changed (+confirmDeleteCount, +delete, +replaceWholeSite)
- publish: description changed (+"only" +"files you changed or added: files you don't send are kept as they are. To remove pages or files, list their paths in delete (files can then be empty). Only when the user explicitly asks to start the site over," +"replaceWholeSite to true:")
- Listed (registry)
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | app.flowershow/flowershow | 25 Oct 2026 | 12 Nov 2026 | 1 |