Just Publish MCP Server

by justpublish Your server? Claim it

answering

Just Publish is answering right now. Last checked 10 min ago. It exposes 3 tools. Last commit 28 Oct 2026.

Publish and update the website you built with AI at a live public URL. Sign-in required.

Uptime history 91 days of history · worst day 92%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

92 ms

Response time

average over 24h

Stars

last commit 28 Oct 2026

What changed 11

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

23 Sep a tool changed version

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

Nothing serious here today

Today is the operative word: we check Just Publish every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 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/

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "just-publish": {
      "type": "http",
      "url": "https://mcp.justpublish.ai/"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

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	sign-in	73 ms	10 min ago

Alternatives to Just Publish

same job, measured the same way

JustCopy

by justcopy

Build, change and publish a business website from your AI assistant, with sign-in and saved data.

answering

Small Site

by dot-billy

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

local only

WebTwizz

by webtwizz

Build websites and web apps with AI, see them in the chat, and publish them.

answering

NSD.SG

by aarif86

Put the page your AI made online at yourname.nsd.sg. Publish, update, list and remove sites.

answering

Cloud

by skkkadoosh

Share the app you built with AI privately: one sign-in link, remove anyone at once.

answering

3dCMS

by 3dcms

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

13 tools answering

Neopress

by neopress

Build, publish, and grow SEO-ready websites just by chatting with your AI assistant.

answering

unulu

by unulu

AI agent website builder. Create and publish link-in-bio sites via MCP or REST API.

4 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 91 checks got a reply (100.0%), average response time 92 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 in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Just Publish?

No API key is involved. Just Publish answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Just Publish?

It answers our handshake in 92 ms on average, which is faster than 93% 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?

The code is open source: it is published under the MIT licence, 1 stars on GitHub and 2 open issues. The licence covers the code in the repository, not the hosted service at mcp.justpublish.ai, which runs on its operator's own terms.