About aft.page
aft.page is a remote MCP server and agent skill for deploying site files or public GitHub repositories to a live URL. It supports deployment updates, history lookup and rollback, with no local code added.
Key features
- 01Deploy HTML and built folders
- 02Build and deploy public GitHub repositories
- 03Update deployments using a slug and edit token
- 04View deploy history and roll back
- 05Check the aft.page connection
Use cases
- 01Publishing a built static site to a shareable URL
- 02Deploying a public GitHub app
- 03Rolling a site back to an earlier deployment
MCP support
The remote server at https://mcp.aft.page/mcp exposes deployment, history, rollback and health tools to MCP clients. The plugin also provides a skill that guides agents through building and deploying.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.aft.page/mcpclaude mcp add --transport http page-aft https://mcp.aft.page/mcp{"mcpServers":{"page-aft":{"type":"http","url":"https://mcp.aft.page/mcp"}}}Open in Cursor{"servers":{"page-aft":{"type":"http","url":"https://mcp.aft.page/mcp"}}}Open in VS Code{"mcpServers":{"page-aft":{"type":"http","url":"https://mcp.aft.page/mcp"}}}{"mcpServers":{"page-aft":{"serverUrl":"https://mcp.aft.page/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEaft.page plugin
Ask your coding agent to deploy to aft.page and get back a live, shareable URL. No account needed for the first deploy.
The plugin is two things: a skill that tells the agent how to build and ship
safely, and the aft.page remote MCP server (https://mcp.aft.page/mcp) that
does the upload. It adds no local code.
Install
Cursor: install aft.page from the Cursor Marketplace, or add this repo as a marketplace source.
Claude Code
/plugin marketplace add aft-page/plugins
/plugin install aft-page@aft-page
Codex, Copilot CLI, VS Code, and other agents via the
plugins installer:
npx plugins add aft-page/plugins
Any MCP client (no plugin):
{
"mcpServers": {
"aft-page": { "type": "streamable-http", "url": "https://mcp.aft.page/mcp" }
}
}
Restart the agent, then say:
Deploy this to aft.page
What it can deploy
Static sites and build output (Vite, Next.js static export), and public GitHub repos through the same engine as aft.page/run: Next.js server rendering, Node, Python (Flask, FastAPI, Django) and Dockerfile apps. The tools:
| Tool | Does |
|---|---|
deploy | Publish HTML or a built folder; update it with the same slug + edit token |
deploy_repo | Build and publish a public GitHub repo |
aft_deploys | List a site's deploy history |
aft_rollback | Roll back to an earlier deploy on the same URL |
aft_health | Check the connection to aft.page |
Before you deploy
- A first deploy is public immediately. Claim it (the agent returns a claim link) to keep it and to make it private.
- The agent stores the site's edit token in
.aft/state.json. Keep.aft/out of git; the skill adds it to.gitignore. - Never deploy secrets: the skill excludes
.env*, keys and credentials.
Layout
.cursor-plugin/plugin.json Cursor manifest
.claude-plugin/ Claude Code manifest + marketplace
.plugin/plugin.json, .mcp.json `npx plugins` manifest + MCP
plugin.json, mcp.json Agent Plugins manifest + MCP
skills/deploy-to-aft/ the skill
Issues and questions: [email protected] · aft.page
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.