Purpose
drop2run-cli is the source repository for Drop2Run's two local runtime packages: the drop2run command-line tool and the @drop2run/mcp server. Both are installed globally first, and then they are given a credential. The purpose of the repository is to let users read what code they have handed their credential to.
Its core purpose is to publish the output of a static site or an agent as an HTTPS link, without git and without build configuration. Static hosting runs on Cloudflare's edge network.
Main capabilities
The command-line tool logs in through a browser and publishes a folder. Logging in requires a browser on the same machine;drop2run login --device covers remote shell scenarios, and CI uses the https://app.dropto.run/account/tokens from DROP2RUN_TOKEN. Other commands include init、ls、open、rollback、rm、token list、whoami and where, and any command plus --json outputs machine-readable results.
The MCP server is used by registering it with a client, rather than running it manually. Claude for macOS and Windows installs from a bundle—download drop2run.mcpb and open it, with no configuration file and no need to install anything first. Claude Code connects with a single command.
The tools it exposes include: publish_files, publish_dir, list_sites, list_folders, delete_site, get_site, update_site, pause_site, resume_site, and rollback_site, as well as login / login_code for getting a token directly in chat. The return result of a publish operation has structured fields in addition to the sentence, so the URL does not have to be read back from natural language; delete_site is permanent, and before running it requires retyping the site's subdomain for confirmation. The token is stored in the same location as the CLI, so logging in through either one covers both.
Each package has complete documentation, including the login flow and what happens when there are no sites: packages/cli/README.md and packages/mcp/README.md. Hosted documentation is at dropto.run/docs/cli and dropto.run/docs/mcp.
Usage
The repository contains the CLI and MCP packages; core and node are not published, and are bundled into each package's dist/ at build time, so drop2run has no runtime dependencies at all after installation—this is a deliberate choice for a tool that holds a token. @drop2run/mcp has two dependencies required by the protocol: @modelcontextprotocol/sdk and zod.
Suitable scenarios
Suitable for users who need to quickly publish a static site or AI agent output as an HTTPS link, especially workflows that want to skip git and build configuration and need to publish directly from chat or a local folder.
Limitations
The Drop2Run service itself—the API, the edge router, the dashboard—is not in this repository, and is not open source. This means what happens after files leave the local machine cannot be audited through thisrepository; what can be audited is all handling of files and tokens before they reach that point, which is the part running with user permissions. Questions about the CLI or MCP server are welcome here; questions about the hosted service should go to dropto.run/contact. This repository is generated, so pull requests are not merged here; changes are applied in the source repository and enter this repository on the next export, preserving commit and author information.
