aft.page MCP server
Commit Oct 29, 2026Deploy static sites, build outputs, or public GitHub repositories to a live URL and manage deployments through an AI agent.
Also known as aft-page/plugins, plugins
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.1.0
- Last commit
- Oct 29, 2026
- License
- MIT
What is aft.page MCP?
aft.page deploys static sites, build outputs, or public GitHub repositories to a live URL and manage deployments through an AI agent.
Summary generated from the project's README
About aft.page MCP server
Developers can turn static sites, build outputs, or public GitHub repositories into live, shareable URLs by instructing an AI agent to deploy. This remote MCP server connects to the aft.page engine to handle the heavy lifting of shipping code without requiring local code changes. It works with various clients including Cursor, Claude Code, and any MCP client using a streamable-http connection to the remote URL.
The server provides specific tools to manage the entire deployment lifecycle. You can use the deploy tool to publish HTML or built folders like Vite and Next.js static exports, or use deploy_repo to build and publish public GitHub repositories. For ongoing management, the aft_deploys tool lists deployment history, while aft_rollback allows you to revert to previous versions on the same URL. The system automatically protects your credentials by excluding .env files and keys from the upload process.
What you can do with it
- 1Deploy a static websiteAsk your coding agent to publish a folder containing HTML or a Vite build to a live URL.
- 2Ship a GitHub repositoryInstruct the agent to build and host a public GitHub repository using the deploy_repo tool.
- 3Revert to a previous versionTell the AI to roll back a live site to an earlier deployment if a mistake is found.
- 4Monitor deployment historyRequest a list of all previous deployments for a specific site to track changes.
Written from the project's README. Every use case is checked against a quote from it.
How to install aft.page MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall aft.page MCP in Claude Code
$ claude mcp add --transport http plugins https://mcp.aft.page/mcpInstall aft.page MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"plugins": {
"url": "https://mcp.aft.page/mcp"
}
}
}Install aft.page MCP in VS Code
.vscode/mcp.json
{
"servers": {
"plugins": {
"type": "http",
"url": "https://mcp.aft.page/mcp"
}
}
}Install aft.page MCP in VS Code CLI
$ code --add-mcp '{"name":"plugins","type":"http","url":"https://mcp.aft.page/mcp"}'Install aft.page MCP in Codex
$ codex mcp add plugins --url https://mcp.aft.page/mcpInstall aft.page MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.plugins] url = "https://mcp.aft.page/mcp"
Install aft.page MCP in Gemini CLI
$ gemini mcp add -s user --transport http plugins https://mcp.aft.page/mcpInstall aft.page MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"plugins": {
"url": "https://mcp.aft.page/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableaft-page/plugins is public and reachablegithub.com/aft-page/plugins ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-29github.com/aft-page/plugins ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 652 msPass
README
View on GitHubaft.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
Entire: the aft CLI as entire aft …
(binary from this repo's releases, named by entire-plugin.yml):
entire plugin install https://github.com/aft-page/plugins
entire aft deploy
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
entire-plugin.yml Entire CLI plugin manifest (binaries ship as releases)
Issues and questions: hello@aft.page · aft.page
aft.page MCP questions
How do I add aft.page MCP to Claude Code?
Run claude mcp add --transport http plugins https://mcp.aft.page/mcp in your terminal. Add --scope user to make it available in every project.
How do I add aft.page MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What can I deploy using aft.page?
You can deploy static sites, build outputs (like Vite or Next.js static exports), and public GitHub repositories including Node, Python, and Dockerfile apps.
Do I need an account for my first deployment?
No, you do not need an account to perform your first deployment.
How can I make my deployment private?
A first deploy is public immediately, but you can claim it via a link returned by the agent to make it private.
Can I revert to a previous version of my site?
Yes, you can use the rollback tool to return to an earlier deployment on the same URL.