Publica contenido generado por IA, markdown, PDFs o sitios web completos mediante enlaces HTTPS en vivo.
También conocido como Drop-to-run/drop2run-cli, drop2run-cli, @drop2run/mcp
- Stars
- 3
- Herramientas
- —
- Descargas, 30 días
- 1535
- Última versión
- 1.5.0
- Último commit
- 13 nov 2026
- Licencia
- MIT
¿Qué es Drop2Run MCP?
Publica contenido generado por IA, markdown, PDFs o sitios web completos mediante enlaces HTTPS en vivo.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Drop2Run
Con Drop2Run, los desarrolladores pueden convertir contenido generado por IA, markdown, PDFs o sitios web completos en enlaces HTTPS activos. Esta herramienta permite que un agente de IA publique su resultado en la web de forma inmediata, lo que resulta muy útil para compartir documentación, informes o prototipos web directamente desde una interfaz de chat. El sistema ofrece veinte herramientas especializadas organizadas en grupos para publicación, gestión de sitios, uso compartido, comentarios y autenticación.
Los usuarios pueden interactuar con el servicio a través de una herramienta de línea de comandos local o un MCP server. Para clientes de escritorio como Claude en macOS o Windows, puedes instalar el servidor mediante un bundle. Los usuarios de Claude Code pueden añadirlo con un solo comando, mientras que los clientes basados en web como ChatGPT utilizan una versión alojada. Las instalaciones locales permiten publicar directorios completos desde tu disco usando la herramienta publish_dir, mientras que la versión alojada se limita a la publicación de archivos de texto. La autenticación se gestiona mediante un inicio de sesión en el navegador o un DROP2RUN_TOKEN para entornos de integración continua.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Drop2Run MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Drop2Run MCP en Claude Code
$ claude mcp add drop2run-cli -- npx -y @drop2run/mcpInstalar Drop2Run MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"drop2run-cli": {
"command": "npx",
"args": [
"-y",
"@drop2run/mcp"
]
}
}
}Instalar Drop2Run MCP en VS Code
.vscode/mcp.json
{
"servers": {
"drop2run-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@drop2run/mcp"
]
}
}
}Instalar Drop2Run MCP en VS Code CLI
$ code --add-mcp '{"name":"drop2run-cli","type":"stdio","command":"npx","args":["-y","@drop2run/mcp"]}'Instalar Drop2Run MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"drop2run-cli": {
"command": "npx",
"args": [
"-y",
"@drop2run/mcp"
]
}
}
}Instalar Drop2Run MCP en Codex
$ codex mcp add drop2run-cli -- npx -y @drop2run/mcpInstalar Drop2Run MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.drop2run-cli] command = "npx" args = ["-y", "@drop2run/mcp"]
Instalar Drop2Run MCP en Gemini CLI
$ gemini mcp add -s user drop2run-cli npx -- -y @drop2run/mcpInstalar Drop2Run MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"drop2run-cli": {
"command": "npx",
"args": [
"-y",
"@drop2run/mcp"
]
}
}
}Verificaciones automáticas
Ejecutado 13 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesibledrop-to-run/drop2run-cli is public and reachablegithub.com/drop-to-run/drop2run-cli ↗Aprobado
- El paquete indica este repositorio como su origen@drop2run/mcp names drop-to-run/drop2run-cli as sourcenpmjs.com/package/@drop2run/mcp ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)No build attestation published for this releaseNo verificado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-11-13github.com/drop-to-run/drop2run-cli ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from @drop2run/mcpAprobado
- No hay avisos críticos en el paquete ni en sus dependenciasthe package checked; no critical advisoryosv.dev ↗Aprobado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPHTTPS endpoint answered 401 (sign-in required)Aprobado
README
Ver en GitHubdrop2run-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.
Preguntas sobre Drop2Run MCP
¿Cómo agrego Drop2Run MCP a Claude Code?
Ejecuta claude mcp add drop2run-cli -- npx -y @drop2run/mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Drop2Run MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.