Press5.xyz
Test mode: no real payments are taken. Pay with Stripe's test card 4242 4242 4242 4242.

Launch pad

Publish a site from your AI tool

An MCP server, a plain HTTP API and a one-file CLI. Free for small static sites.

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

  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_..." } } } }

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": "..." } }.

How sites are served

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.