Drop2Run MCP server

drop2run-cli

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.

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:

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 . The other commands are init, ls, open, rollback, rm, token list, whoami and where, and --json on any of them prints machine-readable output.

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:

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

It exposes six tools — publishfiles, publishdir, listsites, deletesite, and login / logincode to get a token without leaving the chat. The publishes answer with structured fields beside the sentence, so a URL does not have to be read back out of prose; deletesite is permanent and asks for the site's subdomain repeated back before it runs. The token goes to the same place the CLI stores one, so signing in through either covers both.

Each package documents itself in full, including the sign-in flows and what happens without a site: packages/cli/README.md and packages/mcp/README.md. The hosted documentation is at dropto.run/docs/cli and dropto.run/docs/mcp.

What is in here

core and node are not published. They are bundled into each package's dist/ at build time, which is why drop2run installs with no runtime dependencies at all — an intentional choice for something that holds a token. @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.

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

Shortened. The full README is on GitHub.