Connect your LLM to Just Publish.

Quick start

Add the MCP endpoint to your client, then ask the model to publish your files.

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

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

Server URL: https://mcp.justpublish.ai/
Authentication: None

Once connected, ask the model something like: "Publish this HTML to Just Publish and give me the URL." The model calls deploy, returns the URL plus a site_id and edit_token for future updates.

Tool reference — deploy

Publishes a static site. First call (no site_id) creates a new site and returns its credentials. Later calls with the same site_id + edit_token update the site in place.

Parameters

File object

Response (success)

{
  "url":            "https://xK3p9wnA2b.just-web-hosting.com/",
  "site_id":        "xK3p9wnA2b",
  "edit_token":     "...",            // only on create
  "created":        true,             // false on update
  "files_uploaded": 4,
  "total_bytes":    12842
}

Errors

Errors come back as a tool-call result with isError: true and a human-readable message — not as a JSON-RPC error. The model surfaces the message to the user.

JSON-RPC examples

Create a new site

POST https://mcp.justpublish.ai/
Accept: application/json, text/event-stream
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "deploy",
    "arguments": {
      "email": "you@example.com",
      "files": [
        { "path": "index.html", "content": "<h1>hello world</h1>" }
      ]
    }
  }
}

Update an existing site

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "deploy",
    "arguments": {
      "email": "you@example.com",
      "site_id": "xK3p9wnA2b",
      "edit_token": "the token you saved at create time",
      "files": [
        { "path": "index.html", "content": "<h1>hello v2</h1>" }
      ]
    }
  }
}

Constraints

• index.html at the root of the file map is required. A site without it is rejected at deploy.
• Max site size: 50 MB. Max single file: 5 MB. Max 500 files per site.
• Path rules: no .., no leading /, no backslash, no null bytes. The deploy is rejected at validation time, not silently truncated.
• Per-IP rate limits on both site creation and deploys per rolling hour.
• Static files only. No server-side execution, no build step, no environment-variable injection.
• Sites with no traffic for an extended period may be archived (TTL policy).

Edit token & persistence

The edit_token is the only credential needed to update a site over MCP. It's returned once, at create time, and never again — the server stores only a hash. Store it alongside the site_id in your LLM's conversation context, in a saved note, or wherever your client keeps state across sessions.

Losing the token orphans the site from MCP updates. Recovery: sign in at /login with the email you used at deploy time. The dashboard lists your sites and uses session-authenticated HTTP endpoints (not the edit_token) to update or delete them.