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 Just Publish as a connector in your assistant, and it can publish a static website for you and return a live link. Pick your tool below. In Claude you add it and sign in; the others you point at https://mcp.justpublish.ai/ by hand. Either way it is a couple of simple steps and no code. New to this? Start with what AI-built website hosting is.
01 Pick your AI assistant
These four are verified end-to-end. Any MCP-capable client can connect to the same server.
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.
The Claude guide connects the signed-in endpoint https://mcp.justpublish.ai/claude: you sign in once, every site is filed under your account, and your assistant gains one more ability - list_sites, which shows what you have already published so it can find a site without you digging up a code. The same signed-in endpoint exists for ChatGPT at https://mcp.justpublish.ai/chatgpt. The ChatGPT and Cursor guides here use https://mcp.justpublish.ai/, which you add by hand and which identifies you by an email address on the first publish instead of a sign-in. Each signed-in endpoint advertises the contract its directory requires, so the tools they offer are not identical.
02 What your assistant can do
Connect a client by hand to https://mcp.justpublish.ai/ and it gets these three abilities - nothing else. Sign in through the Claude connector and it gets a fourth, list_sites.
| 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. The same server also runs a signed-in endpoint at https://mcp.justpublish.ai/claude for the Claude connector, which adds a fourth tool, list_sites.
Any MCP-capable client. Just Publish has verified end-to-end connect flows for Claude (the signed-in connector at https://mcp.justpublish.ai/claude, on the web, in Claude Desktop, on mobile and in Claude Code), ChatGPT (Developer Mode connector), and Cursor (mcp.json). For ChatGPT and Cursor it is a single URL you add once - https://mcp.justpublish.ai/.
It depends on which endpoint you connect. The Claude connector at https://mcp.justpublish.ai/claude signs you in with Google or a code sent to your email, and files every site under your account. The manually configured endpoint at https://mcp.justpublish.ai/ identifies you by an email address you pass on the first publish instead; proving that address is what keeps the site up and what lets you recover or edit it later. Neither uses an API key.
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