just-publish

Just Publish — put a static website online

Just Publish (https://justpublish.ai) turns static files into a live website at https://{slug}.justpublish.site/. Publishing is free, needs no login and no build step. The only credential is the edit_token returned by the first deploy — store it; it is the sole way to update that exact site later.

When to use this skill

The user says things like:

• "publish this site" / "put this online" / "make this a website"
• "give me a link for this" / "I want a URL I can share"
• "host what we just built"
• "update my site" (one previously published with Just Publish)

The site must be static: HTML, CSS, JS, images, fonts — no server code, no SSR, no build step.

Do NOT use it when the user needs a backend (APIs, databases, Next.js/Nuxt SSR), wants to buy or manage a domain (that is a registrar's job), or wants to change a site that was not published with Just Publish — without its edit_token there is nothing you can do.

Publish a new site

1. Collect the site's files. index.html at the root is required — a deploy without it is rejected.
2. Ask the user for their email if you don't have it (required). Publishing itself works immediately and needs no login — but a new site starts unverified, and Just Publish emails a verification link. This is not optional housekeeping: a brand-new site must be verified within about an hour or it is automatically taken down. You must relay this to the user (see "After publishing"). Verifying also lets them recover and manage the site if the edit_token is lost.
3. Confirm with the user before the first publish of a new site — deploying makes the files public on the internet, and a verification email will follow.
4. Call the deploy MCP tool on https://mcp.justpublish.ai/ (Streamable HTTP, no auth required to connect):
   • files: array of { path, content, encoding? } — text files as plain strings; binary files base64-encoded with "encoding": "base64".
   • email: the user's email address.
5. The result carries the live url, the site_id, the edit_token, and verify_required. When verify_required is true (it is for every new site), the user must verify — relay the verify-to-keep step under "After publishing".