aft.page
MCP serverCloud & infraaft-page publishes an HTML file or a built dist/ folder to a live HTTPS URL, so your page is reachable on the open web. No account is needed. You can drop files in, use the command line, or let your AI handle the publish.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding it, give your AI an HTML file or a dist/ folder and ask it to publish. You will get a live HTTPS link back that you can share.
Then ask your AI: use the deploy tool from aft.page
What your AI can do with it
- Publish an HTML file to a live HTTPS URL
- Deploy a built dist/ folder online
- Publish without creating an account
- Get a shareable link for every deploy
- Publish by dropping files in, with no commands to run
From the project's README
As published by vaibhavmule/aft.page in README.md.
Your agent made the app. aft makes it real. Give aft.page what an agent made → get a durable live URL → share it like a Google Doc.
Hosted path: HTML/files via MCP, paste, upload, or API — plus runtimes
(upstream worker / next) with claim, share, and per-site secrets. See
rfs.txt and docs/STRATEGY.md.
| Path | Role |
|---|---|
www/ | Apex website (landing, login, docs — Cloudflare Pages) |
apps/api/ | Worker: deploy, serve, secrets, upstream proxy |
apps/extension/ | Chrome: Run on AFT on GitHub; ChatGPT/Claude HTML + repo links |
apps/mcp/ | MCP: any agent can deploy_html / deploy_files |
apps/cli/ | Hosted CLI: curl -fsSL https://aft.page/install | sh → aft deploy |
examples/ | vite-hello, next-hello, share-checklist |
Hosted CLI (no account required):
curl -fsSL https://aft.page/install | sh
aft deploy
OSS CLI (archived origin — cli/, github.com/vaibhavmule/aft — parked): vaibhavmule/aft.
Hosted repo: vaibhavmule/aft.page.
Try it
curl -X POST https://api.aft.page/v1/deploy \
-H 'Content-Type: text/html' \
-H 'X-Aft-Client: curl' \
--data '<h1>Hello from aft.page</h1>'
# → { "url": "https://{slug}.aft.page", ... }
Live: hello.aft.page · vite-hello.aft.page (Vite SPA) · next-hello.aft.page (Next SSR SPOC) · share-checklist.aft.page
Human landings: Docs · Drop · Compare · host · share · upload
Deploy a static site without Vercel, Netlify, or Cloudflare Pages
You do not need Vercel, Netlify, or Cloudflare Pages to put a static site online. Those three are right when you already have a git repo, CI, preview PRs, or a production app. If you have dist/ or an agent-made index.html, use aft.page.
curl -fsSL https://aft.page/install | sh
aft deploy
Remote MCP (no account): https://mcp.aft.page/mcp · plugin: npx plugins add vaibhavmule/aft.page
Ranking: aft.page/compare · post: full write-up
Secrets (owner / editor)
# List names only
curl https://api.aft.page/v1/sites/{slug}/secrets -H "Cookie: …"
# Set env value
curl -X PUT https://api.aft.page/v1/sites/{slug}/secrets/ANTHROPIC_API_KEY \
-H "Content-Type: application/json" -H "Cookie: …" \
-d '{"value":"sk-…"}'
aft.json may declare "runtime": "worker" | "next" | "static" and
capabilities.secrets / egress. See docs/CAPABILITIES.md.
Develop the API
cd apps/api
npm install --legacy-peer-deps
npx wrangler deploy
See apps/api/README.md, docs/METRICS.md, and todo.txt.
Tools it offers (5)
What this server listed when ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.
deploydeploy_repoaft_deploysaft_rollbackaft_health
Signals
- Last commit
- Sep 2026
Advanced
- Delivery
- aft-page MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
- Catalog kind
- mcp-server
- Gateway key
io-github-vaibhavmule-aft-page- Source
- github.com/vaibhavmule/aft.page
- Hosted endpoint
https://mcp.aft.page/mcp