Publishes what an AI made — a page, a markdown or PDF doc, or a whole site — to a live HTTPS link.
run.dropto/drop2run Model Context Protocol (MCP) Server
The run.dropto/drop2run MCP server publishes a folder, an HTML page, or a markdown note as a static site. After publishing, it returns a live HTTPS URL for the generated content.
🛠️ Key Features
Publishes a folder as a static site
Publishes an HTML page as a static site
Publishes a markdown note as a static site
Returns a live HTTPS URL
🚀 Use Cases
Host prebuilt static assets from a local folder
Convert and publish an HTML page for immediate access via HTTPS
Publish markdown content as a static site and share a live HTTPS link
⚡ Developer Benefits
Produces an HTTPS-accessible URL for the published output
Supports multiple input formats: folder, HTML, and markdown
⚠️ Limitations
Description does not specify additional tools, authentication, or configuration options
No details provided about build steps, themes, or supported markdown features
Source for the two Drop2Run packages that run on your machine: the drop2run
command line tool and the @drop2run/mcp server.
Both are installed globally and then handed a credential. This repository exists so you can read what
you are giving that credential to.
bash
npm i -g drop2run # https://www.npmjs.com/package/drop2run
npx @drop2run/mcp # https://www.npmjs.com/package/@drop2run/mcp
Using them
The command line tool signs in through a browser and publishes a folder:
bash
drop2run login
drop2run deploy dist
login needs a browser on the same machine; drop2run login --device covers a remote shell, and CI
uses a DROP2RUN_TOKEN from https://app.dropto.run/account/tokens. The other commands include
init, ls, open, info, set and unset (a site's settings, its API upstreams and the keys its
functions read), rollback, rm, comments, invite, token list, whoami and where, and
--json on any of them prints machine-readable output. deploy bundles a folder's _functions/ —
serverless functions, on the plans that include them — on your machine before uploading;
--no-bundle skips that.
The MCP server is registered with a client rather than run by hand. Claude for macOS and Windows
installs it from a bundle — download drop2run.mcpb and open it,
and there is no config file and nothing to install first. Claude Code takes one command:
bash
claude mcp add drop2run -s user -- npx -y @drop2run/mcp
A chat that cannot run a package — Claude on the web or a phone, ChatGPT — adds the hosted copy of the
same server by URL instead, https://mcp.dropto.run/mcp, and signs in to Drop2Run when it connects. In
Claude it is also listed in the
connector directory. Its
tools come from packages/mcp here (src/remote.ts); the sign-in in front of them does not. It
publishes text files only, and the setup is at dropto.run/docs/mcp.
It exposes twenty-five tools, in six groups:
Group
Tools
Publish
publish_files, publish_dir — the second reads a folder on disk, so it is local only
store_list, store_get, store_put, store_delete, store_export — what a site's functions keep; no tool empties a whole store
Sign-in
login, login_code — local server only; the hosted copy signs in when it connects
The publishes answer with structured fields beside the sentence, so a URL does not have to be read back
out of prose. delete_site and change_subdomain ask for the site's current subdomain repeated back
before they run; pause_site is the reversible way to take a site off the air. The token goes to the
same place the CLI stores one, so signing in through either covers both.
An MCP server, so an agent can publish what it just wrote
packages/core
no
The deploy engine — manifest, hashing, upload, go-live. No Node APIs, no browser APIs
packages/node
no
The parts that need fs: reading a folder, the config file, the token store
core and node are not published. They are bundled into each package's dist/ at build time, which
is why drop2run installs with one runtime dependency — an intentional choice for something that
holds a token. That one is esbuild, which bundles a site's _functions/ on your machine and is
loaded only when there is something to bundle. @drop2run/mcp has two, both required by the
protocol: @modelcontextprotocol/sdk and zod.
Building and testing
Each package stands alone — there is no workspace root, and internal imports resolve through the
relative paths in each tsconfig.json.
bash
cd packages/cli # or mcp, or node
npm ci
npm run typecheck
npm test
npm run build # writes dist/, which is what npm ships
packages/core has no dependencies and no build of its own; it is typechecked by the packages that
bundle it.
Where the rest is
This repository is an export of the four packages above, with their full history. The Drop2Run service
itself — the API, the edge router, the dashboard — is not here and is not open source. What that means
in practice: the code that decides what happens to a file after it leaves your machine is not something
this repository lets you audit. What it does let you audit is everything that happens to your files and
your token before that point, which is the part that runs with your privileges.
Issues about the CLI or the MCP server are welcome here. Anything about the hosted service belongs at
dropto.run/contact.
Pull requests are welcome too, with one thing worth knowing first: this repository is generated, so a
pull request is not merged here. The change is applied in the source repository and reaches this
one in the next export, with your commit and its authorship carried along; the pull request is then
closed with a link to the commit. Merging it here instead would put a commit in this history that no
future export contains, and the two would diverge on the very next update.