KitScout

Categories › Cloud & DevOps › Hosting & deployment

aft.page

MCP serverVerified domain · aft.pageRemote● LiveFree to try

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

Install

Remote server: your requests and data go to mcp.aft.page. Claude Code: claude mcp add --transport http aft-page https://mcp.aft.page/mcp · Claude app: Settings → Connectors → Add custom connector.

What it can do

The tools this server listed when we connected to it, in its own words.

  • 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,
  • 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 (pol
  • 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/
  • 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. Cl
  • 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_health — Ping the aft.page deploy API.

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools