Just Publish

What Just Publish MCP server does

Just Publish MCP server gives an AI assistant a publishing workflow for static websites. The service accepts HTML, CSS, JavaScript, and image files, hosts them, and returns a public URL. A deployment also returns a site_id and an edit_token, which identify and authorize later changes to that site.

The service is intended for sites created in or with an AI assistant. It does not build an application or run a framework pipeline: files go in, and a hosted URL comes back. Custom domains are available through Just Publish separately.

How it works

The remote MCP endpoint is https://mcp.justpublish.ai/ and uses Streamable HTTP, so the server does not need to be installed locally. After adding that endpoint to an MCP-compatible client, the assistant can call deploy with the site files and an email address.

Use deploy to create a site or replace the complete contents of an existing one. Save the returned site_id and edit_token; the token is required for file access and edits. For a targeted change, the assistant can first call get_site_files, modify the relevant content, and then call update_site_file. The update operation merges changes to one or a few files instead of replacing the whole site.

The Just Publish MCP server requires a static site with an index.html file. It is therefore suitable for browser-delivered files, not applications that need server-side execution or a build process.

Setup and configuration

Add the remote server to an MCP client with a Streamable HTTP configuration:

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

There are no local packages or server environment variables described in the provided material. The deployment flow requires an email address. The repository also contains an optional just-publish Agent Skill for runtimes that support SKILL.md; it documents the publish and edit flow, including retaining the edit token and the email-verification step.

Tools and capabilities

• deploy: Publishes a new static site or fully replaces an existing site. Returns the live URL, site_id, and edit_token.
• get_site_files: Reads files from a published site. Requires the site_id and edit_token.
• update_site_file: Applies changes to one or a few files while preserving other site files. Requires the site_id and edit_token.

The Just Publish MCP server also exposes static guidance resources covering tool selection, the read-edit-update lifecycle, file conventions, and deployment invariants such as the required index.html and the difference between replacement and merge operations.

Limitations and notes

Only static sites are supported. The provided material does not describe databases, server-side code, application runtimes, framework builds, or deployment pipelines. A full deploy replaces the existing site, so use get_site_files and update_site_file when making a focused change. Keep the edit token available because later reads and updates require it. The repository contains metadata and registry files; the hosted server source is not part of that repository.