Drop2Run MCP

Your agent can write the page. Now it can publish it.

One tool call and the HTML it just wrote is live on its own HTTPS address. No repository, no build config, no dashboard in the loop.

Claude DesktopmacOS · Windows

Open the file and Claude shows an install dialog. Nothing to install first.

Claude Codenothing installs globally

claude mcp add drop2run -s user -- npx -y @drop2run/mcp

Then ask for a publish. With no token stored, Claude signs you in through a browser first — nothing to install, nothing to paste. Cursor, VS Code and the rest: the MCP docs, which are the copy that stays current.

Whatever it wrote, in whatever shape it wrote it.

A page as a string, a note it just wrote, a folder of anything readable. None of it has to be a repository first, and markdown does not have to be built into a site. All six tools →

• publish_files

  Whatever it just wrote

  A page, a note, a page and its stylesheet. Hand over the contents and a URL comes back — nothing is written to disk on the way, and markdown publishes as itself, read through a viewer rather than wrapped in HTML to get there.
• publish_dir

  Or whatever is already on disk

  A built site, a directory of .md, a single .pdf — pointed at by path, so the bytes never pass through the conversation.
• list_sites

  Publish over the same one

  So the second attempt updates the site instead of leaving a second URL nobody reads.

Three things, before the first call.

Every publish lands on its own subdomain over HTTPS, from the edge network. These are the parts that surprise people afterwards.

• ✕ The default subdomain is not indexed. Deliberately, so a page an agent published on a whim does not turn up in search. A custom domain is the paid tier's job, and does not carry that header.
• ✕ A publish with no account does not last past 3 days. Signing in makes it permanent, and the same token can claim a site that was published without one.
• ✕ Static files only. No server running your code, no environment variables at request time, no database. If the page needs any of those it needs a different host, and the home page names which cases those are.

Three pages, three different questions.

• /docs/mcp

  Set the server up

  Every client, both ways to sign in, publishing over an existing site, and what the server does not send anywhere.
• /docs/claude

  Drive it from Claude

  Claude Code and Claude Desktop end to end — including what to expect it to get wrong, and what stops that.
• /docs/for-agents

  Teach an agent the rules

  A skill file at a stable URL, so publishing does not have to be explained to the agent each time.

Add it, then ask for a page.

One line at the top of this page, then “publish this as a site”. The link comes back in the same reply.