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.
Quick start for AI tools
- 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 adevice_codeand auser_code. Press5 emails the person a link. Tell them to open it, check that it shows the sameuser_code, and press Approve. - 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":"..."}'untilstatusisapproved. The reply then holdstoken(starts withp5_). It is shown once: keep it (for example in thePRESS5_TOKENenvironment variable) and never print it in full. People can also make a token themselves at https://my.press5.xyz/launch. - Build the site the usual way (
npm run buildor similar) so you have a folder with anindex.htmlin it. - 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 - Give the person the
urlfrom the reply. A brand-new site's HTTPS certificate takes a minute or two; the reply says"https": "pending"until then and includes anhttp_urlthat 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_..." } } } }
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/* needs Authorization: Bearer <token>. Replies are JSON. Errors look like { "error": { "code": "site_name_taken", "message": "...", "hint": "..." } }.
POST /auth/start{ "email", "client" }: starts an email-approved sign-in. Returnsdevice_code,user_code,interval,expires_in.POST /auth/poll{ "device_code" }:statusispending,approved(withtoken),denied,expiredorclaimed.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": "<!doctype html>..." }, { "path": "logo.png", "content": "<base64>", "encoding": "base64" }] }(up to 15 MB). Add?spa=1(or"spa": truein JSON) for single-page apps: unknown paths then serveindex.html. POST /sites/{name}/rollback{ "deploy": "<deploy id>" }: 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
/aboutservesabout.htmlorabout/index.html. A404.htmlat the top is used for missing pages.- With
spaon, or a200.htmlfile, unknown paths serve that page instead (for client-side routing). - If the whole upload sits in one folder (for example
dist/) with anindex.htmlinside, that folder becomes the site root. - Left out on purpose and listed in the reply:
.git,node_modules,.envfiles, 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.