Connect

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.

About 2 minutes each 4 assistants verified
The short answer

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 and sign in the first time. 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.

Every guide here ends with the same free sign-in, and every site is filed under your account, so your assistant can find what you published with list_sites. The Claude connector uses https://mcp.justpublish.ai/claude, the ChatGPT connector uses https://mcp.justpublish.ai/chatgpt, and every other client uses https://mcp.justpublish.ai/. Each address has its own OAuth token, because a token is bound to the address that issued it.

02 What your assistant can do

Connect any client to https://mcp.justpublish.ai/, sign in, and it gets these four abilities - nothing else.

ToolWhat it does
deployPublish a websiteSends your files and returns a live link.
get_site_filesRead a published site's filesReads what is live right now, so Claude can look at a page before it changes it.
update_site_fileChange specific filesChanges one or a few files on a site that is already live and leaves the rest alone.
list_sitesList your published websitesReturns the websites on your account with their links, dates and views.

03 FAQ

What is Just Publish's MCP server?

A remote MCP server at https://mcp.justpublish.ai/ that gives an AI assistant four tools - deploy, get_site_files, update_site_file and list_sites - to publish a static website (HTML, CSS, JS, images, fonts) to a live URL and edit it afterward. The person signs in once with a free account, and every site is filed under it. The Claude connector uses https://mcp.justpublish.ai/claude, the same server.

Which AI assistants can connect?

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/.

Do I need an API key or to sign in?

You sign in, not paste a key. The first time your assistant connects, it opens a sign-in window: Google or a code sent to your email, a free account. Every site you publish is filed under that account, so your assistant can find and edit it later. There is no API key.

How does editing a published site work?

Every site is filed under your account, so the assistant finds it with list_sites and needs only its site_id. It 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.

What can't it do?

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.