@shipstatic/mcp 1.12.4 → 2.0.0-beta.1

package/dist/tools.js

@@ -209,14 +209,14 @@ export function registerAccountTools(server, ship, call) {
     }), ({ domain, deployment, labels }) => call(() => ship.domains.set(domain, { deployment, labels })));
     server.registerTool('domains_list', titled({
         title: 'List Domains',
-        description: `List all domains with their URLs, linked deployment, and verification status.${PAGING_NOTE}`,
+        description: `List all domains with their URLs, linked deployment, and \`status\`.${PAGING_NOTE}`,
         annotations: annotate(TOOLS.domains_list),
         outputSchema: DomainListResponseSchema,
         inputSchema: PAGINATION_INPUT,
     }), ({ limit, cursor }) => call(() => ship.domains.list({ limit, cursor })));
     server.registerTool('domains_get', titled({
         title: 'Get Domain',
-        description: 'Get domain details including URL, linked deployment, verification status, and labels.',
+        description: '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`).',
         annotations: annotate(TOOLS.domains_get),
         outputSchema: DomainSchema,
         inputSchema: {
@@ -271,7 +271,7 @@ export function registerAccountTools(server, ship, call) {
     }), ({ domain }) => call(() => ship.domains.validate(domain)));
     server.registerTool('domains_verify', titled({
         title: 'Verify Domain DNS',
-        description: 'Trigger DNS verification for a custom domain. Call after the user has configured DNS records from domains_records. Verification is asynchronous — the domain status updates once DNS propagates. A verified domain serves nothing until a deployment is linked with domains_set.',
+        description: 'Trigger DNS verification for a custom domain. Call after the user has configured DNS records from domains_records. 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.',
         annotations: annotate(TOOLS.domains_verify),
         outputSchema: DomainVerifyResponseSchema,
         inputSchema: {

package/dist/vocabulary.d.ts

@@ -204,7 +204,7 @@ export declare const INSTRUCTION_BLOCKS: {
     readonly conceptsHeader: "Concepts:";
     readonly deploymentConcept: "- Deployment: an immutable set of files with an instant URL (e.g. happy-cat-abc1234.shipstatic.com). No setup needed.";
     readonly domainConcept: "- Domain: a custom domain (e.g. www.example.com) pointing to a deployment. Optional. Subdomains only — not apex domains.";
-    readonly domainWorkflow: "To add a custom domain: domains_validate → domains_set → domains_records (show DNS records to user) → user configures DNS → domains_verify → domains_set with the deployment to serve. A domain serves nothing until a deployment is linked, so ask the user which one and link it; domains_get shows whether one is.";
+    readonly domainWorkflow: "To add a custom domain: domains_validate → domains_set → domains_records (show DNS records to user) → user configures DNS → domains_verify → domains_set with the deployment to serve. A domain serves nothing until a deployment is linked, so ask the user which one and link it. Read `status` to know where a domain stands: `unverified` means its DNS records are not configured yet, `unlinked` means DNS is right and nothing is published there, `live` means it serves, `paused` means the plan has no room for it.";
 };
 /**
  * The fragments of the upload tool's description that both transports say.

package/dist/vocabulary.js

@@ -183,7 +183,7 @@ export const INSTRUCTION_BLOCKS = {
     conceptsHeader: 'Concepts:',
     deploymentConcept: '- Deployment: an immutable set of files with an instant URL (e.g. happy-cat-abc1234.shipstatic.com). No setup needed.',
     domainConcept: '- Domain: a custom domain (e.g. www.example.com) pointing to a deployment. Optional. Subdomains only — not apex domains.',
-    domainWorkflow: 'To add a custom domain: domains_validate → domains_set → domains_records (show DNS records to user) → user configures DNS → domains_verify → domains_set with the deployment to serve. A domain serves nothing until a deployment is linked, so ask the user which one and link it; domains_get shows whether one is.',
+    domainWorkflow: 'To add a custom domain: domains_validate → domains_set → domains_records (show DNS records to user) → user configures DNS → domains_verify → domains_set with the deployment to serve. A domain serves nothing until a deployment is linked, so ask the user which one and link it. Read `status` to know where a domain stands: `unverified` means its DNS records are not configured yet, `unlinked` means DNS is right and nothing is published there, `live` means it serves, `paused` means the plan has no room for it.',
 };
 /**
  * The fragments of the upload tool's description that both transports say.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@shipstatic/mcp",
-  "version": "1.12.4",
+  "version": "2.0.0-beta.1",
   "mcpName": "com.shipstatic/mcp",
   "description": "Deploy static websites, landing pages, and prototypes instantly from AI agents. Start with the hosted endpoint at mcp.shipstatic.com (no install, no signup, no API key), or install this package to deploy folders from your own machine. The same fifteen tools either way.",
   "type": "module",
@@ -68,8 +68,8 @@
   "license": "MIT",
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.30.0",
-    "@shipstatic/ship": "2.9.6",
-    "@shipstatic/types": "2.27.0",
+    "@shipstatic/ship": "3.0.0-beta.1",
+    "@shipstatic/types": "3.0.0-beta.1",
     "zod": "^4.4.3"
   },
   "devDependencies": {