Just Publish

What the just-publish MCP server does

just-publish publishes static website content to a live public URL through a chat-based workflow. The supported site content includes HTML pages, CSS stylesheets, JavaScript files, and images. It is intended for sites that can be served as static files rather than applications requiring a documented server-side runtime or database.

The core use case is moving a website from an agent conversation to a publicly reachable location. An agent can work with the site files in chat, then use the just-publish MCP server to publish the resulting static content. The supplied description does not identify whether publishing creates a new site, updates an existing site, or supports both workflows.

Tools and capabilities

The documented capability is static-site publishing. Content can include the following asset types:

• HTML
• CSS
• JavaScript
• Images

The result is a live public URL. The available material does not provide formal tool names, input schemas, output fields, authentication options, custom-domain support, versioning behavior, rollback controls, or site management operations. Treat the publishing action as the supported feature and verify any additional behavior before depending on it in an automation workflow.

The just-publish MCP server may fit a developer who wants an agent to publish a small documentation site, prototype, landing page, or other static asset bundle without leaving chat. It is less clearly suited to projects that need backend execution, private access, persistent application data, or deployment settings not mentioned in the available description.

Limitations and notes

No README content was provided, so installation and configuration instructions cannot be confirmed. The supplied source is the justpublish.ai website, but it does not specify the transport used by the MCP server, required credentials, environment variables, client compatibility, or the exact publishing protocol.

The public URL outcome is documented, but details about URL format, duration, indexing, access controls, file-size limits, build steps, and update behavior are not. The service description also does not state whether it performs a build or expects already-generated static files. Developers should confirm those points before using just-publish in production or in a workflow involving sensitive content.

For a basic evaluation, prepare a static site consisting of the supported file types and use the chat workflow to publish it. Confirm that the resulting URL serves the required pages, styles, scripts, and images. Because the available material does not document deployment history or deletion controls, avoid assuming that published content can be revised or removed through a separate MCP operation.