Deploye statische Websites, Landingpages und Prototypen sofort über einen AI Agent.
Auch bekannt als shipstatic/mcp, mcp, @shipstatic/mcp
- Stars
- 6
- Tools
- 15
- Downloads, 30 Tage
- —
- Neueste Version
- 2.8.3
- Letzter Commit
- 12. Nov. 2026
- Lizenz
- MIT
Was ist ShipStatic MCP?
ShipStatic ist ein MCP server. Deploye statische Websites, Landingpages und Prototypen sofort über einen AI Agent. Er stellt 15 Tools bereit, etwa deployments_upload, deployments_list, deployments_get.
Zusammenfassung generiert aus dem README des Projekts
Über ShipStatic MCP server
ShipStatic ermöglicht es Entwicklern, statische Websites, Landingpages und Prototypen über einen AI Agent zu deployen. Es funktioniert entweder als Remote-Service über eine gehostete URL oder als lokaler Prozess unter Verwendung eines SHIP_TOKEN. Nutzer können es mit verschiedenen Clients wie Claude Desktop, Cursor, Claude Code und VS Code verbinden. Der Server stellt fünfzehn Tools bereit, um den gesamten Deployment-Lifecycle zu verwalten.
Für Nutzer ohne Account ermöglicht das deployments_upload Tool das sofortige Veröffentlichen von Dateien unter einer Live-URL. Diese anonymen Seiten bleiben drei Tage lang aktiv, sofern kein Claim-Link genutzt wird. Registrierte Nutzer erhalten Zugriff auf erweiterte Funktionen wie die Verwaltung eigener Domains, das Auflisten aller Deployments und das Festlegen spezifischer Time-to-Live-Dauern für die automatische Bereinigung. Das System unterstützt zudem den Passwortschutz, um bestimmte Deployments vor Besuchern privat zu halten.
Was du damit machen kannst
- 1Sofortiges Prototype-DeploymentSag deinem AI Agent einfach, er soll deine aktuellen Dateien nehmen und sie sofort online stellen.
- 2Sichere private PreviewsFordere deinen Agenten auf, eine Seite mit integriertem Passwortschutz für Besucher zu veröffentlichen.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du ShipStatic MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenShipStatic MCP in Claude Code installieren
$ claude mcp add mcp -- npx -y @shipstatic/mcpShipStatic MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@shipstatic/mcp"
]
}
}
}ShipStatic MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@shipstatic/mcp"
]
}
}
}ShipStatic MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@shipstatic/mcp"]}'ShipStatic MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@shipstatic/mcp"
]
}
}
}ShipStatic MCP in Codex installieren
$ codex mcp add mcp -- npx -y @shipstatic/mcpShipStatic MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@shipstatic/mcp"]
ShipStatic MCP in Gemini CLI installieren
$ gemini mcp add -s user mcp npx -- -y @shipstatic/mcpShipStatic MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@shipstatic/mcp"
]
}
}
}ShipStatic MCP tools 15
Erkannt aus dem READMEdeployments_uploaddeployments_listdeployments_getdeployments_setdeployments_deletedomains_setdomains_listdomains_getdomains_recordsdomains_dnsdomains_sharedomains_validate
| deployments_upload | — | |
| deployments_list | — | |
| deployments_get | — | |
| deployments_set | — | |
| deployments_delete | — | |
| domains_set | — | |
| domains_list | — | |
| domains_get | — | |
| domains_records | — | |
| domains_dns | — | |
| domains_share | — | |
| domains_validate | — |
Alle 15 Tools anzeigenWeniger Tools anzeigen
domains_verifydomains_deletewhoami
| domains_verify | — | |
| domains_delete | — | |
| whoami | — |
Konfiguration
SHIP_TOKEN
| Name | Beschreibung | Typ |
|---|---|---|
| SHIP_TOKEN | — |
Automatisierte Checks
Geluften am 12. 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 erreichbarBestanden
- Open Source Lizenz (OSI)Bestanden
- Commit oder Release im letzten JahrBestanden
- Package-Name ähnelt keinem populären PackageBestanden
- Remote Endpoint nutzt HTTPSBestanden
- Destruktive Tools sind markiertBestanden
- Keine versteckten Anweisungen an das ModellBestanden
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenNicht geprüft
README
Auf GitHub ansehenShipStatic 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
ShipStatic MCP Fragen
Wie füge ich ShipStatic MCP zu Claude Code hinzu?
Führe claude mcp add mcp -- npx -y @shipstatic/mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich ShipStatic MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Welche Tools bietet ShipStatic MCP?
Er stellt 15 Tools bereit, darunter deployments_upload, deployments_list, deployments_get, deployments_set, deployments_delete.
Wie lange bleiben anonyme Deployments online?
Seiten, die ohne Account veröffentlicht werden, bleiben für 3 Tage online. Du kannst sie jedoch dauerhaft behalten, indem du den bereitgestellten Claim-Link nutzt.
Kann ich meine veröffentlichte Seite mit einem Passwort schützen?
Ja, du kannst über deinen Agenten einen Passwortschutz anfordern, damit Besucher erst ein Passwort eingeben müssen, bevor sie die Seite sehen können.
Wie kann ich eigene Domains nutzen?
Eigene Domains erfordern einen kostenpflichtigen Plan, während Free-Accounts eine ShipStatic-Domain erhalten.