@pitcher/cli-scripts 2.8.0 → 2.10.0

package/README.md

@@ -10,6 +10,55 @@ p --help
 p command --help
 ```
 
+## MCP server
+
+Run `p mcp` to start a stdio [MCP](https://modelcontextprotocol.io) server that exposes this CLI's commands as tools to an MCP-capable host (Claude Desktop, Claude Code, etc). It wraps 50 tools, one per CLI `run*` function: every command above (including `dsr create` + `dsr bind-landing`) except the five local `scaffold` subcommands (which just print/write a starter file and make no request). `dev-sync` is exposed as a one-shot sync only; the continuous `watch` mode is not available as a tool.
+
+```bash
+p mcp
+# or without a global install
+npx @pitcher/cli-scripts mcp
+```
+
+### Environment variables
+
+Auth and org scope are resolved once at boot from environment variables. They are never tool inputs, so the model cannot change org or credentials mid-session.
+
+- `NG_API_KEY` (required, secret): the API key the server authenticates as.
+- `NG_ORG` (default `dev`): organization subdomain, or set `NG_URL` directly for a full origin.
+- `NG_ENV` (`prod` or `test`): controls the destructive-hint guard on write tools (see below). Defaults to a guess based on `NG_ORG` when unset.
+
+One config entry = one org, because the API key is org-specific. To work against multiple orgs, add multiple entries (e.g. `pitcher-dev`, `pitcher-prod`) with different env blocks; do not try to pass org per tool call.
+
+### Host config example (Claude Desktop / `.mcp.json`)
+
+```jsonc
+"pitcher": {
+  "command": "npx",
+  "args": ["-y", "@pitcher/cli-scripts", "mcp"],
+  "env": { "NG_API_KEY": "<key>", "NG_ORG": "dev" }
+}
+```
+
+### Tool annotations
+
+- Read commands are marked `readOnlyHint`. `dev-sync` counts as a write (it mutates remote dev-override state).
+- `publish-app` is always marked `destructiveHint` (it creates a live, org-visible release). Other write tools get `destructiveHint` only when the resolved environment is production (`NG_ENV=prod`, or `NG_ORG` other than `dev` with `NG_ENV` unset). This steers hosts toward requiring extra confirmation before mutating a production org.
+
+### Desktop Extension (`.mcpb`)
+
+For one-click install in Claude Desktop (name + icon, an install-time API-key/org form, no hand-edited config, no Node prerequisite), build a `.mcpb` bundle:
+
+```bash
+yarn mcpb:pack        # → pitcher.mcpb (validated + packed)
+```
+
+Install by double-clicking `pitcher.mcpb` (or Settings → Extensions → Install Extension). Claude Desktop prompts for the API key (stored in the OS keychain) and organization; both are editable afterward, so switching orgs needs no reinstall.
+
+The bundle reuses the same server as `p mcp` but registers a **content-tool subset (47)** — it omits the developer-only `publish-app` and `dev-sync`/`dev-sync-revert`. The `organization` field accepts a subdomain (`acme`), a bare hostname (`acme.my.pitcher.com`), or a full `https://` URL. Build details (esbuild single-file, version injection) live in `mcpb/` and `CLAUDE.md`.
+
+This section is a reference only. For app-development conventions (modules, settings, mount points, SFDC), see the `pitcher-apps` skill, not this README.
+
 ## To run the `publish-app` command:
 
 ```bash
@@ -207,6 +256,9 @@ Create/list/get HTML email templates for the emails app. `create`, `list`, and `
 # Create a template from an HTML file (inline CSS)
 p email-template create --instance-id 01... --name "Welcome" --body-file ./welcome.html --api-key myapikey
 
+# ...or pass the HTML inline instead of a file (use one, not both)
+p email-template create --instance-id 01... --name "Welcome" --body-html "<p>Hi {{recipient.firstName}}</p>" --api-key myapikey
+
 # List templates (optionally filter by name/status/category/target)
 p email-template list --instance-id 01... --api-key myapikey
 
@@ -229,6 +281,9 @@ Create/list DSR (Digital Sales Room) landing-page templates, and set one as the
 # Create a landing template from an HTML file (must contain the email-gate marker)
 p dsr-landing create --instance-id 01... --name "Default" --html-file ./landing.html --api-key myapikey
 
+# ...or pass the HTML (and optionally CSS) inline instead of a file (use one, not both)
+p dsr-landing create --instance-id 01... --name "Default" --html "<div data-pitcher-email-gate></div>" --api-key myapikey
+
 # Create and set as default in one call
 p dsr-landing create --instance-id 01... --name "Default" --html-file ./landing.html --default --api-key myapikey
 
