publish.my

my.publish由 publish.my 發布官方發布者v0.1.0更新於 Oct 30, 2026

Publish a folder as a live website at https://<id>.publish.my. Free, no account needed.

已驗證Streamable HTTP可網頁執行雲端與基礎設施開發者工具

概覽

AI 產生的概覽

把本機資料夾發佈成 publish.my 上的公開靜態網站並回傳網址，還能檢查啟用狀態、列出網站與復原存取權限。

可以做什麼
  • 將含 index.html 的資料夾發佈為公開靜態網站並取得網址，也可更新既有網站
  • 檢查新發佈的網站是否已由站主透過電子郵件確認啟用
  • 列出使用者的網站及其網址、狀態與 30 天瀏覽量
  • 在本機金鑰遺失後，寄送確認連結給站主以復原已上線網站的存取
適用情境
適合使用者想把頁面、示範、報告或原型放到網路上並以連結分享，而不想自行架設主機時使用。也適合從同一個資料夾更新已發佈的網站。
執行需求
可作為 api.publish.my 的遠端端點使用（供沒有檔案系統的用戶端，需登入一次），也可透過 npx publish-my 在本機執行，需 Node 20 以上版本。需要 OAuth 登入或選用的 PUBLISHMY_API_KEY；首次發佈需使用者填寫電子郵件並點擊確認連結。僅支援靜態檔案，框架應用程式需先建置。
安裝前請注意
發佈會把資料夾內容上傳到公開網址，其中任何內容都可被公開讀取；.env 等隱藏檔案、node_modules 及不支援的類型會被排除並回報。API 金鑰儲存在 ~/.publishmy，各網站金鑰儲存在 ~/.config/publish-my 下，專案內也會記錄資料夾對應的網站。更新已上線網站需先詢問使用者再設定 confirm_update。沒有刪除工具，網站須在主控台刪除。免費額度：每帳號 500 MB、每次上傳 50 MB、每網站 2,000 個檔案。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 publish.my，將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存，絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/my.publish%2Fpublish-my/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "publish-my": {
      "type": "http",
      "url": "https://api.publish.my/mcp"
    }
  }
}

README

publish-my

MCP server for publish.my: your AI agent publishes a folder as a live website at https://<id>.publish.my. Free, and no account needed to start.

Ask your agent to "put this online" and it calls publish_site. The first publish gives a preview link; the user enters their email on that page once and the site goes live at the same address. After that, every publish goes live immediately.

Install

Claude Code

sh
claude mcp add publish-my -- npx -y publish-my

Cursor: add this to ~/.cursor/mcp.json

json
{ "mcpServers": { "publish-my": { "command": "npx", "args": ["-y", "publish-my"] } } }

VS Code

sh
code --add-mcp '{"name":"publish-my","command":"npx","args":["-y","publish-my"]}'

Codex

sh
codex mcp add publish-my -- npx -y publish-my

Claude Desktop, Windsurf and other MCP clients: a stdio server running npx -y publish-my (Node 20 or newer).

claude.ai and ChatGPT have no filesystem, so they use the remote connector instead: add a custom connector with the URL https://api.publish.my/mcp and sign in to publish.my once.

Tools

ToolWhat it does
publish_sitePacks a folder (with index.html at its top) and publishes it. Updating a live site needs confirm_update: true, which the agent sets after asking the user.
check_activationChecks whether the user has confirmed their email for a new site.
list_sitesLists the user's sites with status and 30-day views.
reconnect_siteRecovers access to a live site after the key on this machine was lost.

There is no delete tool. Sites are deleted in the console.

What it stores

The same files the curl flow uses, so the two stay interchangeable:

  • ~/.publishmy: your publish.my API key (mode 600), saved when you activate your first site. A working key here is never replaced by a key for a different account.
  • ~/.config/publish-my/keys/<site id> (mode 600): if a site gets activated on a different account than the key in ~/.publishmy, its key is kept here and used only for that site.
  • <project>/.publish-my.json: which publish.my site this folder is, so "publish again" updates the same address.
  • ~/.config/publish-my/pending.json (mode 600): secrets for sites waiting for activation. It is kept out of the project folder so it never ends up in git.

Hidden files (.env and similar), node_modules and file types publish.my does not host are left out of the upload. The tool reports what it left out.

Environment overrides: PUBLISHMY_API_KEY, and PUBLISHMY_API_URL for testing.

Limits (free)

500 MB per account, unlimited sites, 50 MB per upload, 2,000 files per site, static files only. Framework apps (Next.js, Vite, Astro, SvelteKit, Nuxt) must be built first; publish the output folder. Full details: https://publish.my/agents/

Development

sh
npm test                    # unit tests./scripts/e2e-dev.sh        # full flow against a local publish.my DEV server (needs the app repo)node scripts/client.mjs list

來源：README.md，提交 4818f88

工具

4

publish_site

Publish a folder as a website

Publish a local folder (with index.html at its top) as a public static website on publish.my and return its URL. Use for "publish", "deploy", "host", "put online", "share a link", and "publish again / update the site". The first publish of a folder gives a preview URL the user activates by entering their email on that page; after that, publishes go live immediately. Re-publishing a folder that is already live updates the same URL: ask the user first, then pass confirm_update: true. Framework apps (Next.js, Vite, Astro, SvelteKit, Nuxt) must be built/exported first; pass the output folder (out/, dist/, build/, .output/public).

輸入參數path必填new_siteproject_idconfirm_update

check_activation

Check site activation

Check whether the user has activated a newly published site (entered their email and clicked the link). When they have, the site is live and the publish.my key is saved for future updates.

輸入參數project_id

list_sites

List my sites

List the user's publish.my sites with their URLs, status and 30-day views.

無需輸入參數。

reconnect_site

Reconnect a live site

Use when a site is already live but this machine lost its publish.my key (updates fail with 401/403 or "no key"). Emails the site owner a confirm link; once clicked, the key is saved and updates work again.

輸入參數pathproject_id

版本歷史

1
  1. v0.1.0最新Oct 23, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分