@shipstatic/mcp 2.5.0 → 2.6.0-beta.1

package/dist/index.d.ts

@@ -28,8 +28,10 @@
  * what lets the hosted catalogue fence name the fourteen without counting them
  * again, `TOOLS` and `annotate` replaced four annotation classes plus a
  * hand-annotated upload on each transport plus a separate list for the auth
- * need (three owners for one tool's facts, 1.11.0), and `createServer`
- * deleted three regexes in another repo's build (see below).
+ * need (three owners for one tool's facts, 1.11.0), `SERVER_INFO` is the
+ * title, description, website and icon both transports report rather than
+ * each stating its own, and `createServer` deleted three regexes in another
+ * repo's build (see below).
  *
  * **`createServer` is exported; the configured `call` is not.** The extension
  * previously reached stdio's composition by REGEX-PATCHING this package's
@@ -65,4 +67,4 @@
 export { type AuthFailure, type CallFn, type CallOptions, createCall, type ErrorHints, } from './call.js';
 export { createServer } from './server.js';
 export { ACCOUNT_TOOL_NAMES, type AccountToolName, registerAccountTools, TOOLS, type ToolName, } from './tools.js';
-export { annotate, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, type ToolContract, titled, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';
+export { annotate, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_INFO, SERVER_NAME, type ToolContract, titled, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';

package/dist/index.js

@@ -28,8 +28,10 @@
  * what lets the hosted catalogue fence name the fourteen without counting them
  * again, `TOOLS` and `annotate` replaced four annotation classes plus a
  * hand-annotated upload on each transport plus a separate list for the auth
- * need (three owners for one tool's facts, 1.11.0), and `createServer`
- * deleted three regexes in another repo's build (see below).
+ * need (three owners for one tool's facts, 1.11.0), `SERVER_INFO` is the
+ * title, description, website and icon both transports report rather than
+ * each stating its own, and `createServer` deleted three regexes in another
+ * repo's build (see below).
  *
  * **`createServer` is exported; the configured `call` is not.** The extension
  * previously reached stdio's composition by REGEX-PATCHING this package's
@@ -65,4 +67,4 @@
 export { createCall, } from './call.js';
 export { createServer } from './server.js';
 export { ACCOUNT_TOOL_NAMES, registerAccountTools, TOOLS, } from './tools.js';
-export { annotate, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, titled, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';
+export { annotate, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_INFO, SERVER_NAME, titled, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';

package/dist/server.js

@@ -4,7 +4,7 @@ import { DeploymentCreateResponseSchema } from '@shipstatic/types/schemas';
 import { z } from 'zod';
 import { call } from './call.js';
 import { registerAccountTools, TOOLS } from './tools.js';
-import { annotate, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, titled, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';
+import { annotate, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_INFO, titled, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';
 const B = INSTRUCTION_BLOCKS;
 const D = DESCRIPTION_BLOCKS;
 // Composed from the shared blocks plus the two sentences that are genuinely
@@ -30,7 +30,7 @@ ${B.domainWorkflow}`;
 export function createServer(ship, options) {
     const { version, via = DeploymentVia.MCP } = options;
     const server = new McpServer({
-        name: SERVER_NAME,
+        ...SERVER_INFO,
         version,
     }, {
         instructions: INSTRUCTIONS,

package/dist/vocabulary.d.ts

@@ -27,6 +27,7 @@
  * Everything else should be here, and adding a shared fact anywhere else is
  * how the next year's drift starts.
  */
+import type { Implementation } from '@modelcontextprotocol/sdk/types.js';
 /**
  * Two packages, and the split is a rule rather than an accident: **read a
  * constant from whatever will act on it.**
@@ -53,6 +54,27 @@
  * is exactly the shape this package exists to delete.
  */
 export declare const SERVER_NAME = "shipstatic";
+/**
+ * Who the server is, as every transport reports it in `serverInfo`: the
+ * fields a client shows a person when they connect. Everything but the
+ * version, which each transport reads from its own manifest.
+ *
+ * - **`title`** is the product's name as people read it (CANON §1).
+ * - **`description`** is this package's root sentence (CANON §2) with no
+ *   qualifier. The hosted server reports it on every door, and on an
+ *   auth-first door "no account needed" is false.
+ * - **`websiteUrl`** and the **icons** name the product, so they are
+ *   production values in every environment, as in any published package.
+ * - **The icons** are the brand mark the marketing site serves, on our own
+ *   domain: `logo.svg` at `any` size, and `logo.png` rendered from it at
+ *   512x512, because a client that renders icons must support PNG and need
+ *   not support SVG.
+ *
+ * The MCP Registry entry (`server.json`) states the same title, description,
+ * website and icons, and `package.json`'s description opens with the same
+ * sentence; the docs contract holds both to this object.
+ */
+export declare const SERVER_INFO: Omit<Implementation, 'version'>;
 /**
  * The one tool authored per transport — its INPUT differs (a filesystem path
  * over stdio, inline bytes over HTTP), its NAME must not. Exported so the

package/dist/vocabulary.js

@@ -55,6 +55,36 @@ import { formatDuration, PUBLIC_DEPLOYMENT_TTL_SECONDS } from '@shipstatic/types
  * is exactly the shape this package exists to delete.
  */
 export const SERVER_NAME = 'shipstatic';
+/**
+ * Who the server is, as every transport reports it in `serverInfo`: the
+ * fields a client shows a person when they connect. Everything but the
+ * version, which each transport reads from its own manifest.
+ *
+ * - **`title`** is the product's name as people read it (CANON §1).
+ * - **`description`** is this package's root sentence (CANON §2) with no
+ *   qualifier. The hosted server reports it on every door, and on an
+ *   auth-first door "no account needed" is false.
+ * - **`websiteUrl`** and the **icons** name the product, so they are
+ *   production values in every environment, as in any published package.
+ * - **The icons** are the brand mark the marketing site serves, on our own
+ *   domain: `logo.svg` at `any` size, and `logo.png` rendered from it at
+ *   512x512, because a client that renders icons must support PNG and need
+ *   not support SVG.
+ *
+ * The MCP Registry entry (`server.json`) states the same title, description,
+ * website and icons, and `package.json`'s description opens with the same
+ * sentence; the docs contract holds both to this object.
+ */
+export const SERVER_INFO = {
+    name: SERVER_NAME,
+    title: 'ShipStatic',
+    description: 'Deploy static websites, landing pages, and prototypes instantly from AI agents.',
+    websiteUrl: 'https://shipstatic.com',
+    icons: [
+        { src: 'https://www.shipstatic.com/logo.svg', mimeType: 'image/svg+xml', sizes: ['any'] },
+        { src: 'https://www.shipstatic.com/logo.png', mimeType: 'image/png', sizes: ['512x512'] },
+    ],
+};
 /**
  * The one tool authored per transport — its INPUT differs (a filesystem path
  * over stdio, inline bytes over HTTP), its NAME must not. Exported so the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@shipstatic/mcp",
-  "version": "2.5.0",
+  "version": "2.6.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",