# Press5 launch pad
> Publish a static website in one request and get a live HTTPS address like https://my-site.on.press5.xyz.
> Built for AI coding tools: there is an MCP server, a plain HTTP API you can call with curl, and a CLI.
> Free accounts get 3 sites (25 MB each); press5 web hosting customers get 25 sites (100 MB each).
Static sites only for now: HTML, CSS, JavaScript, images, fonts, and the output of any static build
(Vite, React, Vue, Svelte, Astro, Next.js `output: 'export'`, Hugo, Jekyll, Eleventy, plain HTML).
Server code (Node, PHP, Python) does not run here yet.
## Quickest: no account needed
Build the site, then send the output folder. No token, no sign-up:
`tar -czf site.tar.gz -C dist . && curl -s -X POST https://my.press5.xyz/api/v1/deploys --data-binary @site.tar.gz`
or as JSON: `curl -s -X POST https://my.press5.xyz/api/v1/deploys -H 'Content-Type: application/json' -d '{"files":[{"path":"index.html","content":"
Hello
"}]}'`
The reply has:
- `url`: the live site, under a random name like `https://sunny-otter-4821.on.press5.xyz`.
- `claim_url`: **give this to the person.** The site is deleted after 72 hours unless they open it and keep the site
(free, it only asks for their email). Claiming also gives the site HTTPS if it is on http:// until then.
- `site_key` (starts with `p5k_`): send it as `Authorization: Bearer p5k_...` to `POST https://my.press5.xyz/api/v1/deploys` to update the
same site. Keep it to yourself like a password: never show it or put it in published files. It stops working once the site is claimed.
- `next`: what to tell the person.
Limits without an account: 10 MB and 1000 files per deploy, 30 deploys a day per site, no password fields
in pages. CLI: `npx @press5/cli deploy ./dist` does all of this and remembers the site key per folder. MCP: call
`deploy_site` without a token.
To choose the site name, keep sites for good from the start, or deploy bigger sites, sign in as below.
## Quick start for AI tools (with an account)
1. **Get a token.** Ask the person for their email address, then:
`curl -s -X POST https://my.press5.xyz/api/v1/auth/start -H 'Content-Type: application/json' -d '{"email":"person@example.com","client":"Your tool name"}'`
The reply has a `device_code` and a `user_code`. Press5 emails the person a link. Tell them to open it,
check that it shows the same `user_code`, and press Approve.
2. **Wait for approval.** Every 3 seconds:
`curl -s -X POST https://my.press5.xyz/api/v1/auth/poll -H 'Content-Type: application/json' -d '{"device_code":"..."}'`
until `status` is `approved`. The reply then holds `token` (starts with `p5_`). It is shown once:
keep it (for example in the `PRESS5_TOKEN` environment variable) and never print it in full.
People can also make a token themselves at https://my.press5.xyz/launch.
3. **Build the site** the usual way (`npm run build` or similar) so you have a folder with an `index.html` in it.
4. **Deploy it** (creates the site the first time; the name must be free):
`tar -czf site.tar.gz -C dist . && curl -s -X POST "https://my.press5.xyz/api/v1/sites/my-site/deploys" -H "Authorization: Bearer $PRESS5_TOKEN" --data-binary @site.tar.gz`
5. Give the person the `url` from the reply. A brand-new site's HTTPS certificate takes a minute or two;
the reply says `"https": "pending"` until then and includes an `http_url` that works straight away.
## MCP server
Endpoint: `https://my.press5.xyz/mcp` (Streamable HTTP, JSON responses). Send the token as `Authorization: Bearer p5_...`.
Claude Code:
`claude mcp add --transport http press5 https://my.press5.xyz/mcp --header "Authorization: Bearer p5_..."`
Other clients (Cursor, Windsurf, VS Code, Claude Desktop with a remote connector):
`{ "mcpServers": { "press5": { "url": "https://my.press5.xyz/mcp", "headers": { "Authorization": "Bearer p5_..." } } } }`
No token is needed to publish: `claude mcp add --transport http press5 https://my.press5.xyz/mcp` and call `deploy_site`. Without a token
it returns a `claim_url` and a `site_key` (pass `site_key` back to `deploy_site` to update the same site).
Tools: `login_start` and `login_check` (sign in by email when there is no token yet), `deploy_site`
(files as text or base64 in the call: best for small sites), `list_sites`, `site_info`, `rollback_site`, `delete_site`.
For a large build, use the HTTP API with a .tar.gz instead of sending every file through the model.
## CLI
`npx @press5/cli login`, then `npx @press5/cli deploy ./dist --site my-site` (Node 18 or newer, no dependencies).
Or install it once with `npm i -g @press5/cli` and run `press5 deploy`. Single-file download: https://my.press5.xyz/launch/press5.mjs
## HTTP API
Base: `https://my.press5.xyz/api/v1`. Every call except `auth/*` and `POST /deploys` needs `Authorization: Bearer `. Replies are JSON.
Errors look like `{ "error": { "code": "site_name_taken", "message": "...", "hint": "..." } }`.
- `POST /deploys`: publish under a random name. No token: a site with no owner yet (see "Quickest" above).
With `Authorization: Bearer p5k_...`: update that unclaimed site. With a `p5_` token: a new site on your account.
- `POST /auth/start` `{ "email", "client" }`: starts an email-approved sign-in. Returns `device_code`, `user_code`, `interval`, `expires_in`.
- `POST /auth/poll` `{ "device_code" }`: `status` is `pending`, `approved` (with `token`), `denied`, `expired` or `claimed`.
- `GET /me`: the account, its plan and limits.
- `GET /sites`: your sites.
- `POST /sites` `{ "name", "spa" }`: reserve a name without deploying.
- `GET /sites/{name}`: one site with its recent deploys.
- `POST /sites/{name}/deploys`: publish a new version. The body is either
- a .tar.gz (or .tar) of the site folder, sent as the raw body (`--data-binary @site.tar.gz`) or as a multipart file field, or
- JSON `{ "files": [{ "path": "index.html", "content": "..." }, { "path": "logo.png", "content": "", "encoding": "base64" }] }` (up to 15 MB).
Add `?spa=1` (or `"spa": true` in JSON) for single-page apps: unknown paths then serve `index.html`.
- `POST /sites/{name}/rollback` `{ "deploy": "" }`: put an earlier deploy back live.
- `DELETE /sites/{name}`: delete the site and every deploy. The name becomes free for anyone.
## How sites are served
- `/about` serves `about.html` or `about/index.html`. A `404.html` at the top is used for missing pages.
- With `spa` on, or a `200.html` file, unknown paths serve that page instead (for client-side routing).
- If the whole upload sits in one folder (for example `dist/`) with an `index.html` inside, that folder becomes the site root.
- Left out on purpose and listed in the reply: `.git`, `node_modules`, `.env` files, private keys, OS clutter.
- Symlinks are refused. Each deploy is kept for rollback (the last 5 on free accounts, 20 on paid).
## Names and rules
Site names are 3 to 42 characters: lowercase letters, digits and single hyphens. Names are first come, first served.
Names that imitate brands or banks are refused. Phishing, malware, scams and illegal content are removed without
notice and the account is blocked. Free limits: 3 sites, 25 MB and 2000 files per deploy, 50 deploys a day.
Terms: https://press5.xyz/legal/terms-of-service. Report abuse: https://press5.xyz/contact.