@shipstatic/mcp 1.0.0-beta.10 → 1.0.0-beta.12

package/dist/index.d.ts

@@ -20,7 +20,9 @@
  * Every name below answers a question a consumer must otherwise answer for
  * itself, and each admission was a restatement deleted, not a convenience
  * added: `SERVER_NAME` and `UPLOAD_TOOL_NAME` were literals in two repos (the
- * first also correlates the Apps-SDK widget to the connector), `PUBLIC_EXPIRY`
+ * first also correlates the Apps-SDK widget to the connector; the third,
+ * `UPLOAD_TOOL_TITLE`, is the same shape — one operation, one English name for
+ * it, authored per transport only because upload itself is), `PUBLIC_EXPIRY`
  * was the same duration written out eight times, `DESCRIPTION_BLOCKS` the
  * fragments two tool descriptions genuinely share, `ACCOUNT_TOOL_NAMES` is
  * what lets the hosted catalogue fence name the fourteen without counting them
@@ -61,4 +63,4 @@
 export { 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, } from './vocabulary.js';
+export { ANNOTATIONS, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';

package/dist/index.js

@@ -20,7 +20,9 @@
  * Every name below answers a question a consumer must otherwise answer for
  * itself, and each admission was a restatement deleted, not a convenience
  * added: `SERVER_NAME` and `UPLOAD_TOOL_NAME` were literals in two repos (the
- * first also correlates the Apps-SDK widget to the connector), `PUBLIC_EXPIRY`
+ * first also correlates the Apps-SDK widget to the connector; the third,
+ * `UPLOAD_TOOL_TITLE`, is the same shape — one operation, one English name for
+ * it, authored per transport only because upload itself is), `PUBLIC_EXPIRY`
  * was the same duration written out eight times, `DESCRIPTION_BLOCKS` the
  * fragments two tool descriptions genuinely share, `ACCOUNT_TOOL_NAMES` is
  * what lets the hosted catalogue fence name the fourteen without counting them
