LabscoMCP early access ↗
just-doneMCP SERVER · OFFICIAL PROJECT

Just Publish

Publish a static site to a live URL from chat — no git, no CLI, no build step, no login.

by just-done ↗PaaS Deployment & App Hosting✓ Official

LABSCO SUMMARY

The edit_token is the account.

There is no sign-up to get through, which is the point — and it also means the token deploy hands back is the only route into the site afterwards. The other thing worth holding in your head: deploy replaces everything, update_site_file merges. Picking the wrong one is the only way to lose work here.

What it is

A hosted MCP endpoint that takes HTML, CSS, JS and images and returns a public URL. It also returns a site_id and an edit_token, which are what let you or the assistant change the site later.

What you get

  • deploy — publish a new static site, or fully replace an existing one; returns the live URL, a site_id and an edit_token
  • get_site_files — read a published site's files back so the assistant can make a targeted edit
  • update_site_file — change one or a few files in place, merging rather than replacing
  • Guidance resources the client can load before it picks a tool: just-publish-overview, just-publish-edit-lifecycle, just-publish-file-conventions and just-publish-invariants
  • An Agent Skill package in the same repository, for runtimes that read SKILL.md instead of connecting over MCP

Requirements

Nothing to install — point a client at https://mcp.justpublish.ai/ over Streamable HTTP; the registry name is ai.justpublish/just-publish. No account is required: deploy takes an email and returns the edit_token, and that token is the only thing that authorises later edits, so save it. Static files only, and index.html is required. Custom domains are connected at justpublish.ai.

Setup effort

Paste a URL — add the endpoint to your client