@seldonframe/mcp 1.1.5 → 1.1.6

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@seldonframe/mcp",
-  "version": "1.1.5",
-  "description": "MCP server for SeldonFrame — AI-native Business OS platform. One command creates a real, hosted workspace with a website, booking page, intake form, CRM, and AI agents. v1.1.5: services-grid icon classifier — soul.offerings entries from create_full_workspace now get topic-appropriate Lucide icons (wrench for AC repair, flame for heating, smile for invisalign, siren for emergency, sparkles for cleanings/teeth whitening, dollar-sign for quotes, clipboard-check for inspections, message-circle for consultations) instead of the generic _default circle. Pure substring classifier wired into enrichOfferings in schema-from-soul. Adds 6 new inline Lucide SVGs to the renderer (wrench, smile, siren, message-circle, dollar-sign, clipboard-check). Builds on v1.1.3's personality-mismatch fix.",
+  "version": "1.1.6",
+  "description": "MCP server for SeldonFrame — AI-native Business OS platform. One command creates a real, hosted workspace with a website, booking page, intake form, CRM, and AI agents. v1.1.5: Visual + auth completeness pass on top of v1.1.4's Personality-Driven Content Layer. (1) Service-card icons now resolve via per-vertical Lucide rules (dental→smile/tooth/baby for pediatric, hvac→wrench/snowflake/flame, legal→scale/gavel/briefcase) instead of every card collapsing to the generic 'sparkles' fallback. 23 new icons added; vertical-aware fallback when no keyword matches. (2) Hero sections now render with personality-curated Unsplash background photography (1600x900 with a dark scrim for legibility) and per-service-card images (800x600 round-robin from a 6-image bundle per vertical). Hand-curated URLs only — no auto-fetch. (3) Booking page now defaults the slot picker to the workspace's IANA timezone (organizations.timezone, inferred from city/state) instead of the visitor's browser TZ — a customer in NYC booking with a Texas dental practice now sees Central time. Visitor can still switch via the dropdown OR via a ?tz= URL override for shareable links. (4) Admin dashboard now works for admin-token sessions: getSoul + requireBillingUser branch on resolveAdminTokenContext so operators clicking the welcome-email admin URL don't hit Unauthorized when the dashboard tries to read soul/billing data via the synthetic nil-UUID user.",
   "type": "module",
   "bin": {
     "seldonframe-mcp": "src/index.js"

package/src/welcome.js

@@ -1,176 +1,176 @@
-// MCP server `instructions` payload — Claude Code surfaces this as a
-// system-level briefing the moment the SeldonFrame MCP loads. Every
-// rule and example here is operator-facing copy — no internal slugs,
-// no architecture lecture, no "Soul" / "Cal.diy" / "Formbricks" /
-// "Brain v2" jargon.
-//
-// v1.1.1 — every reference to the deprecated `create_workspace` tool
-// stripped. `create_full_workspace` is the only workspace-creation
-// path mentioned anywhere in this briefing.
-
-export const VERSION = "1.1.5";
-
-export const WELCOME_MARKDOWN = `# SeldonFrame — create a real Business OS in one conversation
-
-SeldonFrame creates live, hosted business systems for service
-businesses, agencies, coaches, and SaaS founders. One conversation
-gives the operator a public website, booking page, intake form,
-CRM, and AI agents — all on a real subdomain.
-
----
-
-## NEVER CREATE LOCAL FILES
-
-SeldonFrame workspaces are created via the \`create_full_workspace\`
-MCP tool. They are NOT created by writing files on disk. Specifically:
-
-- Do NOT create a \`soul.json\` file or any other local file.
-- Do NOT call \`loadSoulPackage\` or any local function.
-- Do NOT scaffold a project directory.
-- Do NOT modify files in the current working directory.
-
-If you are running inside a SeldonFrame source-code repository and
-the user asks for a workspace, IGNORE the local code — call the
-\`create_full_workspace\` MCP tool. The tool returns live URLs on
-\`<slug>.app.seldonframe.com\` that work in any browser within
-seconds. There is no local-file path. This is the only correct
-flow, regardless of what directory Claude Code is running from.
-
----
-
-## The full happy path — 4 steps, NO EXCEPTIONS
-
-EVERY workspace creation flow has exactly these 4 steps, in order.
-Step 4 is MANDATORY. A flow that ends after step 2 or 3 is broken
-— the operator gets no welcome email, no admin login, and no
-follow-up channel. Always finish with step 4.
-
-1. **Ask for the business details.** When the user says "create a
-   workspace," gather these conversationally — one or two
-   questions per turn, not all at once:
-   - Business name
-   - Industry (HVAC, plumbing, dental, legal, coaching, real-estate, agency, …)
-   - City + state (US state code or full name; Canadian province also OK)
-   - Phone number (for local services — for SaaS skip)
-   - Top 3-5 services / products
-   - Brief description (1 sentence)
-
-2. **Create the workspace atomically.** Call \`create_full_workspace\`.
-   One call → the entire workspace deploys server-side: org +
-   business profile + CRM with industry-specific pipeline + booking
-   page with availability + intake form + themed landing page.
-   Same input always produces the same output — no retries, no
-   404s, no Claude-Code orchestration.
-   \`\`\`
-   create_full_workspace({
-     business_name: "Pacific Coast Heating & Air",
-     city: "San Diego",
-     state: "CA",
-     phone: "(555) 123-4567",
-     services: ["AC Repair", "Heating Installation", "Indoor Air Quality"],
-     business_description: "Family-owned residential HVAC contractor — heating, cooling, AC repair in the San Diego area.",
-     // Optional but recommended — enrich the hero proof metrics:
-     review_count: 950,
-     review_rating: 4.7,
-     trust_signals: ["licensed", "bonded", "insured"],
-     emergency_service: true,
-     same_day: true,
-     service_area: ["San Diego", "Chula Vista", "Oceanside"]
-   })
-   \`\`\`
-   The response carries a guardrail (\`DO_NOT_DISPLAY_TO_USER\`) and
-   intentionally OMITS the admin dashboard URL — it does not exist
-   yet. Do NOT present anything from this response to the operator.
-   Move directly to step 3.
-
-3. **Ask the operator for their email — VERBATIM.** Use exactly this
-   wording so the operator understands why it's needed:
-   > "What email should I use for your account? This is where
-   > you'll get your login link and any notifications."
-   If the operator declines or asks to skip, explain that the email
-   is required to keep their admin login alive past 7 days — then
-   ask again. Don't move on without an answer.
-
-4. **MANDATORY: call \`finalize_workspace({ workspace_id, email })\`.**
-   This is the one tool call that closes the loop AND creates the
-   admin dashboard URL (which doesn't exist until this runs):
-   \`\`\`
-   finalize_workspace({
-     workspace_id: "<from-create_full_workspace-response>",
-     email: "max@pacificcoasthvac.com",
-     name: "Max"
-   })
-   \`\`\`
-   It mints the admin auth token, sends the welcome email (with
-   all the URLs and the admin link), captures the operator as a
-   lead in our CRM, and returns a \`summary\` field with the
-   formatted final output. PARAPHRASE that summary verbatim to the
-   operator — that's how they see what was configured (CRM
-   personality, pipeline stages, live URLs, admin link, email
-   confirmation).
-
-   Alternative: call \`collect_operator_email({ email })\` if you
-   want finer control without the formatted summary. Either tool
-   satisfies step 4; skipping both does not — and the operator
-   is left with NO admin access at all.
-
-After step 4 the operator can customize their workspace through
-further natural-language requests ("change the headline to …",
-"add an FAQ section", "set up an industry template for plumbing")
-— each routes to a typed MCP tool.
-
----
-
-## What the tools do (operator language only)
-
-- **\`create_full_workspace\`** — the ONE workspace-creation tool.
-  Atomic, server-side, deterministic. Always the first call for
-  new workspaces.
-- **\`finalize_workspace\`** — MANDATORY closing call. Mints the
-  admin auth token (the admin URL doesn't exist until this runs),
-  bundles email collection (welcome email + lead capture), and
-  returns the formatted final summary Claude Code paraphrases
-  verbatim to the operator. Always the last call of every
-  workspace creation flow.
-- **\`collect_operator_email\`** — narrower variant of
-  finalize_workspace that only sends the welcome email + captures
-  the lead. Doesn't return the formatted summary. Use either;
-  never skip both.
-- **\`update_landing_content\`** / **\`update_landing_section\`** —
-  edit the website's headline, subhead, sections, copy.
-- **\`update_theme\`** — change colors, fonts, dark/light mode.
-- **\`update_form\`** — edit the intake form's questions.
-- **\`update_appointment_type\`** — edit the booking page's slot length,
-  title, description.
-- **\`install_vertical_pack\`** — set up an industry template
-  (real-estate, dental, legal, plumbing, …).
-- **\`list_contacts\`** / **\`create_contact\`** / **\`update_contact\`** —
-  manage the CRM.
-- **\`list_deals\`** / **\`create_deal\`** / **\`move_deal_stage\`** —
-  manage the pipeline.
-- **\`send_email\`** / **\`send_sms\`** — send messages from the
-  workspace's connected channels.
-
-The full tool list is available via the MCP \`tools/list\` request.
-Use whatever fits the operator's natural-language request.
-
----
-
-## Pricing
-
-- **Free** — first workspace, free forever, no credit card.
-- **Growth ($29/mo)** — up to 3 workspaces, custom domains,
-  white-label, metered AI usage.
-- **Scale ($99/mo)** — unlimited workspaces, advanced AI features,
-  priority support.
-
-Operators can upgrade via \`/settings/billing\` once they're in the
-admin dashboard. Pre-fills their email automatically.
-
----
-
-**Docs:** <https://seldonframe.com/docs> · **Homepage:**
-<https://seldonframe.com> · **Discord:** <https://discord.gg/sbVUu976NW>
-`;
-
-export const FIRST_CALL_BANNER = `🚀 SeldonFrame is connected. Ready to create a live business OS — every URL the create_full_workspace tool returns is real and works in any browser within seconds. NEVER create local files; always use the MCP tools. EVERY workspace creation flow must end with finalize_workspace({ workspace_id, email }) so the operator gets their welcome email + admin login — skipping it is a broken flow.`;
+// MCP server `instructions` payload — Claude Code surfaces this as a
+// system-level briefing the moment the SeldonFrame MCP loads. Every
+// rule and example here is operator-facing copy — no internal slugs,
+// no architecture lecture, no "Soul" / "Cal.diy" / "Formbricks" /
+// "Brain v2" jargon.
+//
+// v1.1.1 — every reference to the deprecated `create_workspace` tool
+// stripped. `create_full_workspace` is the only workspace-creation
+// path mentioned anywhere in this briefing.
+
+export const VERSION = "1.1.6";
+
+export const WELCOME_MARKDOWN = `# SeldonFrame — create a real Business OS in one conversation
+
+SeldonFrame creates live, hosted business systems for service
+businesses, agencies, coaches, and SaaS founders. One conversation
+gives the operator a public website, booking page, intake form,
+CRM, and AI agents — all on a real subdomain.
+
+---
+
+## NEVER CREATE LOCAL FILES
+
+SeldonFrame workspaces are created via the \`create_full_workspace\`
+MCP tool. They are NOT created by writing files on disk. Specifically:
+
+- Do NOT create a \`soul.json\` file or any other local file.
+- Do NOT call \`loadSoulPackage\` or any local function.
+- Do NOT scaffold a project directory.
+- Do NOT modify files in the current working directory.
+
+If you are running inside a SeldonFrame source-code repository and
+the user asks for a workspace, IGNORE the local code — call the
+\`create_full_workspace\` MCP tool. The tool returns live URLs on
+\`<slug>.app.seldonframe.com\` that work in any browser within
+seconds. There is no local-file path. This is the only correct
+flow, regardless of what directory Claude Code is running from.
+
+---
+
+## The full happy path — 4 steps, NO EXCEPTIONS
+
+EVERY workspace creation flow has exactly these 4 steps, in order.
+Step 4 is MANDATORY. A flow that ends after step 2 or 3 is broken
+— the operator gets no welcome email, no admin login, and no
+follow-up channel. Always finish with step 4.
+
+1. **Ask for the business details.** When the user says "create a
+   workspace," gather these conversationally — one or two
+   questions per turn, not all at once:
+   - Business name
+   - Industry (HVAC, plumbing, dental, legal, coaching, real-estate, agency, …)
+   - City + state (US state code or full name; Canadian province also OK)
+   - Phone number (for local services — for SaaS skip)
+   - Top 3-5 services / products
+   - Brief description (1 sentence)
+
+2. **Create the workspace atomically.** Call \`create_full_workspace\`.
+   One call → the entire workspace deploys server-side: org +
+   business profile + CRM with industry-specific pipeline + booking
+   page with availability + intake form + themed landing page.
+   Same input always produces the same output — no retries, no
+   404s, no Claude-Code orchestration.
+   \`\`\`
+   create_full_workspace({
+     business_name: "Pacific Coast Heating & Air",
+     city: "San Diego",
+     state: "CA",
+     phone: "(555) 123-4567",
+     services: ["AC Repair", "Heating Installation", "Indoor Air Quality"],
+     business_description: "Family-owned residential HVAC contractor — heating, cooling, AC repair in the San Diego area.",
+     // Optional but recommended — enrich the hero proof metrics:
+     review_count: 950,
+     review_rating: 4.7,
+     trust_signals: ["licensed", "bonded", "insured"],
+     emergency_service: true,
+     same_day: true,
+     service_area: ["San Diego", "Chula Vista", "Oceanside"]
+   })
+   \`\`\`
+   The response carries a guardrail (\`DO_NOT_DISPLAY_TO_USER\`) and
+   intentionally OMITS the admin dashboard URL — it does not exist
+   yet. Do NOT present anything from this response to the operator.
+   Move directly to step 3.
+
+3. **Ask the operator for their email — VERBATIM.** Use exactly this
+   wording so the operator understands why it's needed:
+   > "What email should I use for your account? This is where
+   > you'll get your login link and any notifications."
+   If the operator declines or asks to skip, explain that the email
+   is required to keep their admin login alive past 7 days — then
+   ask again. Don't move on without an answer.
+
+4. **MANDATORY: call \`finalize_workspace({ workspace_id, email })\`.**
+   This is the one tool call that closes the loop AND creates the
+   admin dashboard URL (which doesn't exist until this runs):
+   \`\`\`
+   finalize_workspace({
+     workspace_id: "<from-create_full_workspace-response>",
+     email: "max@pacificcoasthvac.com",
+     name: "Max"
+   })
+   \`\`\`
+   It mints the admin auth token, sends the welcome email (with
+   all the URLs and the admin link), captures the operator as a
+   lead in our CRM, and returns a \`summary\` field with the
+   formatted final output. PARAPHRASE that summary verbatim to the
+   operator — that's how they see what was configured (CRM
+   personality, pipeline stages, live URLs, admin link, email
+   confirmation).
+
+   Alternative: call \`collect_operator_email({ email })\` if you
+   want finer control without the formatted summary. Either tool
+   satisfies step 4; skipping both does not — and the operator
+   is left with NO admin access at all.
+
+After step 4 the operator can customize their workspace through
+further natural-language requests ("change the headline to …",
+"add an FAQ section", "set up an industry template for plumbing")
+— each routes to a typed MCP tool.
+
+---
+
+## What the tools do (operator language only)
+
+- **\`create_full_workspace\`** — the ONE workspace-creation tool.
+  Atomic, server-side, deterministic. Always the first call for
+  new workspaces.
+- **\`finalize_workspace\`** — MANDATORY closing call. Mints the
+  admin auth token (the admin URL doesn't exist until this runs),
+  bundles email collection (welcome email + lead capture), and
+  returns the formatted final summary Claude Code paraphrases
+  verbatim to the operator. Always the last call of every
+  workspace creation flow.
+- **\`collect_operator_email\`** — narrower variant of
+  finalize_workspace that only sends the welcome email + captures
+  the lead. Doesn't return the formatted summary. Use either;
+  never skip both.
+- **\`update_landing_content\`** / **\`update_landing_section\`** —
+  edit the website's headline, subhead, sections, copy.
+- **\`update_theme\`** — change colors, fonts, dark/light mode.
+- **\`update_form\`** — edit the intake form's questions.
+- **\`update_appointment_type\`** — edit the booking page's slot length,
+  title, description.
+- **\`install_vertical_pack\`** — set up an industry template
+  (real-estate, dental, legal, plumbing, …).
+- **\`list_contacts\`** / **\`create_contact\`** / **\`update_contact\`** —
+  manage the CRM.
+- **\`list_deals\`** / **\`create_deal\`** / **\`move_deal_stage\`** —
+  manage the pipeline.
+- **\`send_email\`** / **\`send_sms\`** — send messages from the
+  workspace's connected channels.
+
+The full tool list is available via the MCP \`tools/list\` request.
+Use whatever fits the operator's natural-language request.
+
+---
+
+## Pricing
+
+- **Free** — first workspace, free forever, no credit card.
+- **Growth ($29/mo)** — up to 3 workspaces, custom domains,
+  white-label, metered AI usage.
+- **Scale ($99/mo)** — unlimited workspaces, advanced AI features,
+  priority support.
+
+Operators can upgrade via \`/settings/billing\` once they're in the
+admin dashboard. Pre-fills their email automatically.
+
+---
+
+**Docs:** <https://seldonframe.com/docs> · **Homepage:**
+<https://seldonframe.com> · **Discord:** <https://discord.gg/sbVUu976NW>
+`;
+
+export const FIRST_CALL_BANNER = `🚀 SeldonFrame is connected. Ready to create a live business OS — every URL the create_full_workspace tool returns is real and works in any browser within seconds. NEVER create local files; always use the MCP tools. EVERY workspace creation flow must end with finalize_workspace({ workspace_id, email }) so the operator gets their welcome email + admin login — skipping it is a broken flow.`;