aft.page MCP Server

by aft Your server? Claim it

answering

aft.page is answering right now. Last checked 15 min ago. It exposes 5 tools. Last commit 28 Aug 2026.

Deploy HTML or dist/ to a live HTTPS URL. No account. Drop, MCP, or CLI.

Uptime history 36 hours of history

36 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

313 ms

Response time

average over 24h

Stars

last commit 28 Aug 2026

Nothing serious here today

Today is the operative word: we check aft.page every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.aft.page/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.aft.page/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.aft.page/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.aft.page/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.aft.page/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

aft

aft_deploys

List rollback-able deploys for a slug. 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_rollback

Point the live slug at a prior deployId from aft_deploys. Same URL. Needs edit_token from .aft/state.json. Claim not required.

deploy

deploy

Publish to a live URL. Pass html (one page) OR files (built site). Plain HTML → html. Vite/React → npm run build, then files from dist/. Next static export → files from out/. Always include index.html. Never upload src/, node_modules, or .next/. First hit: preferred_slug from aft.json (include aft.json in files). Later: same slug + edit_token from .aft/state.json. Limits: 500 files, 25MB each, 100MB total.

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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.aft.page/mcp	streamable-http	answering	381 ms	15 min ago

Alternatives to aft.page

same job, measured the same way

aft.page

by vaibhavmule

Deploy HTML or dist/ to a live HTTPS URL. No account. Drop, MCP, or CLI.

5 tools answering

ship.page

by ship

Deploy HTML from any agent: POST markup, get a live URL. Static hosting API with MCP tools.

9 tools answering

Breezedeploy

by przemekzur

Deploy a local folder, git repo, or Docker image to a live HTTPS URL from your AI chat.

39 installs/wk local only

Openpouch

by openpouch

Agent-native hosting: deploy any folder to a live URL in one command. No approve tool.

68 installs/wk local only

Netcafe Build

by ainetcafe

Deploy a live web app from one sentence. build_app + poll to a public HTTPS URL you own.

7 tools answering

PageDrop MCP

by dpozimski

Deploy and manage instant HTML sites with paste, upload, and ZIP deploy

33 installs/wk local only

Softkiln Deploy

by softkiln

Host apps built with AI: deploy to a live HTTPS URL, custom domains, secrets and backups.

answering

PastML

by h4ck4life

Deploy HTML and Markdown as live URLs. Create, search, update, and manage pastes from any AI agent.

answering

aft.page — questions

Answers built from our own checks of this server.

What can aft.page do?

It exposes 5 tools, read directly from the server on our last check. Among them: aft_deploys, aft_health, aft_rollback, deploy, deploy_repo. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is aft.page mostly used for?

Its tools cluster around aft and deploy. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is aft.page working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 313 ms. The bar chart above shows every period we have measured.

How do I connect aft.page?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does aft.page need an API key?

No. aft.page completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is aft.page?

It answers our handshake in 313 ms on average, which is faster than 55% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is aft.page open source?

Yes — written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.