Deploy

Ship from your terminal.

Build HTML anywhere — your IDE, ChatGPT, Claude, v0, or by hand. Then pagecraft deploy to a clean URL with password, expiry, brand, client portal, and live data via cron.

Install the CLI

Single binary. macOS or Linux. About 200 KB.

$ curl -fsSL https://pagenta.ai/install.sh | bash

Log in

Same email and password as the dashboard.

$ pagecraft login

Deploy a file

Any standalone .html file — inlined styles, scripts, and assets. Re-run with the same slug to update in place — same URL, no version churn.

$ pagecraft deploy ./my-page.html --slug my-page

→ live at https://pagenta.live/p/<you>/my-page

Common flags

Attach to a client portal

$ pagecraft deploy ./report.html --slug q1-review --client acme-corp

Lock behind a password

$ pagecraft deploy ./report.html --slug q1 --password 'spring-2026'

Auto-expire after a window

$ pagecraft deploy ./preview.html --slug preview --expires-in 7d

Schedule a refresh.js (live data)

$ pagecraft cron set --page stocks --every 1h ./refresh.js

Use it from Claude / Cursor / Codex

The CLI doubles as an MCP server. Any agent that supports MCP can deploy your HTML and manage portals. Add this to your agent’s config:

$ {
  "mcpServers": {
    "pagecraft": {
      "command": "pagecraft",
      "args": ["mcp"]
    }
  }
}

Restart your agent, then prompt: “Take this HTML and deploy it as /pitch under client acme-corp.”

Prefer the hosted MCP — one URL, no install, OAuth flow? Connect via the remote MCP server →

Group pages under a portal

One URL, one password, every page for a client in one place. Useful for shipping a set of deliverables to a single customer.

$ pagecraft client create acme-corp --name 'Acme Corp' --password 'shared-pw'

$ pagecraft client add acme-corp <page-slug>

$ pagecraft client list

← Back to Pages GitHub ↗