@@ -242,7 +297,7 @@ p dsr-landing list --instance-id 01... --api-key myapikey
 p dsr-landing scaffold --out ./landing.html --api-key myapikey
 ```
 
-`--html-file` must contain the `data-pitcher-email-gate` marker verbatim (the platform injects the email-gate form there) — `create` fails client-side before any request if it's missing.
+The landing HTML (whether via `--html-file` or `--html`) must contain the `data-pitcher-email-gate` marker verbatim (the platform injects the email-gate form there) — `create` fails client-side before any request if it's missing. Provide exactly one of `--html` / `--html-file` (and at most one of `--css` / `--css-file`).
 
 Run `p dsr-landing create --help` for the full token/marker reference (editable-region attributes, recipient/customer/org/rep tokens).
 

package/dist/index.js

@@ -25,6 +25,7 @@ import { createGroupsCommand } from './src/commands/groups.js';
 import { createRolesCommand } from './src/commands/roles.js';
 import { createMetadataTemplateCommand } from './src/commands/metadataTemplate.js';
 import { createDsrCommand } from './src/commands/dsr.js';
+import { createMcpCommand } from './src/commands/mcp.js';
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);
 const pkg = JSON.parse(readFileSync(join(__dirname, '..', 'package.json'), 'utf8'));
@@ -57,4 +58,5 @@ program.addCommand(createMetadataTemplateCommand());
 program.addCommand(createDsrCommand());
 program.addCommand(createOrgCommand());
 program.addCommand(createAnalyticsCommand());
+program.addCommand(createMcpCommand());
 program.parseAsync(process.argv);

package/dist/src/commands/canvases.js

@@ -13,14 +13,17 @@ export async function runCanvasesList(opts, deps = {}) {
         assertIntFlags(opts);
         const client = clientFor(opts, deps);
         const params = { instance_id: opts.instanceId, ...listPageParams(opts) };
-        // Send each type flag ONLY when set. The server FilterSet does
-        // setdefault("is_block", False), so blocks are hidden unless --is-block.
-        if (opts.isTemplate)
-            params.is_template = true;
-        if (opts.isSection)
-            params.is_section = true;
-        if (opts.isBlock)
-            params.is_block = true;
+        // Forward each type flag only when explicitly set (true OR false) — the server honors
+        // is_section=false / is_template=false for precise type filtering. CLI switches are
+        // present→true / absent→undefined, so this is behavior-preserving for the CLI; it lets a
+        // programmatic caller (the MCP `type` filter) isolate one canvas type. The server FilterSet
+        // does setdefault("is_block", False), so blocks stay hidden unless is_block is set.
+        if (opts.isTemplate !== undefined)
+            params.is_template = opts.isTemplate;
+        if (opts.isSection !== undefined)
+            params.is_section = opts.isSection;
+        if (opts.isBlock !== undefined)
+            params.is_block = opts.isBlock;
         if (opts.tags)
             params.tags__in = opts.tags;
         if (opts.idIn)

package/dist/src/commands/dsrLanding.d.ts

@@ -8,7 +8,9 @@ export interface DsrLandingDeps {
 export declare function runDsrLandingCreate(opts: CommonOpts & {
     instanceId?: string;
     name?: string;
+    html?: string;
     htmlFile?: string;
+    css?: string;
     cssFile?: string;
     mergeSchema?: string;
     thumbnailUrl?: string;

package/dist/src/commands/dsrLanding.js

@@ -3,7 +3,7 @@ import { clientFor, toCliError } from '../core/http.js';
 import { ok, fail } from '../core/envelope.js';
 import { createCliError } from '../core/errors.js';
 import { emitEnvelope } from '../core/output.js';
-import { readTextFile } from '../core/readInput.js';
+import { resolveTextInput } from '../core/readInput.js';
 import { parseJsonArray } from '../schema/content.js';
 import { withAuthFlags } from './withAuth.js';
 import { withInstanceFlag } from './withInstance.js';
@@ -12,7 +12,7 @@ const DSR_ENDPOINT = '/core/api/protected/dsr-landing-templates';
 const REQUIRED_MARKER = 'data-pitcher-email-gate';
 const TOKEN_HELP = `
 Required marker (the platform injects the email-gate form here at render time):
-  data-pitcher-email-gate    must be present verbatim in --html-file, or create fails client-side
+  data-pitcher-email-gate    must be present verbatim in the landing HTML (--html or --html-file), or create fails client-side
 
 Editable regions (optional, edited in the DSR landing editor without touching markup):
   data-field-id="..."            unique id for the editable block
