Connect your AI assistant
Just Publish plugs into your AI assistant over MCP. Connect it once — then publishing a static website is a single sentence in the chat.
Add https://mcp.justpublish.ai/ as a connector in your assistant, and it can publish a static website for you and return a live link. Pick your tool below. Each guide is a couple of simple steps, no sign-in and no code. New to this? Start with what AI-built website hosting is.
01 Pick your AI assistant
These three are verified end-to-end. Any MCP-capable client can connect to the same URL.
Each flow is verified against the client's own current docs. Not sure your files are ready? See the file-prep guide. For the raw tool schemas, see the MCP reference.
Every guide here uses https://mcp.justpublish.ai/, which needs no sign-in. If your client requires an authenticated connector, the same server is also at https://mcp.justpublish.ai/claude and https://mcp.justpublish.ai/chatgpt behind a sign-in: a site published there is filed under your account, and because it knows who you are it adds one more ability - list_sites, which shows the websites you have already published so your assistant can find one without you digging up a code.
02 What your assistant can do
Whichever tool you connect to the no-sign-in endpoint, it gets the same three abilities - nothing else.
| Tool | What it does |
|---|---|
deployPublish a website | Send the static files (HTML, CSS, JS, images) and get back a live URL, a site_id, and an edit_token. |
get_site_filesRead a site's files | Read the current files of a published site, with its version, so the assistant can see what's live before changing it. |
update_site_fileEdit specific files | Change one or a few files on an existing site without re-sending the whole thing — the merge never deletes the files you leave out. |
03 FAQ
A remote MCP server at https://mcp.justpublish.ai/ that gives an AI assistant three tools — deploy, get_site_files, and update_site_file — to publish a static website (HTML, CSS, JS, images, fonts) to a live URL and edit it afterward. No login is required to publish.
Any MCP-capable client. Just Publish has verified end-to-end connect flows for Claude (custom connector, remote MCP), ChatGPT (Developer Mode connector), and Cursor (mcp.json). Connecting is a single URL you add once — https://mcp.justpublish.ai/.
No. The publish flow is unauthenticated — you add the server URL with “No Authentication” and start publishing. An email is captured on the first deploy only, so you can recover or edit the site later; it isn't a login and isn't verified up front.
The first deploy returns a site_id and an edit_token — that token is the only credential to change the site later. The assistant reads the live files with get_site_files, then changes just the files that need it with update_site_file (a merge that never deletes the files you leave out), or replaces the whole site with another deploy.
It serves static sites only — no servers, databases, logins, or build steps. If a site needs a backend to run, a published static site can't provide it. An index.html at the site root is required.
Keep going