Back to Browse

Publish My MCP Server

Developer ToolsLow Risk10.0MCP RegistryLocalRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://api.publish.my/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (4 strong, 3 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 2 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

file_system

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

Optional. A publish.my API key; without it the first publish gives a preview link and the key is saved to ~/.publishmy when the user activates.Required

Environment variable: PUBLISHMY_API_KEY

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub 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

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

Cursor: 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-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

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

Reviews

No reviews yet

Be the first to review this server!