@@ -33,10 +33,15 @@ export async function runDsrLandingCreate(opts, deps = {}) {
             throw createCliError('VALIDATION', '--name is required for dsr-landing create');
         if (!opts.instanceId)
             throw createCliError('VALIDATION', '--instance-id is required for dsr-landing create');
-        if (!opts.htmlFile)
-            throw createCliError('VALIDATION', '--html-file is required for dsr-landing create');
-        // readTextFile throws VALIDATION on a missing/unreadable file, before any request is made.
-        const html = readTextFile(opts.htmlFile);
+        // Inline HTML (html) OR a file path (htmlFile), not both — exactly one is required.
+        // Inline is the only route that works in hosts without a shared filesystem (e.g. Claude
+        // Desktop). resolveTextInput throws VALIDATION on conflict/oversize/unreadable.
+        const html = resolveTextInput(opts.html, opts.htmlFile, 'html');
+        if (html === undefined) {
+            // host-neutral wording: the MCP tool params are html/htmlFile, the CLI flags are --html/--html-file
+            throw createCliError('VALIDATION', 'provide the landing HTML inline or as a file (html / htmlFile) for dsr-landing create');
+        }
+        // Marker check runs on the resolved HTML regardless of source.
         if (!html.includes(REQUIRED_MARKER)) {
             throw createCliError('VALIDATION', `landing HTML must contain the ${REQUIRED_MARKER} marker`);
         }
@@ -44,8 +49,9 @@ export async function runDsrLandingCreate(opts, deps = {}) {
             throw createCliError('VALIDATION', '--language must be at most 10 characters');
         }
         const body = { instance_id: opts.instanceId, name: opts.name, html };
-        if (opts.cssFile)
-            body.css = readTextFile(opts.cssFile);
+        const css = resolveTextInput(opts.css, opts.cssFile, 'css');
+        if (css !== undefined)
+            body.css = css;
         if (opts.mergeSchema)
             body.merge_schema = parseJsonArray(opts.mergeSchema, 'merge-schema');
         if (opts.thumbnailUrl)
@@ -117,8 +123,10 @@ export function createDsrLandingCommand() {
     const cmd = new Command('dsr-landing').description('create/list DSR (Digital Sales Room) landing-page templates, and set one as default');
     withInstanceFlag(withAuthFlags(cmd.command('create')))
         .option('--name <name>', 'Template name (required)')
-        .option('--html-file <path>', `Path to the landing HTML (required; must contain ${REQUIRED_MARKER})`)
-        .option('--css-file <path>', 'Path to a CSS file for the template')
+        .option('--html <html>', `Inline landing HTML (must contain ${REQUIRED_MARKER}). Use this OR --html-file`)
+        .option('--html-file <path>', `Path to the landing HTML (must contain ${REQUIRED_MARKER}). Use this OR --html`)
+        .option('--css <css>', 'Inline CSS for the template. Use this OR --css-file')
+        .option('--css-file <path>', 'Path to a CSS file for the template. Use this OR --css')
         .option('--merge-schema <json>', 'Merge schema array as inline JSON')
         .option('--language <lang>', 'Language code (max 10 chars)')
         .option('--thumbnail-url <url>', 'Thumbnail image URL')

package/dist/src/commands/emailTemplate.d.ts

@@ -8,6 +8,7 @@ export interface EmailTemplateDeps {
 export declare function runEmailTemplateCreate(opts: CommonOpts & {
     instanceId?: string;
     name?: string;
+    bodyHtml?: string;
     bodyFile?: string;
     subject?: string;
     tags?: string;

package/dist/src/commands/emailTemplate.js

@@ -3,7 +3,7 @@ import { clientFor, toCliError } from '../core/http.js';
 import { ok, fail } from '../core/envelope.js';
 import { createCliError } from '../core/errors.js';
 import { emitEnvelope } from '../core/output.js';
-import { readTextFile } from '../core/readInput.js';
+import { resolveTextInput } from '../core/readInput.js';
 import { listLimitOffsetParams } from '../core/pagination.js';
 import { assertIntFlags, parseJsonObject } from '../schema/content.js';
 import { withAuthFlags } from './withAuth.js';
@@ -26,9 +26,12 @@ export async function runEmailTemplateCreate(opts, deps = {}) {
         const body = { name: opts.name };
         if (opts.subject)
             body.subject = opts.subject;
-        // readTextFile throws VALIDATION on a missing/unreadable file, before any request is made.
-        if (opts.bodyFile)
-            body.body = readTextFile(opts.bodyFile);
+        // Inline body (bodyHtml) OR a file path (bodyFile), not both. Inline is the only
+        // route that works in hosts without a shared filesystem (e.g. Claude Desktop).
+        // resolveTextInput throws VALIDATION on conflict/oversize/unreadable, before any request.
+        const bodyHtml = resolveTextInput(opts.bodyHtml, opts.bodyFile, 'body');
+        if (bodyHtml !== undefined)
+            body.body = bodyHtml;
         if (opts.tags)
             body.tags = parseJsonObject(opts.tags, 'tags');
         if (opts.metadata)
@@ -86,6 +89,7 @@ export function createEmailTemplateCommand() {
     const cmd = new Command('email-template').description('create/list/get HTML email templates for the emails app');
     withInstanceFlag(withAuthFlags(cmd.command('create')))
         .option('--name <name>', 'Template name (required)')
+        .option('--body-html <html>', 'Inline HTML body (inline CSS). Use this OR --body-file')
         .option('--body-file <path>', 'Path to an HTML file (inline CSS) used as the template body')
         .option('--subject <text>', 'Email subject (supports {{tokens}})')
         .option('--tags <json>', 'Tags object as inline JSON')

package/dist/src/commands/mcp.d.ts

@@ -0,0 +1,2 @@
+import { Command } from 'commander';
+export declare function createMcpCommand(): Command;

package/dist/src/commands/mcp.js

@@ -0,0 +1,18 @@
+import { Command } from 'commander';
+import { runMcpServe } from '../mcp/serve.js';
+import { isCliError } from '../core/errors.js';
+export function createMcpCommand() {
+    return new Command('mcp')
+        .description('Run the Pitcher MCP server over stdio (reads NG_API_KEY, NG_ORG/NG_URL, NG_ENV from env)')
+        .action(async () => {
+        try {
+            await runMcpServe();
+        }
+        catch (e) {
+            const message = isCliError(e) ? e.message : e instanceof Error ? e.message : String(e);
+            console.error(`[pitcher-mcp] failed to start: ${message}`);
+            process.exitCode = isCliError(e) ? e.exitCode : 1;
+            return;
+        }
+    });
+}

package/dist/src/core/readInput.d.ts

@@ -1,2 +1,4 @@
 export declare function readTextFile(filePath: string): string;
 export declare function readJsonFile(filePath: string): unknown;
+export declare const MAX_INLINE_BYTES = 400000;
+export declare function resolveTextInput(inline: string | undefined, file: string | undefined, label: string): string | undefined;

package/dist/src/core/readInput.js

@@ -21,3 +21,27 @@ export function readJsonFile(filePath) {
         throw createCliError('VALIDATION', `invalid JSON in ${filePath}`);
     }
 }
+// Cap inbound inline content so a runaway model-generated payload fails cleanly
+// client-side (a clear VALIDATION) instead of ballooning memory or POSTing a huge body
+// that the platform rejects with an opaque 4xx. Bytes, not chars (UTF-8).
+export const MAX_INLINE_BYTES = 400000;
+// Resolve a text field from either an inline string or a file path (exactly one).
+// Truthy guards (not `!== undefined`) preserve the pre-existing falsy-skip behavior:
+// an empty inline string or empty path counts as "not provided", matching the old
+// `if (opts.bodyFile)` / `if (opts.htmlFile)` checks. Returns undefined if neither.
+// The size cap applies only to inline content — a file path is disk-bounded already,
+// and capping it could break existing large-file callers.
+export function resolveTextInput(inline, file, label) {
+    if (inline && file) {
+        throw createCliError('VALIDATION', `provide either an inline ${label} or a ${label} file, not both`);
+    }
+    if (inline) {
+        if (Buffer.byteLength(inline, 'utf-8') > MAX_INLINE_BYTES) {
+            throw createCliError('VALIDATION', `inline ${label} exceeds ${MAX_INLINE_BYTES} bytes`);
+        }
+        return inline;
+    }
+    if (file)
+        return readTextFile(file);
+    return undefined;
+}

package/dist/src/mcp/bundled.d.ts

@@ -0,0 +1,4 @@
+import type { ToolDescriptor } from './tools/types.js';
+export declare const BUNDLE_EXCLUDED_TOOLS: Set<string>;
+export declare const bundledTools: ToolDescriptor[];
+export declare function normalizeOrgUrl(env: NodeJS.ProcessEnv): void;

package/dist/src/mcp/bundled.js

@@ -0,0 +1,25 @@
+import { allTools } from './registry.js';
+// Developer-only tools excluded from the consumer .mcpb bundle. `publish_app` is alwaysDestructive
+// (creates a live, org-visible app release); `dev_sync`/`dev_sync_revert` mutate remote S3 dev state.
+// None are relevant to a non-technical adopter installing the extension. The CLI `p mcp` keeps all 50.
+export const BUNDLE_EXCLUDED_TOOLS = new Set(['pitcher_publish_app', 'pitcher_dev_sync', 'pitcher_dev_sync_revert']);
+// The tool set the .mcpb bundle registers.
+export const bundledTools = allTools.filter((t) => !BUNDLE_EXCLUDED_TOOLS.has(t.name));
+// resolveBaseUrl interpolates NG_ORG into `https://<org>.my.pitcher.com`, so anything that is
+// already a host (a full URL, or a bare hostname like "acme.my.pitcher.com") must route via NG_URL
+// instead — otherwise it becomes a double-interpolated garbage host. The .mcpb install form accepts
+// a subdomain, hostname, or full URL in one `org` field; this moves host-shaped values to NG_URL
+// before the server reads env. A plain subdomain (no dot) stays in NG_ORG. Mutates env in place.
+export function normalizeOrgUrl(env) {
+    const org = env.NG_ORG?.trim();
+    if (!org)
+        return;
+    if (/^https?:\/\//i.test(org)) {
+        env.NG_URL = org;
+        delete env.NG_ORG;
+    }
+    else if (org.includes('.')) {
+        env.NG_URL = `https://${org}`;
+        delete env.NG_ORG;
+    }
+}

package/dist/src/mcp/env.d.ts

@@ -0,0 +1,7 @@
+export interface McpEnv {
+    apiKey: string;
+    org?: string;
+    url?: string;
+    prod: boolean;
+}
+export declare function resolveMcpEnv(env?: NodeJS.ProcessEnv): McpEnv;

package/dist/src/mcp/env.js

@@ -0,0 +1,13 @@
+import { createCliError } from '../core/errors.js';
+export function resolveMcpEnv(env = process.env) {
+    const apiKey = env.NG_API_KEY?.trim();
+    if (!apiKey) {
+        throw createCliError('AUTH', 'NG_API_KEY is required to run the MCP server (set it in the host config env).');
+    }
+    const org = env.NG_ORG?.trim() || 'dev';
+    const url = env.NG_URL?.trim() || undefined;
+    const ngEnv = env.NG_ENV?.trim();
+    const isDevHost = url ? /\/\/dev\.my\.pitcher\.com(\/|$)/.test(url) : org === 'dev';
+    const prod = ngEnv === 'prod' ? true : ngEnv === 'test' ? false : !isDevHost;
+    return { apiKey, org, url, prod };
+}

package/dist/src/mcp/prompts/dsrLanding.d.ts

@@ -0,0 +1,2 @@
+import type { PromptDescriptor } from './types.js';
+export declare const dsrLandingPrompts: PromptDescriptor[];

package/dist/src/mcp/prompts/dsrLanding.js

@@ -0,0 +1,40 @@
+import { z } from 'zod';
+import { instanceLine, recipePreamble } from './shared.js';
+export const dsrLandingPrompts = [
+    {
+        name: 'seed_dsr_landing',
+        title: 'Create DSR landing page',
+        description: 'Author a responsive DSR (Digital Sales Room) landing-page template and create it in an instance.',
+        argsSchema: {
+            instance_id: z.string().optional().describe('Target instance ID (leave blank to resolve interactively)'),
+            vertical: z.string().optional().describe('pharma | medtech | cpg | finserv | generic'),
+            set_default: z.string().optional().describe('"true" to also set it as the instance default'),
+        },
+        build: (args) => {
+            const vertical = args.vertical || 'generic';
+            const setDefault = args.set_default === 'true';
+            const text = [
+                recipePreamble(),
+                '',
+                '## Task: seed a DSR landing page',
+                instanceLine(args.instance_id),
+                `Vertical: ${vertical}.`,
+                '',
+                'Steps:',
+                '1. Draft a responsive landing HTML following the principles above. It **must contain the ' +
+                    '`data-pitcher-email-gate` marker** (the platform injects the email-gate form there). Use ' +
+                    '`clamp()` for fluid sizing (no media queries), guard `{{rep.*}}` merge fields with fallbacks, ' +
+                    'and pick an aesthetic that fits the vertical.',
+                '2. Create it by calling `pitcher_dsr_landing_create` with ' +
+                    `\`{ instanceId, name, html${setDefault ? ', default: true' : ''} }\` — pass the HTML **inline via ` +
+                    '`html`**, not a file path (inline is the only route that works in hosts without a shared filesystem).',
+                setDefault
+                    ? '   (`set_default` was "true" → pass `default: true` so it becomes the instance default.)'
+                    : '   (Leave `default` unset — the caller did not ask to set it as the instance default.)',
+                '3. The create endpoint is editor-gated; if it returns 403, surface it as-is. Report the created ' +
+                    'template id and, if applicable, the DSR link.',
+            ].join('\n');
+            return [{ role: 'user', content: { type: 'text', text } }];
+        },
+    },
+];

package/dist/src/mcp/prompts/emailTemplate.d.ts

@@ -0,0 +1,2 @@
+import type { PromptDescriptor } from './types.js';
+export declare const emailTemplatePrompts: PromptDescriptor[];

package/dist/src/mcp/prompts/emailTemplate.js

@@ -0,0 +1,34 @@
+import { z } from 'zod';
+import { instanceLine, recipePreamble } from './shared.js';
+export const emailTemplatePrompts = [
+    {
+        name: 'seed_email_template',
+        title: 'Create email template',
+        description: 'Author an on-brand HTML email template for the emails app and create it in an instance.',
+        argsSchema: {
+            instance_id: z.string().optional().describe('Target instance ID (leave blank to resolve interactively)'),
+            vertical: z.string().optional().describe('pharma | medtech | cpg | finserv | generic'),
+            use_case: z.string().optional().describe('Short description of what this email is for'),
+        },
+        build: (args) => {
+            const vertical = args.vertical || 'generic';
+            const useCase = args.use_case || 'a general product-update email a rep would send to a customer';
+            const text = [
+                recipePreamble(),
+                '',
+                '## Task: seed an email template',
+                instanceLine(args.instance_id),
+                `Vertical: ${vertical}. Use case: ${useCase}.`,
+                '',
+                'Steps:',
+                '1. Draft compliant inline-CSS HTML following the principles above: max ~620px, table layout, ' +
+                    'one clear CTA, visually distinct editable fields, and a vertical-appropriate greeting and ' +
+                    'compliance footer.',
+                '2. Create it by calling `pitcher_email_template_create` with `{ instanceId, name, bodyHtml }` — ' +
+                    'pass the HTML **inline via `bodyHtml`** (a file path cannot cross a host\'s sandbox boundary, so always inline).',
+                '3. Report the created template id and name.',
+            ].join('\n');
+            return [{ role: 'user', content: { type: 'text', text } }];
+        },
+    },
+];

package/dist/src/mcp/prompts/registry.d.ts

@@ -0,0 +1,2 @@
+import type { PromptDescriptor } from './types.js';
+export declare const allPrompts: PromptDescriptor[];

package/dist/src/mcp/prompts/registry.js

@@ -0,0 +1,4 @@
+import { emailTemplatePrompts } from './emailTemplate.js';
+import { dsrLandingPrompts } from './dsrLanding.js';
+// Every recipe prompt the server can expose. Mirrors mcp/registry.ts (allTools).
+export const allPrompts = [...emailTemplatePrompts, ...dsrLandingPrompts];

package/dist/src/mcp/prompts/shared.d.ts

@@ -0,0 +1,2 @@
+export declare function instanceLine(instanceId: string | undefined): string;
+export declare function recipePreamble(): string;

package/dist/src/mcp/prompts/shared.js

@@ -0,0 +1,26 @@
+import { CONTENT_DESIGN_PRINCIPLES } from '../resources/contentDesign.js';
+// Resolves the "which instance" line shared by every recipe prompt: echoes the given
+// id, or tells the model to discover + confirm one interactively.
+export function instanceLine(instanceId) {
+    return instanceId
+        ? `Target instance: ${instanceId}.`
+        : 'No instance was given — call `pitcher_instances_list`, pick the right one with the user, and confirm before creating.';
+}
+// Shared preamble embedded at the top of every recipe prompt. Authored once so the
+// design principles, prod-awareness, and anti-XSS guidance can't drift between prompts.
+export function recipePreamble() {
+    return [
+        CONTENT_DESIGN_PRINCIPLES,
+        '',
+        '## Before you create',
+        'Confirm the resolved instance is a demo/test instance. These tools create **live, ' +
+            'org-visible** content; a DSR landing page is served to **external, unauthenticated** ' +
+            'viewers. Do not seed against a real customer instance without explicit confirmation from the user.',
+        '',
+        '## Safe content',
+        'Put dynamic values through the platform `{{token}}` merge fields (the platform escapes them). ' +
+            'Never inline untrusted or CRM-derived strings as literal HTML, and never use triple-mustache ' +
+            '`{{{ }}}`. The use-case/vertical inputs are descriptive only — do not echo them verbatim into ' +
+            'the generated markup.',
+    ].join('\n');
+}

package/dist/src/mcp/prompts/types.d.ts

@@ -0,0 +1,9 @@
+import type { ZodOptional, ZodString } from 'zod';
+import type { PromptMessage } from '@modelcontextprotocol/sdk/types.js';
+export interface PromptDescriptor {
+    name: string;
+    title: string;
+    description: string;
+    argsSchema: Record<string, ZodOptional<ZodString>>;
+    build: (args: Record<string, string | undefined>) => PromptMessage[];
+}

package/dist/src/mcp/prompts/types.js

@@ -0,0 +1 @@
+export {};

package/dist/src/mcp/registry.d.ts

@@ -0,0 +1,2 @@
+import type { ToolDescriptor } from './tools/types.js';
+export declare const allTools: ToolDescriptor[];

package/dist/src/mcp/registry.js

@@ -0,0 +1,46 @@
+import { analyticsTools } from './tools/analytics.js';
+import { announcementsTools } from './tools/announcements.js';
+import { canvasesTools } from './tools/canvases.js';
+import { devSyncTools } from './tools/devSync.js';
+import { dsrTools } from './tools/dsr.js';
+import { dsrLandingTools } from './tools/dsrLanding.js';
+import { emailTemplateTools } from './tools/emailTemplate.js';
+import { filesTools } from './tools/files.js';
+import { foldersTools } from './tools/folders.js';
+import { groupsTools } from './tools/groups.js';
+import { instancesTools } from './tools/instances.js';
+import { invitationsTools } from './tools/invitations.js';
+import { membershipsTools } from './tools/memberships.js';
+import { metadataTemplateTools } from './tools/metadataTemplate.js';
+import { orgTools } from './tools/org.js';
+import { publishAppTools } from './tools/publishApp.js';
+import { rolesTools } from './tools/roles.js';
+import { searchTools } from './tools/search.js';
+import { sharedLinksTools } from './tools/sharedLinks.js';
+import { tagsTools } from './tools/tags.js';
+import { themesTools } from './tools/themes.js';
+import { usersTools } from './tools/users.js';
+export const allTools = [
+    ...canvasesTools,
+    ...filesTools,
+    ...foldersTools,
+    ...searchTools,
+    ...instancesTools,
+    ...sharedLinksTools,
+    ...tagsTools,
+    ...announcementsTools,
+    ...dsrLandingTools,
+    ...dsrTools,
+    ...emailTemplateTools,
+    ...themesTools,
+    ...usersTools,
+    ...invitationsTools,
+    ...rolesTools,
+    ...orgTools,
+    ...analyticsTools,
+    ...membershipsTools,
+    ...groupsTools,
+    ...metadataTemplateTools,
+    ...devSyncTools,
+    ...publishAppTools,
+];

package/dist/src/mcp/resources/contentDesign.d.ts

@@ -0,0 +1,3 @@
+import type { ResourceDescriptor } from './types.js';
+export declare const CONTENT_DESIGN_PRINCIPLES = "# Pitcher content design principles\n\nDistilled guidance for authoring good Pitcher demo content. Apply these when generating\nemail templates and DSR landing pages.\n\n## 1. Palette \u2014 derive, never hardcode\nBuild a 6-tone ramp from the instance primary color rather than pasting brand hex codes:\ndarken 30% and 15% for accents/headers, lighten 15/30/60/80% for backgrounds and tints.\nThis keeps content on-brand across instances automatically.\n\n## 2. HTML email standards\n- Max width ~620px, centered in the viewport.\n- Table-based layout \u2014 NOT CSS grid/flex (email clients drop them).\n- All styles inline \u2014 no `<style>` block.\n- Exactly one clear call-to-action.\n- Make editable regions obvious: wrap them in a visually distinct container (colored\n  background, left border, an uppercase label above).\n- Every template needs a realistic demo story \u2014 a use case a sales rep would actually send.\n\n## 3. DSR landing-page standards\n- The HTML MUST contain the `data-pitcher-email-gate` marker (the platform injects the\n  email-gate form there at render time), or creation fails client-side.\n- Responsive without media queries: use `clamp(min, fluid, max)` for sizing plus\n  `flex-wrap: wrap`; that covers 320px to 1440px with no breakpoints.\n- Guard merge fields at the field level with sensible fallbacks, e.g. a default when\n  `{{rep.name}}` is absent.\n\n## 4. Band / bookend layout (shared canvas vocabulary)\n- Hero: full brand fill with a white title.\n- Content bands: alternate white and a faint brand tint; use generous padding.\n- Closing: a deeper brand fill.\n- Avoid the \"washed-out trap\" \u2014 inject real brand fills instead of relying on theme\n  presets that hard-code headings to black.\n\n## 5. Safe dynamic content (security \u2014 required)\nDynamic values go ONLY through the platform's `{{token}}` merge fields, which the platform\nescapes. Never inline untrusted or CRM-derived strings as literal HTML, and never use\ntriple-mustache `{{{ }}}`. DSR landing pages render to external, unauthenticated viewers,\nso unescaped dynamic HTML is a stored-XSS boundary. Descriptive inputs (a use case, a\nvertical) are for steering the design \u2014 do not echo them verbatim into the markup.\n\n## 6. Demo-story discipline (house rules)\n- Every artifact needs a realistic use case a rep would actually send.\n- No real vendor or competitor names.\n- Stats and figures are illustrative, not represented as real customer data.\n- All copy in English.\n";
+export declare const contentDesignResource: ResourceDescriptor;

package/dist/src/mcp/resources/contentDesign.js

@@ -0,0 +1,62 @@
+// Distilled Pitcher content-design nucleus. This is the SINGLE source: the resource
+// below returns it, and both recipe prompts (mcp/prompts/*) embed it inline (a URI
+// mention alone is not auto-fetched by MCP hosts, so prompts must carry the text).
+//
+// Distilled from the personal Claude Code skills `email-templates`, `dsr-landing-seed`,
+// and `playbook-seed` (palette/band vocabulary). Those skills remain the authoritative
+// deep version; keep this in sync on material design changes. Last synced: 2026-07-17.
+export const CONTENT_DESIGN_PRINCIPLES = `# Pitcher content design principles
+
+Distilled guidance for authoring good Pitcher demo content. Apply these when generating
+email templates and DSR landing pages.
+
+## 1. Palette — derive, never hardcode
+Build a 6-tone ramp from the instance primary color rather than pasting brand hex codes:
+darken 30% and 15% for accents/headers, lighten 15/30/60/80% for backgrounds and tints.
+This keeps content on-brand across instances automatically.
+
+## 2. HTML email standards
+- Max width ~620px, centered in the viewport.
+- Table-based layout — NOT CSS grid/flex (email clients drop them).
+- All styles inline — no \`<style>\` block.
+- Exactly one clear call-to-action.
+- Make editable regions obvious: wrap them in a visually distinct container (colored
+  background, left border, an uppercase label above).
+- Every template needs a realistic demo story — a use case a sales rep would actually send.
+
+## 3. DSR landing-page standards
+- The HTML MUST contain the \`data-pitcher-email-gate\` marker (the platform injects the
+  email-gate form there at render time), or creation fails client-side.
+- Responsive without media queries: use \`clamp(min, fluid, max)\` for sizing plus
+  \`flex-wrap: wrap\`; that covers 320px to 1440px with no breakpoints.
+- Guard merge fields at the field level with sensible fallbacks, e.g. a default when
+  \`{{rep.name}}\` is absent.
+
+## 4. Band / bookend layout (shared canvas vocabulary)
+- Hero: full brand fill with a white title.
+- Content bands: alternate white and a faint brand tint; use generous padding.
+- Closing: a deeper brand fill.
+- Avoid the "washed-out trap" — inject real brand fills instead of relying on theme
+  presets that hard-code headings to black.
+
+## 5. Safe dynamic content (security — required)
+Dynamic values go ONLY through the platform's \`{{token}}\` merge fields, which the platform
+escapes. Never inline untrusted or CRM-derived strings as literal HTML, and never use
+triple-mustache \`{{{ }}}\`. DSR landing pages render to external, unauthenticated viewers,
+so unescaped dynamic HTML is a stored-XSS boundary. Descriptive inputs (a use case, a
+vertical) are for steering the design — do not echo them verbatim into the markup.
+
+## 6. Demo-story discipline (house rules)
+- Every artifact needs a realistic use case a rep would actually send.
+- No real vendor or competitor names.
+- Stats and figures are illustrative, not represented as real customer data.
+- All copy in English.
+`;
+export const contentDesignResource = {
+    name: 'content-principles',
+    uri: 'pitcher://design/content-principles',
+    title: 'Pitcher content design principles',
+    description: 'Palette, HTML-email, DSR-landing, band-layout, and safe-token guidance for authoring content.',
+    mimeType: 'text/markdown',
+    read: () => CONTENT_DESIGN_PRINCIPLES,
+};

package/dist/src/mcp/resources/registry.d.ts

@@ -0,0 +1,2 @@
+import type { ResourceDescriptor } from './types.js';
+export declare const allResources: ResourceDescriptor[];