@shipstatic/mcp 1.1.1-beta.4 → 1.2.0-beta.1

package/README.md

@@ -137,6 +137,16 @@ The hosted endpoint exposes `deployments_upload` only. The local install exposes
 
 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 reclaims it — handy for previews and throwaway iterations you would otherwise have to remember to delete.
+
+```json
+{ "path": "/path/to/dist", "ttl": 3600 }
+```
+
+It needs `SHIP_TOKEN`: a keyless deploy 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 a custom domain — deploy without one when the site needs a domain.
+
 ## Registry
 
 Published to the [MCP Registry](https://registry.modelcontextprotocol.io/v0.1/servers?search=com.shipstatic/mcp) as `com.shipstatic/mcp`. Registry-aware clients see both the hosted endpoint and the local install and pick the right transport for their environment.

package/dist/server.js

@@ -20,7 +20,7 @@ To deploy: call ${UPLOAD_TOOL_NAME} with the build output directory path. ${B.li
 
 Without SHIP_TOKEN, deployments are public and expire in ${PUBLIC_EXPIRY}. ${B.claim}
 
-With SHIP_TOKEN configured, deployments go to the user's account and never expire. Listing, managing, and domain operations also require SHIP_TOKEN.
+With SHIP_TOKEN configured, deployments go to the user's account and never expire — pass \`ttl\` (seconds) to ${UPLOAD_TOOL_NAME} for one that expires on its own. Listing, managing, and domain operations also require SHIP_TOKEN.
 
 ${B.conceptsHeader}
 ${B.deploymentConcept}
@@ -50,8 +50,15 @@ export function createServer(ship, options) {
             labels: z.array(z.string()).optional().describe(PARAM_DESCRIPTIONS.labels),
             password: z.string().optional().describe(PARAM_DESCRIPTIONS.password),
             idempotencyKey: z.string().optional().describe(PARAM_DESCRIPTIONS.idempotencyKey),
+            // A bare `z.number()`, and the absences are the point. `.min()`/`.max()`
+            // would restate `TTL_CONSTRAINTS`, and `.int()` would restate the
+            // fraction rule — all three owned by `validateTtl`, which the SDK runs
+            // in-process before a byte is uploaded and which answers in the
+            // constitution's own words. A second validator here could only ever
+            // disagree with the first, silently; its absence fails loudly instead.
+            ttl: z.number().optional().describe(PARAM_DESCRIPTIONS.ttl),
         },
-    }, ({ path, labels, password, idempotencyKey }) => call(() => ship.deployments.upload(path, { labels, password, idempotencyKey, via })));
+    }, ({ path, labels, password, idempotencyKey, ttl }) => call(() => ship.deployments.upload(path, { labels, password, idempotencyKey, ttl, via })));
     // The other fourteen. Identical on every transport, so they live in the
     // shared package rather than here — see tools.ts for why upload is not
     // among them.

package/dist/vocabulary.d.ts

@@ -200,4 +200,20 @@ export declare const PARAM_DESCRIPTIONS: {
      * the same one on both. The window is derived, never typed out.
      */
     readonly idempotencyKey: `Makes this deploy replayable instead of repeatable. A deploy is not naturally idempotent: if a call times out you cannot tell "it never landed" from "it landed and the response was lost", and retrying creates a second deployment. Send the same key on the retry and the original deployment is replayed instead (within ${number} hours). Key the ATTEMPT \u2014 a run id, a commit sha, a uuid minted before the first try \u2014 never one minted fresh on each retry, which would defeat the point.`;
+    /**
+     * Shared one door ahead of its offer, for the same reason `idempotencyKey`
+     * is: only stdio declares `ttl` today (`cloudflare/mcp/CLAUDE.md`'s
+     * divergence table records the hosted deferral and its trigger), and the two
+     * refusals this teaches belong to the platform, so they read identically on
+     * every door.
+     *
+     * **Two things are deliberately absent, and both are the same rule.** The
+     * RANGE, because `@shipstatic/ship` validates it in-process before a byte is
+     * uploaded and relays the constitution's own sentence — a second copy here
+     * could only ever disagree with it. And the name of any credential: stdio
+     * owns `SHIP_TOKEN`, the hosted door owns "connect an account", and a SHARED
+     * string that named either would put one door's fact in the other's mouth.
+     * `tests/vocabulary.test.ts` fences the second half for every member.
+     */
+    readonly ttl: "Seconds until this deployment expires and the platform reclaims it; omit for one that never does. Only for authenticated deploys — an anonymous deployment already expires on the platform's schedule, and a requested ttl on one is refused. A deployment carrying a ttl cannot be linked to a custom domain: deploy without one if the site needs a domain.";
 };

package/dist/vocabulary.js

@@ -184,4 +184,20 @@ export const PARAM_DESCRIPTIONS = {
      * the same one on both. The window is derived, never typed out.
      */
     idempotencyKey: `Makes this deploy replayable instead of repeatable. A deploy is not naturally idempotent: if a call times out you cannot tell "it never landed" from "it landed and the response was lost", and retrying creates a second deployment. Send the same key on the retry and the original deployment is replayed instead (within ${IDEMPOTENCY_KEY_CONSTRAINTS.WINDOW_SECONDS / 3600} hours). Key the ATTEMPT — a run id, a commit sha, a uuid minted before the first try — never one minted fresh on each retry, which would defeat the point.`,
+    /**
+     * Shared one door ahead of its offer, for the same reason `idempotencyKey`
+     * is: only stdio declares `ttl` today (`cloudflare/mcp/CLAUDE.md`'s
+     * divergence table records the hosted deferral and its trigger), and the two
+     * refusals this teaches belong to the platform, so they read identically on
+     * every door.
+     *
+     * **Two things are deliberately absent, and both are the same rule.** The
+     * RANGE, because `@shipstatic/ship` validates it in-process before a byte is
+     * uploaded and relays the constitution's own sentence — a second copy here
+     * could only ever disagree with it. And the name of any credential: stdio
+     * owns `SHIP_TOKEN`, the hosted door owns "connect an account", and a SHARED
+     * string that named either would put one door's fact in the other's mouth.
+     * `tests/vocabulary.test.ts` fences the second half for every member.
+     */
+    ttl: "Seconds until this deployment expires and the platform reclaims it; omit for one that never does. Only for authenticated deploys — an anonymous deployment already expires on the platform's schedule, and a requested ttl on one is refused. A deployment carrying a ttl cannot be linked to a custom domain: deploy without one if the site needs a domain.",
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@shipstatic/mcp",
-  "version": "1.1.1-beta.4",
+  "version": "1.2.0-beta.1",
   "mcpName": "com.shipstatic/mcp",
   "description": "ShipStatic MCP — deploy static websites from AI agents. Full toolset incl. custom domains. Free hosted endpoint at mcp.shipstatic.com — no install.",
   "type": "module",
@@ -61,14 +61,14 @@
     "url": "https://github.com/shipstatic/mcp/issues"
   },
   "engines": {
-    "node": ">=20.0.0"
+    "node": ">=20.19.0"
   },
   "author": "ShipStatic",
   "license": "MIT",
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.30.0",
-    "@shipstatic/ship": "2.2.0-beta.8",
-    "@shipstatic/types": "2.7.0-beta.4",
+    "@shipstatic/ship": "2.2.0",
+    "@shipstatic/types": "2.7.0",
     "zod": "^4.4.3"
   },
   "devDependencies": {