Deploy a static site
deploy_sitePublish a static website (HTML, CSS, JS, images) to the Press5 launch pad and get its live URL. Works with no account: without a token the site gets a random name, goes live at once, and the reply has a claim_url for the person to keep it (unclaimed sites are deleted after 3 days) and a site_key to redeploy the same site. With a token, "site" picks the name (3-42 lowercase letters, digits, hyphens; created the first time if free). Send every file of the built site; this replaces the whole site. Text files as plain content, binary files as base64 with encoding "base64". Best for small sites: for big builds use the HTTP API with a .tar.gz (see https://my.press5.xyz/llms.txt). To start from one of the free starter templates (list_templates), send "template" and optional "fields" instead of files.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "deploy_site"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| spa | No | Single-page app: serve index.html for unknown paths (client-side routing) | |
| site | No | Site name, becomes <site>.on.press5.xyz. Needs a token; leave it out for a random name. | |
| files | No | ||
| token | No | A press5 token (p5_...). Only needed when the MCP connection has no Authorization header, e.g. right after login_check. | |
| fields | No | With template: the text to fill in, by field key, e.g. {"name": "Rosie's Café", "email": "hi@rosies.example"}. | |
| site_key | No | The site_key from an earlier deploy without an account, to update that same site. | |
| template | No | Instead of files: the id of a starter template from list_templates, published as it is or with "fields" filled in. |