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 分