ship.page

Deploy a multi-file site

deploy_files

Destructive

Deploy a map of path -> content as a multi-file site (must include index.html to serve at the root). Anonymous: up to 100 files per request, 7-day expiry (30 days once signed in). Pro ($4/mo): up to 10,000 files, custom or no TTL, named drops.

Input Schema

Name	Required	Description
`ttl`	No	Lifetime in seconds (min 60). Anonymous: max 604800 (7 days), default 7 days. Signed-in free: max 2592000 (30 days), default 30 days. A longer ttl is capped at the max. Paid: any value, omit for no expiry.
`name`	No	Stable name for a redeployable drop (1-41 chars of [a-z0-9-]). Requires an active subscription; the URL stays the same across redeploys.
`agent`	No	Name of the AI agent or app publishing this drop, e.g. 'chatgpt', 'claude', 'cursor'. AI agents: always set this.
`email`	No	Contact email for an anonymous deploy: the one-time claim link is mailed to it, so the drop stays recoverable even if the claim_token from the response is lost. Pass it whenever the deploy is for a human. Ignored for authenticated deploys (those are owned already).
`files`	Yes	Map of relative paths (e.g. 'index.html', 'css/app.css') to either a string, or { encoding: 'base64', content } for binary files.
`password`	No	Shared password: 8-128 Unicode characters, at most 512 UTF-8 bytes. Requires active paid Pro/Team. Sent privately, never in the URL or response. Omit on a live named redeploy to preserve protection. Recreating an expired or purged name is a new drop: send the password again.

Output Schema

Name	Required	Description
`url`	Yes
`hint`	No	Present when the requested ttl was over the plan's maximum and was capped to it.
`name`	No
`plan`	Yes
`slug`	Yes	Drop slug; the site is live at https://<slug>.ship.place/
`files`	Yes
`replaced`	No	Present with named deploys; true when an existing drop was replaced
`claim_url`	No	Present on anonymous deploys: a browser link that saves the drop to whichever account opens it. It carries the claim token, so keep it private.
`next_step`	No	Present when an API or MCP deploy expires: when the page expires and how to keep it online, written to be passed on to the person the page was made for.
`expires_at`	Yes	ISO timestamp, or null when the drop never expires
`claim_email`	No	Present when email was accepted on an anonymous deploy; the claim link was mailed to this address.
`claim_token`	No	One-time claim token (spc_...), present only on anonymous deploys and shown once. Anyone holding it can attach the drop to an account via claim_drop.
`password_protected`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / name / description

Previous value: -"Stable name for a redeployable drop (1-41 chars of [a-z0-9-]). Requires an active subscription; Team accounts serve it on their vanity subdomain."New value: +"Stable name for a redeployable drop (1-41 chars of [a-z0-9-]). Requires an active subscription; the URL stays the same across redeploys."

Changed3 schema fields changedNov 4, 2026

changedInput schema / properties / ttl / description

Previous value: -"Lifetime in seconds (min 60). Anonymous: max 2592000 (30 days), default 30 days. Signed-in free: max 7776000 (90 days), default 90 days. Paid: any value, omit for no expiry."New value: +"Lifetime in seconds (min 60). Anonymous: max 604800 (7 days), default 7 days. Signed-in free: max 2592000 (30 days), default 30 days. A longer ttl is capped at the max. Paid: any value, omit for no expiry."

addedOutput schema / properties / hint

Added value: +{
+  "description": "Present when the requested ttl was over the plan's maximum and was capped to it.",
+  "type": "string"
+}

changedOutput schema / properties / next_step / description

Previous value: -"Present with claim_url: one sentence on keeping the page online, written to be passed on to the person the page was made for."New value: +"Present when an API or MCP deploy expires: when the page expires and how to keep it online, written to be passed on to the person the page was made for."

Changed3 schema fields changedOct 12, 2026

addedOutput schema / properties / claim_email

Added value: +{
+  "description": "Present when email was accepted on an anonymous deploy; the claim link was mailed to this address.",
+  "type": "string"
+}

addedOutput schema / properties / claim_url

Added value: +{
+  "description": "Present on anonymous deploys: a browser link that saves the drop to whichever account opens it. It carries the claim token, so keep it private.",
+  "type": "string"
+}

addedOutput schema / properties / next_step

Added value: +{
+  "description": "Present with claim_url: one sentence on keeping the page online, written to be passed on to the person the page was made for.",
+  "type": "string"
+}

Changed1 schema field changedSep 29, 2026

changedOutput schema / properties / slug / description

Previous value: -"Drop slug; the site is live at https://<slug>.shipped.run/"New value: +"Drop slug; the site is live at https://<slug>.ship.place/"

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / agent

Added value: +{
+  "description": "Name of the AI agent or app publishing this drop, e.g. 'chatgpt', 'claude', 'cursor'. AI agents: always set this.",
+  "maxLength": 64,
+  "type": "string"
+}

