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 分