@shipstatic/mcp 2.4.1-beta.3 → 2.4.2-beta.1

package/dist/tools.d.ts

@@ -31,7 +31,7 @@
  * Claude connectors directory refuses submission for a tool that lacks one, so
  * a titleless tool is not a shabby tool — it is an unlistable product. The
  * style is short Title Case verb phrases naming what the USER gets ("List
- * Deployments", "Connect Custom Domain"); the name obeys `resource_action` for
+ * Deployments", "Set Domain"); the name obeys `resource_action` for
  * the agent, the title reads as English for the human, and the description
  * carries every precision neither can. Both catalogue pins assert a title on
  * every tool, so the next one cannot be added without one.

package/dist/tools.js

@@ -31,7 +31,7 @@
  * Claude connectors directory refuses submission for a tool that lacks one, so
  * a titleless tool is not a shabby tool — it is an unlistable product. The
  * style is short Title Case verb phrases naming what the USER gets ("List
- * Deployments", "Connect Custom Domain"); the name obeys `resource_action` for
+ * Deployments", "Set Domain"); the name obeys `resource_action` for
  * the agent, the title reads as English for the human, and the description
  * carries every precision neither can. Both catalogue pins assert a title on
  * every tool, so the next one cannot be added without one.
@@ -191,12 +191,14 @@ export function registerAccountTools(server, ship, call) {
     }), ({ deployment }) => call(() => ship.deployments.delete(deployment)));
     // Domains
     server.registerTool('domains_set', titled({
-        title: 'Connect Custom Domain',
-        description: 'Create or update a custom domain. Can reserve a name (omit deployment), link it to a deployment, switch deployments, or update labels. domains_records then returns the DNS records to configure.',
+        title: 'Set Domain',
+        description: '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.',
         annotations: annotate(TOOLS.domains_set),
         outputSchema: DomainSetResultSchema,
         inputSchema: {
-            domain: z.string().describe('Domain name (e.g. "www.example.com" or "blog.example.com")'),
+            domain: z
+                .string()
+                .describe('Domain name: a ShipStatic domain (e.g. "yourname.shipstatic.com") or a custom domain (e.g. "www.example.com")'),
             deployment: z
                 .string()
                 .optional()
@@ -266,7 +268,7 @@ export function registerAccountTools(server, ship, call) {
         inputSchema: {
             domain: z
                 .string()
-                .describe('Domain name to check (e.g. "www.example.com"). Call before domains_set to check availability.'),
+                .describe('Domain name to check (e.g. "yourname.shipstatic.com" or "www.example.com"). Call before domains_set to check availability.'),
         },
     }), ({ domain }) => call(() => ship.domains.validate(domain)));
     server.registerTool('domains_verify', titled({

package/dist/vocabulary.d.ts

@@ -213,8 +213,8 @@ export declare const INSTRUCTION_BLOCKS: {
     readonly claim: "The response includes a claim URL — always show the deployment URL and the claim URL to the user so they can keep the site permanently.";
     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. 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.";
+    readonly domainConcept: "- Domain: a name pointing to a deployment. Optional. A ShipStatic domain (e.g. yourname.shipstatic.com) needs no setup; a custom domain (e.g. www.example.com) needs DNS records. Subdomains only, not apex domains.";
+    readonly domainWorkflow: "To give a deployment a ShipStatic domain: domains_validate → domains_set with the domain and the deployment. It is live at once, with no DNS. To add a custom domain: domains_validate → domains_set → domains_records (show DNS records to user) → user configures DNS → domains_verify, only while its `status` is `unverified` → 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

@@ -192,8 +192,8 @@ export const INSTRUCTION_BLOCKS = {
     claim: 'The response includes a claim URL — always show the deployment URL and the claim URL to the user so they can keep the site permanently.',
     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. 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.',
+    domainConcept: '- Domain: a name pointing to a deployment. Optional. A ShipStatic domain (e.g. yourname.shipstatic.com) needs no setup; a custom domain (e.g. www.example.com) needs DNS records. Subdomains only, not apex domains.',
+    domainWorkflow: 'To give a deployment a ShipStatic domain: domains_validate → domains_set with the domain and the deployment. It is live at once, with no DNS. To add a custom domain: domains_validate → domains_set → domains_records (show DNS records to user) → user configures DNS → domains_verify, only while its `status` is `unverified` → 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": "2.4.1-beta.3",
+  "version": "2.4.2-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",