Changed1 schema field changedSep 18, 2026

changedOutput schema / properties / slug / description

Previous value: -"Drop slug; the site is live at https://<slug>.shipped.cloud/"New value: +"Drop slug; the site is live at https://<slug>.shipped.run/"

Changed1 schema field changedSep 16, 2026

changedOutput schema / properties / slug / description

Previous value: -"Drop slug; the site is live at https://<slug>.shipped.run/"New value: +"Drop slug; the site is live at https://<slug>.shipped.cloud/"

Changed1 schema field changedSep 16, 2026

changedOutput schema / properties / slug / description

Previous value: -"Drop slug; the site is live at https://<slug>.shipped.page/"New value: +"Drop slug; the site is live at https://<slug>.shipped.run/"

Changed1 schema field changedSep 10, 2026

changedOutput schema / properties / slug / description

Previous value: -"Drop slug; the site is live at https://<slug>.shipped.run/"New value: +"Drop slug; the site is live at https://<slug>.shipped.page/"

Changed3 schema fields changedSep 9, 2026

addedInput schema / properties / password

Added value: +{
+  "description": "Shared password: 8-128 Unicode characters, at most 512 UTF-8 bytes. Requires active paid Pro/Team. Sent privately, never in the URL or response. Omit on a live named redeploy to preserve protection. Recreating an expired or purged name is a new drop: send the password again.",
+  "maxLength": 128,
+  "minLength": 8,
+  "type": "string",
+  "writeOnly": true
+}

addedOutput schema / properties / password_protected
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "slug",
-  "url",
-  "files",
-  "plan",
-  "expires_at"
-]New value: +[
+  "slug",
+  "url",
+  "files",
+  "plan",
+  "expires_at",
+  "password_protected"
+]

Changed1 schema field changedSep 1, 2026

changedInput schema / properties / ttl / description

Previous value: -"Lifetime in seconds (min 60). Anonymous: max 604800 (7 days), default 7 days. Signed-in free: max 2592000 (30 days), default 30 days. Paid: any value, omit for no expiry."New value: +"Lifetime in seconds (min 60). Anonymous: max 2592000 (30 days), default 30 days. Signed-in free: max 7776000 (90 days), default 90 days. Paid: any value, omit for no expiry."

Changed1 schema field changedAug 31, 2026

changedOutput schema / properties / slug / description

Previous value: -"Drop slug; the site is live at https://<slug>.shipped.page/"New value: +"Drop slug; the site is live at https://<slug>.shipped.run/"

Changed1 schema field changedAug 27, 2026

addedInput schema / properties / email

Added value: +{
+  "description": "Contact email for an anonymous deploy: the one-time claim link is mailed to it, so the drop stays recoverable even if the claim_token from the response is lost. Pass it whenever the deploy is for a human. Ignored for authenticated deploys (those are owned already).",
+  "type": "string"
+}

Changed1 schema field changedAug 21, 2026

changedInput schema / properties / ttl / description

Previous value: -"Lifetime in seconds (min 60). Free: max 604800 (7 days), default 7 days. Paid: any value, omit for no expiry."New value: +"Lifetime in seconds (min 60). Anonymous: max 604800 (7 days), default 7 days. Signed-in free: max 2592000 (30 days), default 30 days. Paid: any value, omit for no expiry."

Changed1 schema field changedAug 20, 2026

addedOutput schema / properties / claim_token

Added value: +{
+  "description": "One-time claim token (spc_...), present only on anonymous deploys and shown once. Anyone holding it can attach the drop to an account via claim_drop.",
+  "type": "string"
+}

First observedAug 18, 2026

TDQS

A3.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false. The description adds meaningful operational context beyond those annotations: anonymous file limits, 7-day expiry, 30-day signed-in retention, paid-tier max files and TTL behavior, and named drops. It does not fully explain overwrite or purge semantics for named redeploys, but it substantially improves transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a compact, front-loaded paragraph that leads with the core action and then layers on constraints and tier information. The parenthetical tier details are dense but relevant. There is little wasted text, though the sentence could be split for easier scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is complex, with six parameters, nested file objects, annotations, and an output schema. The description covers the essential payload requirement, tier limits, expiry behavior, and named drops, while the output schema handles return values. It leaves some sibling-routing and redeploy-overwrite details implicit, but is otherwise complete enough to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents ttl, name, agent, email, files, and password in detail. The description reinforces tier limits and the index.html requirement, which adds some framing beyond the schema. Because most parameter-level meaning is already in the schema, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: deploy a map of path -> content as a multi-file site. It also gives a key structural constraint that index.html must be included to serve at the root. It is clearly distinct from a generic deploy, though it does not explicitly contrast itself with sibling deploy_html or append_files.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through file-count and TTL tiers, and the index.html requirement tells the agent when a payload is valid. However, it does not explicitly say when to choose this over deploy_html for single-file HTML or append_files for incremental changes. Usage guidance is therefore present but inferred rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ship.page tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?