Publish it.
Ask your assistant for a page. Say publish it. A link comes back that anyone can open.
ridgeline-race.uholdco.space— visit a live published siteLive in seconds
The page is on the internet before you have finished reading the reply.
Its own address
Every site gets its own origin, so nothing you publish can reach anything else.
Nothing is lost
Every version is kept. Roll back to any of them, or delete the site outright.
How it works
Connect it once. After that, publishing is a sentence.
https://share-flame-nine.vercel.app/api/mcp
Add it to any assistant that takes custom MCP connectors — the guides cover Claude, ChatGPT and Cursor. Everything else happens in the conversation.
- 01
Connect once
Add the share endpoint to your assistant as a custom connector and sign in. No API key to paste, no token to keep in a note, nothing to install.
- 02
Ask for a site
Say what you want and end with “publish it”. The assistant writes the files, declares them to the server, and uploads the bytes straight to the edge.
- 03
Get a live URL
A verified, versioned site comes back in the reply. Say “roll that back” and the previous version is serving again in seconds.
One publish, start to finish
A request, three tool calls, and a URL that works.
What the public sees
- You: Make a one-page site for Saturday's trail race and publish it.
- Assistant: Writing it now — start times, the route map, and a link for parking.
- Tool call prepare_deployment: 3 files declared · server authorises exactly these (index.html 4.1 kB, style.css 1.2 kB, map.png 88.4 kB)
- Tool call PUT × 3: bytes go straight to the edge · SHA-256 recomputed on write
- Tool call finalize_deployment: 3 of 3 objects match the manifest · version marked live
- Published. Rolling back is one sentence away. The site is live at https://ridgeline-race.uholdco.space/
Your next page is one message away.
Free while it is new. Ten sites, 25 MB each, no card.
Start publishing