Just Publish MCP Server

by justpublish Your server? Claim it

answering

Just Publish is answering right now. Last checked 5 min ago. It exposes 3 tools. Last commit 12 Sep 2026.

Publish the website you built with AI to a live public URL — straight from chat, no setup.

Uptime history 47 days of history · worst day 99%

47 days agonow

98.9%

Uptime 24h

91 of 92 checks

Tools

read from the server

115 ms

Response time

average over 24h

Stars

last commit 12 Sep 2026

What changed 10

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.

12 Sep 3 tool descriptions were rewritten deploy, get_site_files, update_site_file

12 Sep a tool changed the parameters it asks for deploy

12 Sep a tool changed version

10 Sep a tool changed version2 times that day

13 Aug a tool changed version

9 Aug a tool changed version2 times that day

and 2 more, back to 9 August 2026

Just Publish missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add just-publish --transport http https://mcp.justpublish.ai/

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "just-publish": {
      "url": "https://mcp.justpublish.ai/"
    }
  }
}

~/.codex/config.toml

[mcp_servers.just-publish]
url = "https://mcp.justpublish.ai/"

.cursor/mcp.json

{
  "mcpServers": {
    "just-publish": {
      "url": "https://mcp.justpublish.ai/"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "just-publish": {
      "url": "https://mcp.justpublish.ai/"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

site

get_site_files

Read the files of a site you already published, so you can make a targeted edit instead of rebuilding the whole site from memory. Returns a complete manifest (every file's path, size, content-type, sha256) plus the contents of the text files (HTML/CSS/JS/etc). Also returns the site's current `version` - pass it back to update_site_file so you don't overwrite a newer change. Pass `paths` to fetch only specific files; omit it to get all text files. Requires site_id + edit_token.

update_site_file

Change one or a few files of an already-published site, leaving every other file untouched (a 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 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.

deploy

deploy

Put a website live at a public URL. Use this when the user wants to publish, launch, or get a page online - e.g. 'I need a website', 'put up a page for my business', 'make this live'. Takes static files (HTML, CSS, JS, images) and returns a working URL anyone can open. No build step, no config. First call: omit site_id and edit_token - you get back a url, a site_id, and an edit_token. Keep the edit_token; it's the only way to change this site later. Later calls: pass site_id + edit_token to publish over the same site. deploy REPLACES the whole site - any file you leave out is DELETED. To change just one or a few files, use update_site_file instead. To see what's currently live before editing, use get_site_files first.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.justpublish.ai/	streamable-http	answering	78 ms	5 min ago

Alternatives to Just Publish

same job, measured the same way

drop

by neuronik

Publish web pages straight from your AI assistant and share them with a link.

answering

Dplooy

by dplooy

Publish a complete website to a live URL from your AI assistant: forms, bookings, content, chatbot

answering

Small Site

by dot-billy

Validate and publish built static websites to a public Small Site URL.

local only

Netcafe Build

by ainetcafe

Deploy a live web app from one sentence. build_app + poll to a public HTTPS URL you own.

7 tools answering

Sitelas

by sitelas

Build a real website from a chat — then run it: read messages, check traffic, publish changes.

answering

MakeItRun

by makeitrunai

Publish HTML from Claude or ChatGPT to a live URL with a QR code — no developer needed.

answering

Miinideck

by suiyang-meta

Publish AI-generated HTML to a private, unguessable link, straight from Claude or ChatGPT.

answering

3dCMS

by 3dcms

Build a real 3D website by chatting: pages, models and text in space, published to a live URL.

8 tools answering

Just Publish — questions

Answers built from our own checks of this server.

What can Just Publish do?

It exposes 3 tools, read directly from the server on our last check. Among them: deploy, get_site_files, update_site_file. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Just Publish working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 92 checks got a reply (98.9%), average response time 115 ms. The bar chart above shows every period we have measured.

How do I connect Just Publish?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Just Publish need an API key?

No. Just Publish completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Just Publish?

It answers our handshake in 115 ms on average, which is faster than 82% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Just Publish open source?

Yes — it is published under the MIT licence and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.