@shipstatic/mcp 1.7.0 → 1.8.0

package/README.md

@@ -64,7 +64,7 @@ Everything above works with no account at all. Connect one when your client offe
 
 Install this package when your agent needs to deploy **a folder on your own machine** — the hosted endpoint takes files inline, so it has no path to read from — when you'd rather configure a token once than sign in, or when your MCP client doesn't speak OAuth yet.
 
-The config asks for one thing: `SHIP_TOKEN`. **Its value is your API key** — one credential, two names. The console mints it as an *API key* (it starts with `ship-`), and the setting that carries it is called the *token*. Get yours free at [my.shipstatic.com/api-key](https://my.shipstatic.com/api-key), paste it where the snippets below show `ship-your-api-key`, and every site you publish lands in your account, never expires, and gets bigger limits.
+The config asks for one thing: `SHIP_TOKEN`. **Its value is your API key** — one credential, two names. The console mints it as an *API key* (it starts with `ship-`), and the setting that carries it is called the *token*. Get yours free at [my.shipstatic.com/api-key](https://my.shipstatic.com/api-key), paste it where the snippets below show `ship-your-api-key`, and every site you publish lands in your account and never expires, with a rate limit of your own instead of the shared anonymous pools.
 
 The key is optional: leave it out and the local server behaves exactly like the hosted endpoint with no account connected — public sites, claim links, live for 3 days.
 

package/dist/index.d.ts

@@ -63,4 +63,4 @@
 export { type AuthFailure, type CallFn, type CallOptions, createCall, type ErrorHints, } from './call.js';
 export { createServer } from './server.js';
 export { ACCOUNT_TOOL_NAMES, registerAccountTools } from './tools.js';
-export { ANNOTATIONS, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';
+export { ANNOTATIONS, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, titled, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';

package/dist/index.js

@@ -63,4 +63,4 @@
 export { createCall, } from './call.js';
 export { createServer } from './server.js';
 export { ACCOUNT_TOOL_NAMES, registerAccountTools } from './tools.js';
-export { ANNOTATIONS, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';
+export { ANNOTATIONS, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, titled, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';

package/dist/server.js

@@ -3,7 +3,7 @@ import { DeploymentVia, MY_API_KEY_URL } from '@shipstatic/types';
 import { z } from 'zod';
 import { call } from './call.js';
 import { registerAccountTools } from './tools.js';
-import { ANNOTATIONS, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';
+import { ANNOTATIONS, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, titled, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';
 // Destructured so the fifteen registrations below read as they always have.
 // The definitions live in `vocabulary.ts` because the hosted transport speaks
 // the same ones — that file records what is shared, what is not, and why.
@@ -39,7 +39,7 @@ export function createServer(ship, options) {
         instructions: INSTRUCTIONS,
     });
     // Deployments
-    server.registerTool(UPLOAD_TOOL_NAME, {
+    server.registerTool(UPLOAD_TOOL_NAME, titled({
         title: UPLOAD_TOOL_TITLE,
         description: `Deploy a static site instantly — ${D.free}. Returns the live URL, file count, and size. Without SHIP_TOKEN, the response includes a claim URL (site expires in ${PUBLIC_EXPIRY}) — always show both the deployment URL and claim URL to the user. ${D.password}`,
         annotations: CREATE,
@@ -58,7 +58,7 @@ export function createServer(ship, options) {
             // disagree with the first, silently; its absence fails loudly instead.
             ttl: z.number().optional().describe(PARAM_DESCRIPTIONS.ttl),
         },
-    }, ({ path, labels, password, idempotencyKey, ttl }) => call(() => ship.deployments.upload(path, { labels, password, idempotencyKey, ttl, 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/tools.js

@@ -37,7 +37,7 @@
  * every tool, so the next one cannot be added without one.
  */
 import { z } from 'zod';
-import { ANNOTATIONS } from './vocabulary.js';
+import { ANNOTATIONS, titled } from './vocabulary.js';
 const { READ, WRITE, DESTRUCTIVE } = ANNOTATIONS;
 /**
  * The fourteen, by name, in registration order.
@@ -103,13 +103,13 @@ const PAGING_NOTE = " The response's `cursor` is null on the last page; pass it
 const DEPLOYMENT_EXAMPLE = 'happy-cat-abc1234.shipstatic.com';
 export function registerAccountTools(server, ship, call) {
     // Deployments
-    server.registerTool('deployments_list', {
+    server.registerTool('deployments_list', titled({
         title: 'List Deployments',
         description: `List all deployments with their URLs, status, labels, and password protection state.${PAGING_NOTE}`,
         annotations: READ,
         inputSchema: PAGINATION_INPUT,
-    }, ({ limit, cursor }) => call(() => ship.deployments.list({ limit, cursor })));
-    server.registerTool('deployments_get', {
+    }), ({ limit, cursor }) => call(() => ship.deployments.list({ limit, cursor })));
+    server.registerTool('deployments_get', titled({
         title: 'Get Deployment',
         description: 'Get deployment details including URL, status, file count, size, labels, and password protection state.',
         annotations: READ,
@@ -118,8 +118,8 @@ export function registerAccountTools(server, ship, call) {
                 .string()
                 .describe(`Deployment hostname (e.g. "${DEPLOYMENT_EXAMPLE}"). Returned by deployments_upload or deployments_list.`),
         },
-    }, ({ deployment }) => call(() => ship.deployments.get(deployment)));
-    server.registerTool('deployments_set', {
+    }), ({ deployment }) => call(() => ship.deployments.get(deployment)));
+    server.registerTool('deployments_set', titled({
         title: 'Update Deployment Labels',
         description: 'Update deployment labels. Replaces all existing labels.',
         annotations: WRITE,
@@ -131,8 +131,8 @@ export function registerAccountTools(server, ship, call) {
                 .array(z.string())
                 .describe('Labels to set. Replaces all existing labels. Pass empty array to clear.'),
         },
-    }, ({ deployment, labels }) => call(() => ship.deployments.set(deployment, { labels })));
-    server.registerTool('deployments_delete', {
+    }), ({ deployment, labels }) => call(() => ship.deployments.set(deployment, { labels })));
+    server.registerTool('deployments_delete', titled({
         title: 'Delete Deployment',
         description: 'Permanently delete a deployment and its files. You MUST confirm with the user before calling this tool, referencing the deployment.',
         annotations: DESTRUCTIVE,
@@ -141,9 +141,9 @@ export function registerAccountTools(server, ship, call) {
                 .string()
                 .describe(`Deployment hostname to delete (e.g. "${DEPLOYMENT_EXAMPLE}")`),
         },
-    }, ({ deployment }) => call(() => ship.deployments.delete(deployment)));
+    }), ({ deployment }) => call(() => ship.deployments.delete(deployment)));
     // Domains
-    server.registerTool('domains_set', {
+    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. After creating, call domains_records and show the DNS records to the user.',
         annotations: WRITE,
@@ -158,14 +158,14 @@ export function registerAccountTools(server, ship, call) {
                 .optional()
                 .describe('Labels for organizing domains (e.g. ["production"]).'),
         },
-    }, ({ domain, deployment, labels }) => call(() => ship.domains.set(domain, { deployment, labels })));
-    server.registerTool('domains_list', {
+    }), ({ 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}`,
         annotations: READ,
         inputSchema: PAGINATION_INPUT,
-    }, ({ limit, cursor }) => call(() => ship.domains.list({ limit, cursor })));
-    server.registerTool('domains_get', {
+    }), ({ 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.',
         annotations: READ,
@@ -174,8 +174,8 @@ export function registerAccountTools(server, ship, call) {
                 .string()
                 .describe('Domain name (e.g. "www.example.com"). Use domains_list to find names.'),
         },
-    }, ({ domain }) => call(() => ship.domains.get(domain)));
-    server.registerTool('domains_records', {
+    }), ({ domain }) => call(() => ship.domains.get(domain)));
+    server.registerTool('domains_records', titled({
         title: 'Get DNS Records',
         description: 'Get the DNS records the user needs to configure at their DNS provider. Call after domains_set. You MUST show the returned records to the user.',
         annotations: READ,
@@ -184,8 +184,8 @@ export function registerAccountTools(server, ship, call) {
                 .string()
                 .describe('Domain name. Must be a domain previously created with domains_set.'),
         },
-    }, ({ domain }) => call(() => ship.domains.records(domain)));
-    server.registerTool('domains_dns', {
+    }), ({ domain }) => call(() => ship.domains.records(domain)));
+    server.registerTool('domains_dns', titled({
         title: 'Look Up DNS Provider',
         description: 'Look up the DNS provider for a domain (e.g. Cloudflare, Namecheap). Helps the user know where to configure their DNS records.',
         annotations: READ,
@@ -194,8 +194,8 @@ export function registerAccountTools(server, ship, call) {
                 .string()
                 .describe('Domain name to look up DNS provider for (e.g. "www.example.com")'),
         },
-    }, ({ domain }) => call(() => ship.domains.dns(domain)));
-    server.registerTool('domains_share', {
+    }), ({ domain }) => call(() => ship.domains.dns(domain)));
+    server.registerTool('domains_share', titled({
         title: 'Share DNS Setup',
         description: 'Get a shareable DNS setup link for a domain. Share the link with the user so they, or whoever manages their DNS, can view the required records without needing an API key.',
         annotations: READ,
@@ -204,8 +204,8 @@ export function registerAccountTools(server, ship, call) {
                 .string()
                 .describe('Domain name to generate a share link for. Must be a domain previously created with domains_set.'),
         },
-    }, ({ domain }) => call(() => ship.domains.share(domain)));
-    server.registerTool('domains_validate', {
+    }), ({ domain }) => call(() => ship.domains.share(domain)));
+    server.registerTool('domains_validate', titled({
         title: 'Check Domain Availability',
         description: 'Check if a domain name is valid and available before creating it. Returns the normalized form and availability.',
         annotations: READ,
@@ -214,8 +214,8 @@ export function registerAccountTools(server, ship, call) {
                 .string()
                 .describe('Domain name to check (e.g. "www.example.com"). Call before domains_set to check availability.'),
         },
-    }, ({ domain }) => call(() => ship.domains.validate(domain)));
-    server.registerTool('domains_verify', {
+    }), ({ 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.',
         annotations: WRITE,
@@ -224,19 +224,19 @@ export function registerAccountTools(server, ship, call) {
                 .string()
                 .describe('Domain name to verify DNS for. Must be a domain previously created with domains_set.'),
         },
-    }, ({ domain }) => call(() => ship.domains.verify(domain)));
-    server.registerTool('domains_delete', {
+    }), ({ domain }) => call(() => ship.domains.verify(domain)));
+    server.registerTool('domains_delete', titled({
         title: 'Delete Domain',
         description: 'Permanently delete a domain. You MUST confirm with the user before calling this tool, referencing the domain name.',
         annotations: DESTRUCTIVE,
         inputSchema: {
             domain: z.string().describe('Domain name to delete (e.g. "www.example.com")'),
         },
-    }, ({ domain }) => call(() => ship.domains.delete(domain)));
+    }), ({ domain }) => call(() => ship.domains.delete(domain)));
     // Account
-    server.registerTool('whoami', {
+    server.registerTool('whoami', titled({
         title: 'Show Account',
         description: 'Show authenticated account details including email, plan, and usage.',
         annotations: READ,
-    }, () => call(() => ship.whoami()));
+    }), () => call(() => ship.whoami()));
 }

package/dist/vocabulary.d.ts

@@ -141,6 +141,28 @@ export declare const ANNOTATIONS: {
         readonly idempotentHint: true;
     };
 };
+/**
+ * One title, two wire slots: project a tool config's top-level `title` into
+ * `annotations.title` at registration.
+ *
+ * The MCP spec carries a tool title in two places. The 2025-06-18 revision
+ * put it top-level on the Tool object (where every registration here states
+ * it), and `ToolAnnotations.title` is the older 2025-03-26 slot that some
+ * readers still key on. The Claude connectors portal is one of them, measured
+ * on submission day 2026-08-31: its Tools step rendered every top-level title
+ * as the heading and simultaneously flagged all fifteen tools with "Missing
+ * annotations: title". So both slots must be populated, and they must agree.
+ *
+ * The top-level `title` stays the single owner. This projection is the only
+ * writer of the annotations copy, applied at every registration on both
+ * transports, and the catalogue fences hold the two slots equal off a real
+ * `tools/list` so a registration that bypasses it goes red rather than
+ * shipping a bare slot back to the portal.
+ */
+export declare function titled<C extends {
+    title: string;
+    annotations?: object;
+}>(config: C): C;
 /**
  * INSTRUCTIONS sentences both transports say.
  *

package/dist/vocabulary.js

@@ -125,6 +125,27 @@ export const ANNOTATIONS = {
     WRITE: { readOnlyHint: false, destructiveHint: false, idempotentHint: true, ...OPEN_WORLD },
     DESTRUCTIVE: { readOnlyHint: false, destructiveHint: true, idempotentHint: true, ...OPEN_WORLD },
 };
+/**
+ * One title, two wire slots: project a tool config's top-level `title` into
+ * `annotations.title` at registration.
+ *
+ * The MCP spec carries a tool title in two places. The 2025-06-18 revision
+ * put it top-level on the Tool object (where every registration here states
+ * it), and `ToolAnnotations.title` is the older 2025-03-26 slot that some
+ * readers still key on. The Claude connectors portal is one of them, measured
+ * on submission day 2026-08-31: its Tools step rendered every top-level title
+ * as the heading and simultaneously flagged all fifteen tools with "Missing
+ * annotations: title". So both slots must be populated, and they must agree.
+ *
+ * The top-level `title` stays the single owner. This projection is the only
+ * writer of the annotations copy, applied at every registration on both
+ * transports, and the catalogue fences hold the two slots equal off a real
+ * `tools/list` so a registration that bypasses it goes red rather than
+ * shipping a bare slot back to the portal.
+ */
+export function titled(config) {
+    return { ...config, annotations: { ...config.annotations, title: config.title } };
+}
 /**
  * INSTRUCTIONS sentences both transports say.
  *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@shipstatic/mcp",
-  "version": "1.7.0",
+  "version": "1.8.0",
   "mcpName": "com.shipstatic/mcp",
   "description": "Deploy static websites from AI agents. Start with the hosted endpoint at mcp.shipstatic.com \u2014 no install, no signup, no API key \u2014 or install this package to deploy folders from your own machine. The same fifteen tools either way.",
   "type": "module",