bots.st/aft-page

aft.page

Deploy site builds or repos to a live URL

2295 ms

answered our call 8 Nov, 02:51 UTC

How to reach it

Tool	What it says it does
`aft_deploys`	List the versions (v1, v2…) of a slug with their label, door, commit and whether each is live or a held preview. Needs edit_token from .aft/state.json (or the first deploy). Same history the project UI shows after claim.
`aft_health`	Ping the aft.page deploy API.
`aft_promote`	Make a held preview version live at the same URL. Pass version (e.g. 4) or deploy_id from aft_deploys. Needs edit_token.
`aft_rollback`	Point the live slug at a prior version from aft_deploys, by version number or deploy_id. Same URL. Needs edit_token from .aft/state.json. Claim not required.
`deploy`	Publish to a live URL. Pass html (one page) OR files (a built site, or a small app's source). Plain HTML → html. Vite/React → npm run build, then files from dist/. Next static export → files from out/; a static site needs index.html. Flask/FastAPI/Django/Express → the source files with…
`deploy_repo`	Same engine as aft.page/run: public GitHub URL → detect → build → live URL. Static is instant; Vite and Next.js build in the background (polls until live or failed). Private repos are refused. For a local project dir, use hosted CLI aft deploy instead.

Deploy a folder, build output, or public GitHub repo to a live URL. Update, roll back.

Website: aft.page/mcp
Source: github.com/aft-page/plugins
Publisher: aft.page
Listed from: the official MCP Registry as page.aft/mcp
Version: 1.1.0, updated 25 Oct 2026
Kinds of work: Cloud and DevOps, Browser and automation, Domains and websites

aft.page: registered 26 Jul 2026 (3 months ago), at CloudFlare, Inc., its name does not resolve now

From our own crawl of domain names: registry records and the home page as our crawler last saw it.

Is this your bot? Claim its address to add a verified badge and keep the listing current.