publish-my
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@publish-my publish this folder as a live website"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
claude mcp add publish-my -- npx -y publish-myCursor: add this to ~/.cursor/mcp.json
{ "mcpServers": { "publish-my": { "command": "npx", "args": ["-y", "publish-my"] } } }VS Code
code --add-mcp '{"name":"publish-my","command":"npx","args":["-y","publish-my"]}'Codex
codex mcp add publish-my -- npx -y publish-myClaude 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.
Related MCP server: StaticX MCP Server
Tools
Tool | What it does |
| Packs a folder (with |
| Checks whether the user has confirmed their email for a new site. |
| Lists the user's sites with status and 30-day views. |
| Recovers 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
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 listAvailable Tools
4 toolscheck_activationCheck site activationBIdempotentInspect
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.
Inputs: project_id.
list_sitesList my sitesARead-onlyInspect
List the user's publish.my sites with their URLs, status and 30-day views.
Inputs: no named parameters.
publish_sitePublish a folder as a websiteADestructiveInspect
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).
Inputs: path (required), new_site, project_id, confirm_update.
reconnect_siteReconnect a live siteAInspect
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.
Inputs: path, project_id.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a distinct step in the static-hosting lifecycle (publish, check activation, list, reconnect), and descriptions spell out the trigger conditions. The only soft overlap is between check_activation and reconnect_site, since both hinge on the user clicking an emailed link, though the preconditions (new site vs. lost key) are stated clearly enough to separate them.
All four tools follow a uniform snake_case verb_noun pattern (publish_site, check_activation, list_sites, reconnect_site). No mixed conventions or vague standalone verbs.
Four tools is a tight, purposeful surface for a static-site publishing service, with each tool earning its place. It sits at the low end of the comfortable range, but nothing feels redundant or padded.
Publish (create), re-publish (update), list (read), activation check, and key recovery are covered, so the core loop is closed. However, there is no way to unpublish/delete a site, rename it, or inspect a single site's details, which are predictable needs for a hosting service.
Maintenance
Related MCP Connectors
Deploy static sites from AI agents: deploy_site publishes files and returns a live URL in seconds.
Put the page your AI made online at yourname.nsd.sg. Publish, update, list and remove sites.
Publish websites from AI: create sites, upload HTML/images, access control, custom domains.
Build and publish a website from a chat. No account or API key needed; you get a live link to share.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to deploy static websites to the Demox platform with automatic directory packaging and cloud storage integration. It includes tools for managing deployments, such as listing, viewing, and deleting websites.725 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to deploy static websites to StaticX, including creating sites, uploading builds, publishing releases, and managing domains.23 npmMIT
- AlicenseNot gradedqualityCmaintenancePublish the website you built with AI to a live public URL — straight from chat, no setup. Enables deploying static sites and updating them with edit tokens.1MIT

drop2run-mcpofficial
AlicenseAqualityBmaintenancePublishes what an AI made — a page, a markdown or PDF doc, or a whole site — to a live HTTPS link. Runs locally over stdio from the @drop2run/mcp npm package, or hosted at https://mcp.dropto.run/mcp for chats that connect by URL.203MIT