aft.page

page.aft由 aft.page 发布官方发布者v1.1.0更新于 Oct 25, 2026

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

已验证Streamable HTTP可网页运行云端与基础设施开发者工具

概览

AI 生成的概览

远程 MCP 服务器，让助手把 HTML、构建产物或公开 GitHub 仓库发布到可访问的网址，并可查看版本、回滚和提升预览。

可以做什么
  • 把单个 HTML 页面或构建好的站点目录发布到线上网址
  • 构建并部署公开的 GitHub 仓库，包括 Next.js、Node、Python 和 Dockerfile 应用
  • 列出站点的部署版本，含标签、提交以及线上或预览状态
  • 把线上网址回滚到较早版本，或将保留的预览提升为线上
  • 检查与部署 API 的连接状态
适用场景
适合希望让编码助手把页面、静态构建或公开仓库直接发布成可分享网址、无需自行搭建托管，并在同一对话中管理后续版本与回滚的场景。
运行要求
远程 streamable HTTP 端点，首次部署无需本地包或账号。更新、列出版本、回滚和提升需要站点的 edit_token，助手会将其保存在 .aft/state.json 中。仅支持公开的 GitHub 仓库。
安装前请注意
首次部署会立即公开，需通过认领（claim）才能保留并设为私有。edit_token 保存在 .aft/state.json，应避免提交到 git。切勿部署 .env、密钥或凭据等机密。部署会写入内容并发布到公开网址。

安装

在 SourceWeft 中

  1. 打开 控制台中的 aft.page，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/page.aft%2Fmcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "aft-page": {
      "type": "http",
      "url": "https://mcp.aft.page/mcp"
    }
  }
}

README

aft.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

text
/plugin marketplace add aft-page/plugins/plugin install aft-page@aft-page

Codex, Copilot CLI, VS Code, and other agents via the plugins installer:

bash
npx plugins add aft-page/plugins

Entire: the aft CLI as entire aft … (binary from this repo's releases, named by entire-plugin.yml):

bash
entire plugin install https://github.com/aft-page/pluginsentire aft deploy

Any MCP client (no plugin):

json
{  "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:

ToolDoes
deployPublish HTML or a built folder; update it with the same slug + edit token
deploy_repoBuild and publish a public GitHub repo
aft_deploysList a site's deploy history
aft_rollbackRoll back to an earlier deploy on the same URL
aft_healthCheck 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

text
.cursor-plugin/plugin.json   Cursor manifest.claude-plugin/              Claude Code manifest + marketplace.plugin/plugin.json, .mcp.json   `npx plugins` manifest + MCPplugin.json, mcp.json        Agent Plugins manifest + MCPskills/deploy-to-aft/        the skillentire-plugin.yml            Entire CLI plugin manifest (binaries ship as releases)

Issues and questions: [email protected] · aft.page

来源：README.md，提交 fbb6365

工具

6

deploy

Deploy to aft.page

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, then files from dist/. Next static export → files from out/; a static site needs index.html. Flask/FastAPI/Django/Express → the source files with requirements.txt or package.json; aft builds and runs it. Never upload node_modules, .venv, or .next/. First hit: preferred_slug from aft.json (include aft.json in files). Later: same slug + edit_token from .aft/state.json — every update is a new version (v1, v2…) at the same URL. Pass hold:true to keep an update as a preview until aft_promote. label names the version. Limits: 500 files, 25MB each, 100MB total.

输入参数holdhtmlfileslabelexpiresedit_tokenpreferred_slug

deploy_repo

Deploy a public GitHub 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.

输入参数url必填

aft_deploys

List aft.page deploy history

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/state.json (or the first deploy). Same history the project UI shows after claim.

输入参数slug必填edit_token必填

aft_rollback

Rollback aft.page site

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. Claim not required.

输入参数slug必填versiondeploy_idedit_token必填

aft_promote

Promote a held aft.page version

Make a held preview version live at the same URL. Pass version (e.g. 4) or deploy_id from aft_deploys. Needs edit_token.

输入参数slug必填versiondeploy_idedit_token必填

aft_health

Check aft.page API

Ping the aft.page deploy API.

无需输入参数。

版本历史

2
  1. v1.1.0最新Oct 25, 2026
  2. v1.0.0Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分