Just Publish

Just Publish turns a website you built with AI into a live, public URL — without leaving the chat.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Deploy: Publish a static site (HTML, CSS, JS, images) to a public URL. First call: omit site_id and edit_token — you'll get back a URL, site_id, and edit_token. Save the edit_token if the user wants t
  • Get Site Files: Read the files of a site you previously published, so you can make a TARGETED edit instead of regenerating the whole site from memory. Returns: a complete manifest (every file's path,
  • Update Site File: Update ONE OR A FEW files of an already-published site, leaving every other file untouched (MERGE — unlike deploy, which replaces the whole site). Ideal for small edits: fix a typo i

What data it sees

Do you need an account

No: the server works without sign-in

Just Publish turns a website you built with AI into a live, public URL — without leaving the chat. No git, no CLI, no build step, no dashboard, and no login to fumble through. You hand it your files, it hands back a working link.

It's built for the person who made a site with ChatGPT, Claude, or Cursor and just wants it online.

How it works

Call deploy with your files (HTML, CSS, JS, images) and an email. You get back a live url, a site_id, and an edit_token. Keep the token and you can update the same site anytime — either a full redeploy or a single-file edit. That's the whole flow.

Tools

  • deploy — Publish a static site to a public URL. First call creates a new site and returns its url, site_id, and edit_token; pass those back to update it in place.
  • update_site_file — Change one or a few files on an existing site without resending the whole thing.
  • get_site_files — Read what's currently live before you edit.

Who it's for

Non-technical builders and AI agents that generate a static site and need it hosted in one step. If you can describe a page, you can publish it.

Good to know

  • No accounts required. Edit access is held by the edit_token returned at publish time.
  • Static sites only — files in, URL out. No frameworks or build pipelines.
  • Free to start; a $9/mo Builder plan and custom-domain connection are available at justpublish.ai.

How to connect

How to connect Just Publish to Claude

The server address to paste into Claude settings:

https://justpublish--just-done.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Just Publish to ChatGPT

The server address to paste into ChatGPT settings:

https://justpublish--just-done.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Just Publish to Cursor

The server address to paste into Cursor settings:

https://justpublish--just-done.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (3)

Raw names from tools/list. Only developers need these.

deployPublish a static site (HTML, CSS, JS, images) to a public URL. First call: omit site_id and edit_token — you'll get back a URL, site_id, and edit_token. Save the edit_token if the user wants to update the same site later. Subsequent calls: pass site_id + edit_token to update the same site in place — note that deploy REPLACES the entire file set (any file you omit is deleted). To change just one or a few files without resending the whole site, use update_site_file instead. To read what's currently live before editing, use get_site_files.
get_site_filesRead the files of a site you previously published, so you can make a TARGETED edit instead of regenerating the whole site from memory. Returns: a complete manifest (every file's path, size, content-type, sha256) and the contents of the text files (HTML/CSS/JS/etc). Also returns the site's current `version` — pass it back to update_site_file to avoid clobbering a newer change. Pass `paths` to fetch only specific files; omit it to get all text files. Requires site_id + edit_token.
update_site_fileUpdate ONE OR A FEW files of an already-published site, leaving every other file untouched (MERGE — unlike deploy, which replaces the whole site). Ideal for small edits: fix a typo in index.html, swap a stylesheet, add one page. Best practice: call get_site_files first, edit the returned content, then call this with the files you changed and the `expected_version` from that read — if the site changed in the meantime you'll get a clear conflict telling you to re-read. Requires site_id + edit_token. Cannot delete files (use deploy to drop a file) and cannot remove index.html.