@@ -61,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, } from './vocabulary.js';
+export { ANNOTATIONS, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';

package/dist/server.js

@@ -3,7 +3,7 @@ import { DeploymentVia } 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, } from './vocabulary.js';
+import { ANNOTATIONS, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, 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.
@@ -40,6 +40,7 @@ export function createServer(ship, options) {
     });
     // Deployments
     server.registerTool(UPLOAD_TOOL_NAME, {
+        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,
         inputSchema: {

package/dist/tools.d.ts

@@ -26,6 +26,15 @@
  * on *this* transport (the hint is `createCall`'s one per-transport argument).
  * A tool list that changes shape under the caller would be a second, dynamic
  * contract for an agent to track, and MCP clients cache the catalogue.
+ *
+ * **Every tool carries a `title`, and it is a gate rather than a nicety.** The
+ * 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
+ * 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.
  */
 import type { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import type Ship from '@shipstatic/ship';

package/dist/tools.js

@@ -26,6 +26,15 @@
  * on *this* transport (the hint is `createCall`'s one per-transport argument).
  * A tool list that changes shape under the caller would be a second, dynamic
  * contract for an agent to track, and MCP clients cache the catalogue.
+ *
+ * **Every tool carries a `title`, and it is a gate rather than a nicety.** The
+ * 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
+ * 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.
  */
 import { z } from 'zod';
 import { ANNOTATIONS } from './vocabulary.js';
@@ -95,11 +104,13 @@ const DEPLOYMENT_EXAMPLE = 'happy-cat-abc1234.shipstatic.com';
 export function registerAccountTools(server, ship, call) {
     // Deployments
     server.registerTool('deployments_list', {
+        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', {
+        title: 'Get Deployment',
         description: 'Get deployment details including URL, status, file count, size, labels, and password protection state.',
         annotations: READ,
         inputSchema: {
@@ -109,6 +120,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ deployment }) => call(() => ship.deployments.get(deployment)));
     server.registerTool('deployments_set', {
+        title: 'Update Deployment Labels',
         description: 'Update deployment labels. Replaces all existing labels.',
         annotations: WRITE,
         inputSchema: {
@@ -121,6 +133,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ deployment, labels }) => call(() => ship.deployments.set(deployment, { labels })));
     server.registerTool('deployments_delete', {
+        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,
         inputSchema: {
@@ -131,6 +144,7 @@ export function registerAccountTools(server, ship, call) {
     }, ({ deployment }) => call(() => ship.deployments.delete(deployment)));
     // Domains
     server.registerTool('domains_set', {
+        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,
         inputSchema: {
@@ -146,11 +160,13 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ domain, deployment, labels }) => call(() => ship.domains.set(domain, { deployment, labels })));
     server.registerTool('domains_list', {
+        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', {
+        title: 'Get Domain',
         description: 'Get domain details including URL, linked deployment, verification status, and labels.',
         annotations: READ,
         inputSchema: {
@@ -160,6 +176,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ domain }) => call(() => ship.domains.get(domain)));
     server.registerTool('domains_records', {
+        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,
         inputSchema: {
@@ -169,6 +186,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ domain }) => call(() => ship.domains.records(domain)));
     server.registerTool('domains_dns', {
+        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,
         inputSchema: {
@@ -178,6 +196,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ domain }) => call(() => ship.domains.dns(domain)));
     server.registerTool('domains_share', {
+        title: 'Share DNS Setup',
         description: 'Get a shareable DNS setup hash for a domain. The hash can be shared with the user so they can view the required DNS records without needing an API key.',
         annotations: READ,
         inputSchema: {
@@ -187,6 +206,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ domain }) => call(() => ship.domains.share(domain)));
     server.registerTool('domains_validate', {
+        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,
         inputSchema: {
@@ -196,6 +216,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ domain }) => call(() => ship.domains.validate(domain)));
     server.registerTool('domains_verify', {
+        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,
         inputSchema: {
@@ -205,6 +226,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ domain }) => call(() => ship.domains.verify(domain)));
     server.registerTool('domains_delete', {
+        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: {
@@ -213,6 +235,7 @@ export function registerAccountTools(server, ship, call) {
     }, ({ domain }) => call(() => ship.domains.delete(domain)));
     // Account
     server.registerTool('whoami', {
+        title: 'Show Account',
         description: 'Show authenticated account details including email, plan, and usage.',
         annotations: READ,
     }, () => call(() => ship.whoami()));

package/dist/vocabulary.d.ts

@@ -60,6 +60,26 @@ export declare const SERVER_NAME = "shipstatic";
  * `[UPLOAD_TOOL_NAME, ...ACCOUNT_TOOL_NAMES]` rather than counting to fifteen.
  */
 export declare const UPLOAD_TOOL_NAME = "deployments_upload";
+/**
+ * The upload tool's human-readable `title`, shared for the same reason the
+ * name is — and NOT for the reason the description is not.
+ *
+ * A title names the OPERATION, and the operation is identical on both doors:
+ * a user reading "Deploy Static Site" in a client's tool list learns nothing
+ * about how the bytes got there. The description is the opposite — hosted
+ * spends a paragraph telling an Apps-SDK caller not to base64-encode text, a
+ * hazard a filesystem path cannot have — which is why one is exported whole
+ * and the other only in fragments.
+ *
+ * The other fourteen titles live inline in `tools.ts`: one definition, both
+ * transports, nothing to keep in agreement. This one is authored per transport
+ * (upload is the tool each door writes for itself), so without an owner it
+ * would be two literals in two repos with nothing comparing them.
+ *
+ * Titles are not decoration here: the Claude connectors directory refuses
+ * submission for a tool that lacks one.
+ */
+export declare const UPLOAD_TOOL_TITLE = "Deploy Static Site";
 /**
  * How long an anonymous deployment lives, in the words an agent reads.
  *

package/dist/vocabulary.js

@@ -62,6 +62,26 @@ export const SERVER_NAME = 'shipstatic';
  * `[UPLOAD_TOOL_NAME, ...ACCOUNT_TOOL_NAMES]` rather than counting to fifteen.
  */
 export const UPLOAD_TOOL_NAME = 'deployments_upload';
+/**
+ * The upload tool's human-readable `title`, shared for the same reason the
+ * name is — and NOT for the reason the description is not.
+ *
+ * A title names the OPERATION, and the operation is identical on both doors:
+ * a user reading "Deploy Static Site" in a client's tool list learns nothing
+ * about how the bytes got there. The description is the opposite — hosted
+ * spends a paragraph telling an Apps-SDK caller not to base64-encode text, a
+ * hazard a filesystem path cannot have — which is why one is exported whole
+ * and the other only in fragments.
+ *
+ * The other fourteen titles live inline in `tools.ts`: one definition, both
+ * transports, nothing to keep in agreement. This one is authored per transport
+ * (upload is the tool each door writes for itself), so without an owner it
+ * would be two literals in two repos with nothing comparing them.
+ *
+ * Titles are not decoration here: the Claude connectors directory refuses
+ * submission for a tool that lacks one.
+ */
+export const UPLOAD_TOOL_TITLE = 'Deploy Static Site';
 /**
  * How long an anonymous deployment lives, in the words an agent reads.
  *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@shipstatic/mcp",
-  "version": "1.0.0-beta.10",
+  "version": "1.0.0-beta.12",
   "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",
@@ -66,8 +66,8 @@
   "license": "MIT",
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.30.0",
-    "@shipstatic/ship": "2.0.0-beta.17",
-    "@shipstatic/types": "2.5.0-beta.21",
+    "@shipstatic/ship": "2.0.0-beta.18",
+    "@shipstatic/types": "2.5.0-beta.22",
     "zod": "^4.4.3"
   },
   "devDependencies": {