Despliega sitios web estáticos, landing pages y prototipos al instante a través de un agente de IA.
También conocido como shipstatic/mcp, mcp, @shipstatic/mcp
- Stars
- 6
- Herramientas
- 15
- Descargas, 30 días
- —
- Última versión
- 2.8.3
- Último commit
- 12 nov 2026
- Licencia
- MIT
¿Qué es ShipStatic MCP?
Despliega sitios web estáticos, landing pages y prototipos al instante a través de un agente de IA. Expone 15 herramientas, como deployments_upload, deployments_list, deployments_get.
Resumen generado a partir del README del proyecto
Acerca del MCP server de ShipStatic
ShipStatic permite a los desarrolladores desplegar sitios web estáticos, landing pages y prototipos mediante un agente de IA. Funciona como un servicio remoto a través de una URL alojada o como un proceso local utilizando un SHIP_TOKEN. Los usuarios pueden conectarlo con varios clientes, incluyendo Claude Desktop, Cursor, Claude Code y VS Code. El servidor proporciona quince herramientas para gestionar todo el ciclo de vida del despliegue.
Para usuarios sin cuenta, la herramienta deployments_upload permite la publicación instantánea de archivos en una URL en vivo. Estos sitios anónimos permanecen activos durante tres días a menos que se utilice un enlace de reclamación. Los usuarios registrados tienen acceso a funciones avanzadas como la gestión de dominios personalizados, el listado de todos los despliegues y la configuración de duraciones específicas de tiempo de vida para la limpieza automática. El sistema también admite la protección por contraseña para mantener despliegues específicos privados frente a los visitantes.
Qué puedes hacer con él
- 1Despliegue instantáneo de prototiposPide a tu agente de IA que tome tus archivos actuales y los suba a internet de inmediato.
- 2Previsualizaciones privadas segurasSolicita a tu agente que publique un sitio con protección por contraseña integrada para los visitantes.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar ShipStatic MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar ShipStatic MCP en Claude Code
$ claude mcp add mcp -- npx -y @shipstatic/mcpInstalar ShipStatic MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@shipstatic/mcp"
]
}
}
}Instalar ShipStatic MCP en VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@shipstatic/mcp"
]
}
}
}Instalar ShipStatic MCP en VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@shipstatic/mcp"]}'Instalar ShipStatic MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@shipstatic/mcp"
]
}
}
}Instalar ShipStatic MCP en Codex
$ codex mcp add mcp -- npx -y @shipstatic/mcpInstalar ShipStatic MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@shipstatic/mcp"]
Instalar ShipStatic MCP en Gemini CLI
$ gemini mcp add -s user mcp npx -- -y @shipstatic/mcpInstalar ShipStatic MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@shipstatic/mcp"
]
}
}
}Iniciado por HostedMCP el 16 nov 2026
Ejecutamos este comando para @shipstatic/mcp 2.8.3 en un contenedor aislado sin red ni claves. Respondió y listó 15 herramientas.
Herramientas de ShipStatic MCP 15
Leído del servidor con tools/listdeployments_uploadAcciónDeploy a static site to a live URL: free, no account or API key required. **File content is plain text by default.** Pass HTML/CSS/JS/JSON/SVG/etc. directly in each file's `content` as a regular string. Only set `encoding: "base64"` per-file for binary content (images, fonts) — do not base64-encode text. Returns the live URL. Without a connected account, the response also includes a one-time claim URL, and the site expires in 3 days unless claimed. Pass `password` to make the site private.
deployments_listSolo lecturaList all deployments with their URLs, status, labels, and password protection state. The response's `cursor` is null on the last page; pass it back as `cursor` to fetch the next.
deployments_getSolo lecturaGet deployment details including URL, status, file count, size, labels, and password protection state.
deployments_setAcciónUpdate deployment labels. Replaces all existing labels.
deployments_deleteAcciónPermanently deletes a deployment and its files.
domains_setAcciónCreate or update a domain: a ShipStatic domain (e.g. "yourname.shipstatic.com"), live as soon as a deployment is linked, or a custom domain (e.g. "www.example.com"), which needs DNS records first. Can reserve a name (omit deployment), link it to a deployment, switch deployments, or update labels. For a custom domain, domains_records then returns the DNS records to configure.
domains_listSolo lecturaList all domains with their URLs, linked deployment, and `status`. The response's `cursor` is null on the last page; pass it back as `cursor` to fetch the next.
domains_getSolo lecturaGet domain details including URL, linked deployment, labels, and `status`: the one word saying what the domain needs from its owner (`unverified`, `unlinked`, `live`, `paused`).
domains_recordsSolo lecturaReturns the DNS records to configure at the domain's DNS provider. Call after domains_set. Custom domains only: a ShipStatic domain has no records to configure.
domains_dnsSolo lecturaReturns the DNS provider recorded for the domain, if known (e.g. Cloudflare, Namecheap): where its DNS records are configured. Custom domains only, and only while the domain is unverified; once its DNS is right there is nothing left to locate.
domains_shareSolo lecturaReturns a shareable DNS setup URL that needs no API key, for whoever manages the domain's DNS. Custom domains only, and only while the domain is unverified; a verified domain has no setup left to share.
domains_validateSolo lecturaCheck if a domain name is valid and available before creating it. Returns the normalized form and availability.
| deployments_upload | Deploy a static site to a live URL: free, no account or API key required. **File content is plain text by default.** Pass HTML/CSS/JS/JSON/SVG/etc. directly in each file's `content` as a regular string. Only set `encoding: "base64"` per-file for binary content (images, fonts) — do not base64-encode text. Returns the live URL. Without a connected account, the response also includes a one-time claim URL, and the site expires in 3 days unless claimed. Pass `password` to make the site private. | Acción |
| deployments_list | List all deployments with their URLs, status, labels, and password protection state. The response's `cursor` is null on the last page; pass it back as `cursor` to fetch the next. | Solo lectura |
| deployments_get | Get deployment details including URL, status, file count, size, labels, and password protection state. | Solo lectura |
| deployments_set | Update deployment labels. Replaces all existing labels. | Acción |
| deployments_delete | Permanently deletes a deployment and its files. | Acción |
| domains_set | Create or update a domain: a ShipStatic domain (e.g. "yourname.shipstatic.com"), live as soon as a deployment is linked, or a custom domain (e.g. "www.example.com"), which needs DNS records first. Can reserve a name (omit deployment), link it to a deployment, switch deployments, or update labels. For a custom domain, domains_records then returns the DNS records to configure. | Acción |
| domains_list | List all domains with their URLs, linked deployment, and `status`. The response's `cursor` is null on the last page; pass it back as `cursor` to fetch the next. | Solo lectura |
| domains_get | Get domain details including URL, linked deployment, labels, and `status`: the one word saying what the domain needs from its owner (`unverified`, `unlinked`, `live`, `paused`). | Solo lectura |
| domains_records | Returns the DNS records to configure at the domain's DNS provider. Call after domains_set. Custom domains only: a ShipStatic domain has no records to configure. | Solo lectura |
| domains_dns | Returns the DNS provider recorded for the domain, if known (e.g. Cloudflare, Namecheap): where its DNS records are configured. Custom domains only, and only while the domain is unverified; once its DNS is right there is nothing left to locate. | Solo lectura |
| domains_share | Returns a shareable DNS setup URL that needs no API key, for whoever manages the domain's DNS. Custom domains only, and only while the domain is unverified; a verified domain has no setup left to share. | Solo lectura |
| domains_validate | Check if a domain name is valid and available before creating it. Returns the normalized form and availability. | Solo lectura |
Mostrar las 15 herramientasMostrar menos herramientas
domains_verifyAcciónTrigger DNS verification for a custom domain. Call after the user has configured DNS records from domains_records. Custom domains only, and refused once the domain is verified: read domains_get instead. Verification is asynchronous: read the domain again with domains_get to learn the verdict, since its `status` has not moved yet when this returns. A verified domain serves nothing until a deployment is linked with domains_set.
domains_deleteAcciónPermanently deletes a domain.
whoamiSolo lecturaReturns your email and name, and the account's plan, usage and caps.
| domains_verify | Trigger DNS verification for a custom domain. Call after the user has configured DNS records from domains_records. Custom domains only, and refused once the domain is verified: read domains_get instead. Verification is asynchronous: read the domain again with domains_get to learn the verdict, since its `status` has not moved yet when this returns. A verified domain serves nothing until a deployment is linked with domains_set. | Acción |
| domains_delete | Permanently deletes a domain. | Acción |
| whoami | Returns your email and name, and the account's plan, usage and caps. | Solo lectura |
Configuración
SHIP_TOKEN
| Nombre | Descripción | Tipo |
|---|---|---|
| SHIP_TOKEN | — |
Verificaciones automáticas
Ejecutado 16 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 accesibleshipstatic/mcp is public and reachablegithub.com/shipstatic/mcp ↗Aprobado
- El paquete indica este repositorio como su origen@shipstatic/mcp names shipstatic/mcp as sourcenpmjs.com/package/@shipstatic/mcp ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)Sigstore attestation for @shipstatic/mcpnpmjs.com/package/@shipstatic/mcp/v/2.8.3#provenance ↗Aprobado
- 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-12github.com/shipstatic/mcp ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from @shipstatic/mcpAprobado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo15 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo tool named like delete, drop or execAprobado
- El endpoint remoto responde al handshake de MCPinitialize answered with protocol 2025-11-25 in 218 ms; tools/list returned 15 toolsAprobado
README
Ver en GitHubShipStatic MCP
One URL. Your agent ships.
Deploy static websites, landing pages, and prototypes instantly. Free, no account needed.
Ask your agent to put your site online, and get back a real link you can share in seconds.
Try it in seconds, no account needed
Drop https://mcp.shipstatic.com into any MCP client. No install, no signup, no API key: your agent can publish a website in its next message.
https://mcp.shipstatic.com
ChatGPT
Add the ShipStatic plugin from its page in ChatGPT. There is nothing to paste.
Claude Desktop and claude.ai
Settings → Connectors → Add custom connector, paste https://mcp.shipstatic.com, save.
Claude Code
claude mcp add --transport http shipstatic https://mcp.shipstatic.com
Cursor, Antigravity, Devin Desktop, n8n, Zed, and anywhere with mcp.json
{
"mcpServers": {
"shipstatic": {
"url": "https://mcp.shipstatic.com"
}
}
}
VS Code
Install ShipStatic for VS Code. The server is built in, with no config at all.
Then just ask
"Publish this with ShipStatic."
Your agent publishes it, and you get back a link you can share right away, and a claim link. The site stays up for 3 days, and opening the claim link keeps it for good.
Want the site private? Say "publish this with ShipStatic's built-in password protection". Visitors have to type the password before they see anything, and saying "built-in" keeps your agent from writing a password page of its own.
Keep your sites with a free account
Everything above works with no account. A free account keeps your sites for good, gives you a ShipStatic domain like yourname.shipstatic.com, and shows you everything you've published in one place. A custom domain like www.example.com needs a paid plan.
Connect one when your client offers to sign you in, and the same URL answers with the rest. There's nothing to install and no key to paste: your client starts the sign-in itself.
Tools
All fifteen tools are on both doors. What changes is not which tools exist, but which ones answer: deployments_upload is the one that needs no account, and the other fourteen answer once you have connected one (hosted) or set SHIP_TOKEN (local).
Publishing, with no account
| Tool | Description |
|---|---|
deployments_upload |
Publish files and get a live URL instantly, optionally protected by a password |
Deployments, with an account
| Tool | Description |
|---|---|
deployments_list |
List all deployments with their URLs, status, labels, and password protection state. Pages with limit and cursor |
deployments_get |
Get deployment details including URL, status, file count, size, labels, and password protection state |
deployments_set |
Update the labels on a deployment for organization and filtering |
deployments_delete |
Permanently delete a deployment and all its files |
Domains, with an account
| Tool | Description |
|---|---|
domains_set |
Connect a custom domain to your site, switch deployments, or update labels |
domains_list |
List all domains with their linked deployment and verification status. Pages with limit and cursor |
domains_get |
Get domain details including linked deployment, verification status, and labels |
domains_records |
Get the DNS records you need to configure at your DNS provider |
domains_dns |
The DNS provider recorded for a domain, if known (e.g. Cloudflare, Namecheap) |
domains_share |
Get a shareable link so someone else can see the required DNS records |
domains_validate |
Check if a domain name is valid and available before connecting it |
domains_verify |
Check if DNS is configured correctly after you set up the records |
domains_delete |
Permanently disconnect and delete a custom domain |
Account, with an account
| Tool | Description |
|---|---|
whoami |
Your email and name, and the account's plan, usage and caps |
Paging long lists
deployments_list and domains_list accept limit and cursor. Each response carries a cursor: pass it back to fetch the next page. A null cursor means you're on the last one.
Retrying a deploy safely
deployments_upload accepts an idempotencyKey. If a deploy times out you cannot tell "it never landed" from "it landed and the response was lost", and retrying without a key creates a second site. Send the same key on the retry and you get back the site the first try made, once it went live. A key works only within your account: an anonymous deploy ignores it, and a retry makes a new site.
Key the attempt, not the try: a run id, a commit sha, or a uuid generated before the first call. A key that changes on every retry does nothing.
Deployments that clean themselves up
deployments_upload accepts a ttl in seconds. The deployment expires when the time is up and the platform removes it. That's useful for previews and quick experiments you'd otherwise have to remember to delete.
{ "path": "/path/to/dist", "ttl": 3600 }
It needs an account (a connected account on the hosted endpoint, or SHIP_TOKEN locally): a deploy with no account already expires on the platform's schedule, so a ttl on one is refused rather than ignored. A deployment carrying a ttl cannot be linked to any domain: deploy without one when the site needs a domain.
Run it on your own machine
This package runs the same fifteen tools, reached the other way: as a local process instead of the hosted URL. Use it when your MCP client doesn't speak OAuth yet, or when you'd rather set a key once than sign in. To publish a folder from your own machine, use the ShipStatic CLI instead: it reads the files straight from disk.
It needs Node.js 20.19 or newer, and takes one setting, SHIP_TOKEN, whose value is your API key from my.shipstatic.com/api-key. Without it, the local server works like the hosted URL with no account connected.
claude mcp add shipstatic -e SHIP_TOKEN=ship-your-api-key -- npx -y @shipstatic/mcp
Any other client takes the same command and setting in its mcp.json:
{
"mcpServers": {
"shipstatic": {
"command": "npx",
"args": ["-y", "@shipstatic/mcp"],
"env": { "SHIP_TOKEN": "ship-your-api-key" }
}
}
}
The MCP Registry lists ShipStatic as com.shipstatic/mcp, with the hosted URL.
Also available
| Surface | Reach it |
|---|---|
| CLI and SDK | npx @shipstatic/ship ./dist |
| VS Code | Search "ShipStatic" in the Marketplace |
| Plugin | Install it in Cursor, Claude Code, Codex or Gemini CLI |
| OpenCode | opencode plugin add opencode-shipstatic |
| n8n | Search "ShipStatic" in n8n's node panel |
| GitHub Action | shipstatic/action@v3 |
| Agent Skill | npx skills add shipstatic/plugin |
License
MIT
Preguntas sobre ShipStatic MCP
¿Cómo agrego ShipStatic MCP a Claude Code?
Ejecuta claude mcp add mcp -- npx -y @shipstatic/mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego ShipStatic 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.
¿Qué herramientas proporciona ShipStatic MCP?
Expone 15 herramientas, incluidas deployments_upload, deployments_list, deployments_get, deployments_set, deployments_delete.
¿Cuánto tiempo permanecen en línea los despliegues anónimos?
Los sitios publicados sin una cuenta permanecen activos durante 3 días, pero puedes mantenerlos para siempre abriendo el enlace de reclamación proporcionado.
¿Puedo proteger mi sitio publicado con una contraseña?
Sí, puedes solicitar la protección por contraseña a través de tu agente para asegurar que los visitantes deban introducir una contraseña antes de ver el sitio.
¿Cómo puedo usar dominios personalizados?
Los dominios personalizados requieren un plan de pago, mientras que las cuentas gratuitas reciben un dominio de ShipStatic.