Veröffentlicht KI-generierte Inhalte, Markdown, PDFs oder komplette Websites über Live-HTTPS-Links.
Auch bekannt als Drop-to-run/drop2run-cli, drop2run-cli, @drop2run/mcp
- Stars
- 3
- Tools
- —
- Downloads, 30 Tage
- 1.535
- Neueste Version
- 1.5.0
- Letzter Commit
- 13. Nov. 2026
- Lizenz
- MIT
Was ist Drop2Run MCP?
Veröffentlicht KI-generierte Inhalte, Markdown, PDFs oder komplette Websites über Live-HTTPS-Links.
Zusammenfassung generiert aus dem README des Projekts
Über Drop2Run MCP server
Mit Drop2Run können Entwickler KI-generierte Inhalte, Markdown, PDFs oder ganze Websites in Live-HTTPS-Links verwandeln. Dieses Tool ermöglicht es einem AI Agent, seine Ergebnisse sofort im Web zu veröffentlichen, was ideal zum Teilen von Dokumentationen, Berichten oder Web-Prototypen direkt aus einem Chat-Interface ist. Das System bietet zwanzig spezialisierte Tools, die in Gruppen für Publishing, Site Management, Sharing, Comments und Authentication organisiert sind.
Nutzer können mit dem Service über ein lokales CLI-Tool oder einen MCP server interagieren. Für Desktop-Clients wie Claude auf macOS oder Windows kannst du den Server über ein Bundle installieren. Claude Code Nutzer können ihn mit einem einzigen Befehl hinzufügen, während webbasierte Clients wie ChatGPT eine hosted Version nutzen. Lokale Installationen erlauben es, ganze Verzeichnisse von deiner Festplatte mit dem publish_dir Tool zu veröffentlichen, während die hosted Version auf das Veröffentlichen von Textdateien beschränkt ist. Die Authentication erfolgt über einen browserbasierten Login oder einen DROP2RUN_TOKEN für Continuous Integration Umgebungen.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Drop2Run MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenDrop2Run MCP in Claude Code installieren
$ claude mcp add drop2run-cli -- npx -y @drop2run/mcpDrop2Run MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"drop2run-cli": {
"command": "npx",
"args": [
"-y",
"@drop2run/mcp"
]
}
}
}Drop2Run MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"drop2run-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@drop2run/mcp"
]
}
}
}Drop2Run MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"drop2run-cli","type":"stdio","command":"npx","args":["-y","@drop2run/mcp"]}'Drop2Run MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"drop2run-cli": {
"command": "npx",
"args": [
"-y",
"@drop2run/mcp"
]
}
}
}Drop2Run MCP in Codex installieren
$ codex mcp add drop2run-cli -- npx -y @drop2run/mcpDrop2Run MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.drop2run-cli] command = "npx" args = ["-y", "@drop2run/mcp"]
Drop2Run MCP in Gemini CLI installieren
$ gemini mcp add -s user drop2run-cli npx -- -y @drop2run/mcpDrop2Run MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"drop2run-cli": {
"command": "npx",
"args": [
"-y",
"@drop2run/mcp"
]
}
}
}Automatisierte Checks
Geluften am 13. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbardrop-to-run/drop2run-cli is public and reachablegithub.com/drop-to-run/drop2run-cli ↗Bestanden
- Paket nennt dieses Repository als Quelle@drop2run/mcp names drop-to-run/drop2run-cli as sourcenpmjs.com/package/@drop2run/mcp ↗Bestanden
- Build-Provenienz (Sigstore-Attestierung)No build attestation published for this releaseNicht geprüft
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-11-13github.com/drop-to-run/drop2run-cli ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNo popular package one edit away from @drop2run/mcpBestanden
- Keine kritischen Advisories im Paket oder seinen Abhängigkeitenthe package checked; no critical advisoryosv.dev ↗Bestanden
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeHTTPS endpoint answered 401 (sign-in required)Bestanden
README
Auf GitHub ansehendrop2run-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 https://app.dropto.run/account/tokens. 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
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 tools, in five groups:
| Group | Tools |
|---|---|
| Publish | publish_files, publish_dir — the second reads a folder on disk, so it is local only |
| Sites | list_sites, list_folders, get_site, update_site, pause_site, resume_site, rollback_site, change_subdomain, delete_site |
| Sharing | list_people, invite_people, remove_person |
| Comments | list_comments, reply_comment, resolve_comment, reopen_comment |
| 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.
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
| Package | Published | What it is |
|---|---|---|
packages/cli |
drop2run |
The command line tool: login, deploy, ls, rollback, rm |
packages/mcp |
@drop2run/mcp |
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 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
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.
Licence
MIT.
Drop2Run MCP Fragen
Wie füge ich Drop2Run MCP zu Claude Code hinzu?
Führe claude mcp add drop2run-cli -- npx -y @drop2run/mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Drop2Run MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.