Just Publish MCP Server

Publish a static website to a live public URL straight from chat.

Remote serverstreamable-http

What is the Just Publish MCP server?

Most cloud and infrastructure work still happens through a UI a human drives. Just Publish MCP server moves it into the conversation instead. Publish a static website to a live public URL straight from chat.

The short version

Describe a site to your AI assistant — ChatGPT, Claude, Gemini, or any MCP-enabled client — and it publishes the site and hands back a live URL. 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. Built for the person who made a site with AI and just wants it online.

Public metadata + registry listing for the Just Publish MCP server: server.json, .mcp.json, icons, and this README. The server runs at https://mcp.justpublish.ai/; its source is not part of this repo.

The tools it exposes

The server publishes 3 tools. What each one is for:

  • deploy — Publish a new static site (HTML/CSS/JS/images), or fully replace an existing one. Returns the live URL, a site_id, and an edit_token
  • get_site_files — Read a published site's files so the assistant can make a targeted edit. Requires site_id + edit_token
  • update_site_file — Change one or a few files in place (merge). Requires site_id + edit_token

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Just Publish's toolset — deploy, get_site_files, update_site_file — is a fair guide to whether it matches your workflow. It is maintained by ai.justpublish; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
deployPublish a new static site (HTML/CSS/JS/images), or fully replace an existing one. Returns the live URL, a site_id, and an edit_token.
get_site_filesRead a published site's files so the assistant can make a targeted edit. Requires site_id + edit_token.
update_site_fileChange one or a few files in place (merge). Requires site_id + edit_token.

How to install the Just Publish MCP server

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

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Just Publish to deploy.
  • Use Just Publish to get site files.
  • Use Just Publish to update site file.

Frequently asked questions

It connects Just Publish to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (deploy, get_site_files, update_site_file) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Just Publish directly.