Deploy a folder, build output, or public GitHub repo to a live URL. Update, roll back.
Connect Remote server
claude mcp add --transport http mcp https://mcp.aft.page/mcp
{
"mcpServers": {
"mcp": {
"url": "https://mcp.aft.page/mcp"
}
}
}
{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.aft.page/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcp.aft.page/mcp
Tools 6 found in our last check
deployPublish 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 fil…
deploy_repoSame 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.
aft_deploysList 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_rollbackPoint 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.
aft_promoteMake a held preview version live at the same URL. Pass version (e.g. 4) or deploy_id from aft_deploys. Needs edit_token.
aft_healthPing the aft.page deploy API.
Details
| Endpoint | https://mcp.aft.page/mcp (Streamable HTTP) |
| First published | 25 Oct 2026 |
| Last updated | 25 Oct 2026 |
| Registry name | page.aft/mcp |
More cloud and devops servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
