@wix/mcp 1.0.93 → 1.0.94

package/build/bin-standalone.js

@@ -71177,7 +71177,7 @@ var REST_PORTAL_ID = "d1972c09-74e2-4d36-a6f2-54e3310d4ad9";
 var RECIPES_INDEX_URL = "https://dev.wix.com/docs/api-reference/articles/ai-tools/wix-mcp/skills/wix-management-recipes-index";
 var DOCS_URL_PREFIX = "https://dev.wix.com/docs/";
 var SKILLS_REGISTRY_URL = new RegExp(
-  "^https://(?:dev\\.wix\\.com(?:/docs)?|www\\.wix\\.com(?:/velo/reference)?)/skills(?:[/.?#]|$)"
+  "^https://(?:dev\\.wix\\.com(?:/docs)?|www\\.wix\\.com(?:/velo/reference)?)/skills(?:[/.?#]|$)|^https://www\\.wix\\.com/headless/"
 );
 function isSkillsRegistryUrl(url) {
   return SKILLS_REGISTRY_URL.test(url.trim());
@@ -71602,10 +71602,8 @@ function buildSystemReminderGuidelines(includeReadme, includeImageUploadGuidance
   if (includeReadme) {
     lines.push(
       "if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed.",
-      "**Exception \u2014 creating a new Wix site/website:** For a normal creation request \u2014 and only then \u2014 skip WixREADME and the docs search, and route straight to the Wix site-creation tools available to you; their descriptions carry the routing rules. Everything else starts with WixREADME as usual.",
-      "If the user explicitly asks for a headless site, Wix Classic Editor site, or manual account/API-based site creation, call CreateWixBusinessGuide right away \u2014 these don't need the site's purpose first.",
-      "If the user \u2014 or you, earlier in this conversation \u2014 already have a finished page or site in any form (HTML/CSS/JS files, a static build, a zip, another builder's export, a design you can export to HTML) and want it live on Wix, call StartDeployWebsite right away \u2014 not a site-creation tool, not the docs.",
-      "Never default to AI or search templates unless the user explicitly requests it. When the user named no creation method - let the user make that choice as the site-creation tools' descriptions direct. Never route normal site creation through ManageWixSite, CallWixSiteAPI, or ExecuteWixAPI."
+      "**Creating a new Wix site \u2014 and only then \u2014 skip WixREADME and the docs.** First settle one thing: will the user keep working on this site with you, in code, or design it themselves in Wix's editor? In code \u2014 you or the user have code, the two of you designed it here, they asked you to build it, they asked for a headless site, or it is an app: StartDeployWebsite if the code exists in any form, StartHeadlessBuild if not, called right away (it only returns the guide; the site's purpose is not needed first). In Wix's editor: the site-creation tools; their descriptions carry the rules. Everything else starts with WixREADME as usual.",
+      "Never default to AI or search templates unless the user explicitly requests it. When the user named no creation method - let the user make that choice as the site-creation tools' descriptions direct. Never route site creation through ManageWixSite, CallWixSiteAPI, or ExecuteWixAPI."
     );
   }
   lines.push(
@@ -71653,9 +71651,8 @@ function buildSystemReminder(includeReadme, includeImageUploadGuidance = true) {
   );
   const flows = buildSystemReminderFlows(includeReadme);
   return dedent_default`
-    <agent-mandatory-instructions>
-    YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW
-    A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES.
+    <wix-usage-guide>
+    How to work with Wix through these tools. Following these steps avoids failed or incorrect API calls.
     <goal>
     ${AGENT_GOAL}
     </goal>
@@ -71665,7 +71662,7 @@ function buildSystemReminder(includeReadme, includeImageUploadGuidance = true) {
     <flow-description>
     ${flows}
     </flow-description>
-    </agent-mandatory-instructions>
+    </wix-usage-guide>
   `;
 }
 var SYSTEM_REMINDER = buildSystemReminder(true);
@@ -71677,18 +71674,14 @@ var SITE_CREATION_COPY = {
   unstatedMethod: {
     nonWidget: "you MUST ask whether they want to build with AI or start from a template, and create nothing and show nothing until they answer",
     widget: "you MUST call `WixSiteCreation` and let them choose"
-  },
-  normalCreationRoute: {
-    nonWidget: "route those through `WixSiteBuilder` or `SearchSiteTemplates`",
-    widget: "route those through `WixSiteCreation`"
   }
 };
 var SITE_GUIDANCE = dedent_default`
-  First decide which of two different things is being asked for:
-  - The site is code the user or you control — hand-written HTML/CSS/JS, a static build, a zip, another AI builder's export, or a page or design you made earlier in this conversation — and it should go live on Wix. This is also the route whenever the user wants to keep working on the site here, with you: a Wix Headless site is a regular coded site, so you keep full control of the design and can change and redeploy it from this conversation at any time, and Wix business capabilities can be added to it as a backend when they are needed. Call StartDeployWebsite: it returns the recipe to host those exact files as a Wix Headless site (updates reuse the same site and URL; the drop page is only its fallback). Do not offer AI or templates for this and do not call any site-creation tool.
-  - Wix should create the site — generated with AI from a description, or started from a template — and the user will design and edit it in Wix rather than through you. That is what the site-creation tools do; they never take files you already have.
+  First decide who keeps building the site:
+  - **You, in code**: a Wix Headless site, with full control of the design, changed and redeployed from this conversation, Wix business features added as a backend. This is the case when you or the user have code (hand-written files, a static build, a zip, another builder's export, a page you made here): call StartDeployWebsite. It is also the case when nothing is coded yet but the user asked you to build it or asked for a headless site, the two of you worked out its design in this conversation, or it is an app (a game, a dashboard, a tool): call StartHeadlessBuild right away, before asking what the site is for. Do not offer AI or templates for either.
+  - **The user, in Wix's editor**: Wix generates it with AI or starts it from a template, and the user designs it in Wix. That is what the site-creation tools do; they never take files you already have.
 
-  For a new site there are two things to settle: what the site is for, and how to build it. The how is AI generation vs. starting from a template, so naming templates, a template id or Wix Studio (Wix Studio is also the template side) already settles it.
+  For a new site in Wix's editor there are two things to settle: what the site is for, and how to build it. The how is AI generation vs. starting from a template, so naming templates, a template id or Wix Studio (Wix Studio is also the template side) already settles it.
 
   Settle what the site is for first: its purpose, topic, business type, audience, or main visitor action. Naming a method is not a description of the site, and neither is the business or industry on its own.
   If you can't tell yet, ask the preferred question below and nothing else — one question, no creation-method question in the same reply, and no internal tool names.
@@ -71708,6 +71701,7 @@ var toWidget = (text) => Object.values(SITE_CREATION_COPY).reduce(
 );
 var EXECUTE_WIX_API_INTRO = dedent_default`
   Execute JavaScript code against the Wix REST API when code is useful for chaining related calls, pagination, loops, branching, or in-memory transformation.
+  Putting a site live or changing a headless site's files starts with StartDeployWebsite; building a new site in code with StartHeadlessBuild.
 
   CODE CONTRACT:
   - Pass an async function expression: \`async function() { ... }\` or \`async () => { ... }\`. Put every declaration, \`await\`, and \`return\` inside it, and do not invoke it yourself.
@@ -71792,7 +71786,7 @@ var ACCOUNT_SITE_EXECUTE_SCOPE = dedent_default`
   declare const files: Array<{ path: string; content: string; encoding?: "base64" }>;
   \`\`\`
 
-  FILE UPLOADS: files never go inline in \`code\`; two params feed the \`files\` global. \`attachments\` takes files attached in the chat or created in your file sandbox, of any type and size up to 10 MB per call (a zip of a whole site, HTML, images, PDFs): pass the files themselves, all in one call, and the platform resolves each into \`{ download_url, file_id, file_name?, mime_type? }\` — the bytes are fetched for you and arrive as base64 entries named by file name. The \`files\` param takes content you have as text here: text goes raw; a small binary (icon, logo, font) rides as a \`base64\`-tagged entry — large images/video are referenced by URL (\`<img src="https://...">\`), not bundled. \`wix.multipart()\` turns the whole set into one upload body (bytes, so binary is safe):
+  FILE UPLOADS: files never go inline in \`code\`; two params feed the \`files\` global. \`attachments\` works in ChatGPT only: pass files attached in the chat or created in your sandbox (any type, up to 10 MB per call: a zip of a whole site, HTML, images, PDFs) as you have them, by file id or /mnt/data path, all in one call. ChatGPT swaps each for \`{ download_url, file_id, file_name?, mime_type? }\` before the call reaches Wix, and the bytes arrive as base64 entries named by file name. Other clients send the value unchanged and the call fails before running; there, leave \`attachments\` out, or upload from your shell if it reaches the internet. The \`files\` param takes content you have as text here: text goes raw; a small binary (icon, logo, font) rides as a \`base64\`-tagged entry — large images/video are referenced by URL (\`<img src="https://...">\`), not bundled. \`wix.multipart()\` turns the whole set into one upload body (bytes, so binary is safe):
   \`\`\`javascript
   // files param:
   //   === FILE: index.html ===
@@ -71953,7 +71947,7 @@ function buildToolDescriptions(includeReadme, includeImageUploadGuidance = true)
     ReadFullDocsArticle: dedent_default`
     Fetches the full Wix docs article or method article with code examples for using the method.
     Docs articles looks like this: https://dev.wix.com/docs/... and they can either be general docs articles or method articles.
-    Also reads Wix skills pages — https://www.wix.com/skills/<skill>, https://dev.wix.com/docs/skills/<skill>, and the files they link (e.g. .../<skill>/references/<file>.md) — exactly as served.
+    Also reads Wix skills pages — https://www.wix.com/skills/<skill>, https://dev.wix.com/docs/skills/<skill>, and the files they link (e.g. .../<skill>/references/<file>.md) — and Wix Headless agent pages under https://www.wix.com/headless/ (e.g. https://www.wix.com/headless/skill.md), exactly as served.
     Take the URL from the user's message or an earlier tool result. To reach an article you have no URL for, search or browse the docs first.
     For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include ?apiView=SDK.
     ${reminder}
@@ -72001,7 +71995,7 @@ function buildToolDescriptions(includeReadme, includeImageUploadGuidance = true)
     ${reminder}
   `,
     ManageWixSite: dedent_default`
-    Use account level API in order to create a site and update a site.
+    Use account level API in order to update a site.
     Account-level only: this tool acts on the account itself, or on sites as objects within it, and sends no site context. Anything that reads or writes inside a site is site-level and does not belong here — use a site-level tool with that site's \`siteId\`.
     For POST/PATCH/PUT requests, pass the request body as a JSON object or array in the "body" parameter with all the required fields and values as described in the API schema, code examples, or docs you retrieved (e.g. body: {"name": "value", "nested": {"key": "value"}} or body: [{"key": "value"}]).
     The API endpoint url param MUST ALWAYS be taken from the conversation context.
@@ -72080,14 +72074,15 @@ function buildToolDescriptions(includeReadme, includeImageUploadGuidance = true)
 
     Do not call this if the user explicitly asks to build with AI; call \`WixSiteBuilder\` instead.
     Do not call this if the user asks for templates or Wix Studio; call \`SearchSiteTemplates\` instead.
+    Not for a site the user wants you to build in code, a design you worked out together, or an app: call \`StartHeadlessBuild\`.
 
     When calling this tool, infer \`customActions\` from the user's request so the reply can be tailored — 2-3 concrete, industry-specific setup actions for the site (see the input's guidance).
 
     After calling, you MUST speak the message provided in the tool result to the user as your reply — do not stay silent and do not replace it with a one-line pointer to the widget. Write out ALL of it, word for word: its opening line (the "Ready to set up your … site?" question INCLUDING "Choose your path in the widget above:"), BOTH of its option bullets, and its "Next up:" line, each on its own line and in that order. Do not summarize, shorten, drop any line, invent your own opener, rename the options, or add an intro or outro.
   `,
     "import-claude-design-from-url": dedent_default`
-    Import a design created in Claude's design tool into Wix. Takes the signed claudeusercontent.com URL Claude Design produces for its self-contained HTML bundle (all images, fonts, and styles inlined); any other host is rejected. Creates a live Wix-hosted site and returns its URL.
-    NOT for a page or site that exists in any other form (the user's own HTML/CSS/JS, a static build, a zip, another builder's export, a page you made in this conversation) — for those call StartDeployWebsite instead; it returns the recipe to publish the files yourself.
+    Import a design created in Claude's design tool into Wix. Only for the signed \`claudeusercontent.com\` bundle URL Claude Design's "Send to Wix" produces (a self-contained HTML bundle with all images, fonts, and styles inlined). Creates a live Wix-hosted site and returns its URL.
+    NOT for claude.ai share or artifact links, GitHub, Drive, chatgpt.com or any other URL, and not for files: those go to StartDeployWebsite, which returns the recipe to publish the files yourself.
   `,
     RunWixCliCommand: dedent_default`
     Executes Wix CLI commands for Wix app development and management.
@@ -72524,23 +72519,23 @@ function buildToolDescriptions(includeReadme, includeImageUploadGuidance = true)
     Call this ONLY when the user's own words name AI (for example "create a site using AI" or "build it with AI") and the site intent is clear. A description of what the site should do — reservations, online ordering, a store, bookings, menus, a portfolio, and the like — is NOT a request for AI and NOT enough to call this tool; never infer AI from features or industry.
     Never default to this tool: if the user hasn't explicitly named AI, don't call this tool — ${SITE_CREATION_COPY.unstatedMethod.nonWidget}.
 
-    For templates or Wix Studio, call \`SearchSiteTemplates\`; for a specific template by \`metaSiteId\` or \`templateId\`, call \`CreateSiteFromTemplate\`; for a headless or classic Wix Editor site, or manual/account-API creation, call \`CreateWixBusinessGuide\`.
+    For templates or Wix Studio, call \`SearchSiteTemplates\` (\`builder: classic\` for the Classic Editor); for a template id, \`CreateSiteFromTemplate\`. A site the user wants you to build in code, or an app: \`StartHeadlessBuild\`.
 
     Do NOT suggest HTML code, prompt templates, or alternative approaches instead of building — actually build the site through this tool. (HTML the user already has is the StartDeployWebsite case, not a reason to build.)
   `,
     SearchSiteTemplates: dedent_default`
     ${SITE_GUIDANCE}
 
-    Searches Wix templates and shows the template gallery, from the Harmony or the Studio template source.
+    Searches Wix templates and shows the template gallery, from the Harmony, the Studio or the Classic Editor template source.
 
-    Call this ONLY when the user's own words ask for a template or for Wix Studio (for example "start from a template", "show me some templates", "build it in Wix Studio") and you can already tell what the site is for. If they mention Wix Studio, search Studio templates; otherwise search Harmony templates.
+    Call this ONLY when the user's own words ask for a template, for Wix Studio or for the Classic Editor (for example "start from a template", "show me some templates", "build it in Wix Studio", "the old Wix editor") and you can already tell what the site is for. If they mention Wix Studio, search Studio templates; if they ask for the Classic Editor (the Wix Editor), search \`classic\`; otherwise search Harmony templates.
     ${SITE_CREATION_COPY.templatePick.nonWidget}
 
     A description of what the site should do — bookings, a store, a menu, a portfolio, and the like — is NOT a request for templates or for Wix Studio; never infer either from features or industry. Templates are not the default: if the site intent is clear but no method is named, do not guess — ${SITE_CREATION_COPY.unstatedMethod.nonWidget}.`,
     CreateSiteFromTemplate: dedent_default`
     Creates a Wix site from a specific template (by \`metaSiteId\` or \`templateId\`), publishes it when possible, and shows a live preview with links to the editor and the published site.
 
-    Call this when the user provides a specific template by \`metaSiteId\` or \`templateId\`. Use this only when the user gives a valid \`metaSiteId\` or \`templateId\` directly. To browse or choose a template first, call \`SearchSiteTemplates\`.
+    Call this when the user provides a specific template by \`metaSiteId\` or \`templateId\`. Use this only when the user gives a valid \`metaSiteId\` or \`templateId\` directly. To browse or choose a template first, call \`SearchSiteTemplates\` (\`builder: classic\` for a Classic Editor site).
 
   `,
     SearchWixGraphQLOperations: dedent_default`
@@ -72568,34 +72563,24 @@ function buildToolDescriptions(includeReadme, includeImageUploadGuidance = true)
     Compose: put independent reads in one document as several root fields, and use related-entity fields (e.g. \`inventoryItems\`, \`collections\`, \`fulfillments\`) instead of extra round-trips. Select only the fields you need; every object field needs a selection set. Variables: use them for \`JSON\` scalars (filter, sort) and plain scalars (String, Int, ID), declared in the document (e.g. \`query Q($f: JSON) { ... filter: $f ... }\`). Write mutation inputs and any object that contains an enum INLINE as GraphQL literals with enum values unquoted (e.g. \`input: { product: { name: "Mug", productType: PHYSICAL } }\`) — this endpoint fails with 503 when an enum value arrives inside an object-typed variable. For lists page with \`cursorPaging\` or \`paging\` exactly as the input type declares (never the other one), and request \`pageInfo { hasNext total }\`; \`total\` is only populated with offset \`paging\`, so for a cursor-paged list count by walking pages or use a count operation.
     Results: each root field fails independently — \`errors[].path\` names the failing field and \`errors[].extensions.message\` the cause (e.g. PERMISSION_DENIED); \`data\` still holds the fields that succeeded. Mutations return the created/updated entity — read the IDs from it and do not re-query to verify. Large results are truncated: narrow the selection or page size instead of re-running.
     Set \`hasMutations: true\` for any document containing a mutation root field.
+  `,
+    UploadHeadlessWebsiteFiles: dedent_default`
+    The upload step of the StartDeployWebsite and StartHeadlessBuild guides, and nothing else: puts a finished static website's files — index.html plus its CSS/JS/images, a static build, or a zip of the site — onto an existing Wix Headless site by its metaSiteId. Call it ONLY after one of them has returned its guide in this conversation and the site exists: for a new site, first run the recipe's provision call and pass the metaSiteId it returns; for a site deployed earlier, pass its metaSiteId. It does not create sites. Every upload replaces the whole file set and the URL stays. Returns the live URL and the dashboard link, and points back to the recipe for what comes next.
+    Pass the files themselves: in ChatGPT as \`attachments\` (any type, a zip is unpacked), elsewhere as the \`files\` text bundle (\`=== FILE: <path> ===\` sections, \`base64\` tag for small binaries). The site must contain index.html at its root.
+    NOT a site-creation tool: a request to create, build, design or generate a site — with or without a description — never comes here (those are the site-creation tools, after their own questions). Also NOT for media uploads to an existing site (UploadImageToWixSite) or any other API call (ExecuteWixAPI).
   `,
     StartDeployWebsite: dedent_default`
-    The user — or you, earlier in this conversation — ALREADY HAVE a finished page or site, in any form, and it should be live on Wix — or an already-deployed Wix Headless site whose files should be replaced. The site can be HTML/CSS/JS files, a static build (dist/, out/), a zip, another AI builder's export, or a page/design you created in this conversation (export it to HTML first — a finished design IS a finished page). Call this when the user says deploy, host, publish, put online, make it live, get a URL, update my site, or upload my site / index.html.
+    The user — or you, earlier in this conversation — ALREADY HAVE a finished page or site, in any form, and it should be live on Wix — or an already-deployed Wix Headless site whose files should be replaced. The site can be HTML/CSS/JS files, a static build (dist/, out/), a zip, another AI builder's export, or a page/design you created in this conversation (export it to HTML first — a finished design IS a finished page). Call this when the user says deploy, host, put online, make it live, get a URL, upload my site / index.html, or wants to update or redeploy the files of a site you or the user deployed as code.
     Updates keep the same site and URL. Also for implementing a backend on such a site as a Wix Headless project — same site, same URL. Works with or without a Wix login (anonymous deploy with a save link), through the Wix MCP alone or from a shell.
     Missing real functionality — a fake checkout, a form that goes nowhere, bookings — is NOT a reason to rebuild the site with a site-creation tool: deploy the page as is, then add the backend afterwards (the recipe covers it).
-    Returns the full recipe; follow it and run the flow yourself. The drop page is only the fallback when you can't.
-    NOT for: a screenshot, mockup or reference image of a site the user WANTS (nothing exists to deploy yet — that is site creation: WixSiteBuilder / templates); a Claude Design share URL (import-claude-design-from-url); migrating a live site by URL or CSV exports; adding HTML or code into an existing Wix site; uploading images or documents to a site's media (UploadImageToWixSite).
+    Returns the full recipe; follow it and run the flow yourself. When the UploadHeadlessWebsiteFiles tool is available, use it for the recipe's upload step — after the site exists (the recipe's provision call, or a metaSiteId from an earlier deploy) — instead of building the multipart body in code; never before this tool. The drop page is only the fallback when you can't.
+    NOT for: a screenshot or reference of a site the user wants Wix to generate (the site-creation tools); a site described in words with no code yet (StartHeadlessBuild); a Wix editor site's content or settings (WixSiteBuilder's edit mode, or WixREADME); a Claude Design bundle URL (import-claude-design-from-url); migrating a live site by URL or CSV exports; adding HTML or code into an existing Wix site; uploading images or documents to a site's media (UploadImageToWixSite).
   `,
-    CreateWixBusinessGuide: dedent_default`
-    Provides comprehensive documentation for creating a new Wix business (site, app, etc.).
-    Call this ONLY when the user explicitly asks for a headless site, a Wix Classic Editor site, or manual/advanced account/API-based site creation — these don't need the site's purpose first. For normal site-creation ${SITE_CREATION_COPY.normalCreationRoute.nonWidget}; for a specific template id, call \`CreateSiteFromTemplate\`.
-    Exception, even when the user says "headless": if a finished page or site already exists in any form (their own HTML/CSS/JS, a static build, a zip, an AI-builder export, a page you made in this conversation) and they want it hosted, don't call this tool — call StartDeployWebsite, which returns the recipe to publish the files yourself. This guide's CLI flow is for BUILDING a headless frontend, not for hosting ready-made files.
-
-    ## What This Tool Contains
-
-    This tool provides complete documentation including:
-    - Template selection (empty sites or designed templates)
-    - Wix Editor vs Wix Studio options
-    - Regular vs Headless site creation (CLI-based; returns setup instructions)
-    - API endpoint details and parameters
-    - Post-creation steps (OAuth for headless, publishing for regular sites)
-    - App installation instructions
-
-    ## After Reading This Documentation
-
-    **After reading this documentation:**
-    1. Use ManageWixSite for account-level site creation API calls
-    2. Use CallWixSiteAPI / ExecuteWixAPI for site-level follow-up API calls (like install apps if needed)`
+    StartHeadlessBuild: dedent_default`
+    The user wants a site or web app that you build and keep changing in code, here with them, and no code exists yet. Wix runs its business side (store, bookings, CMS, forms, members, payments) as a Wix Headless site. Call this when the user asks you to build it yourself rather than Wix's AI or a template; when the two of you worked out a design in this conversation and nothing is coded yet; when it is an app (a game, a dashboard, a tool); when the user asks for a headless site; when a prompt links \`wix.com/headless/skill.md\` or a project's \`download.zip\`; or to move a Wix site to code.
+    Call it right away: it only returns the guide, and the site's purpose is not needed first (pass "not stated yet" for what you don't know). Returns the full guide; follow it and do the work yourself, choosing its route by what you can reach (a shell that reaches Wix, or this MCP alone).
+    NOT for: files, a build, a zip or a page that already exist (StartDeployWebsite); a site the user will design in Wix's editor (the site-creation tools); a Claude Design URL (import-claude-design-from-url).
+  `
   };
 }
 var defaultToolDescriptions = buildToolDescriptions(true);
@@ -72604,9 +72589,9 @@ var recipesIndexDoc = {
   action: "include"
 };
 var README_INTRO = dedent_default`
-  <agent-mandatory-instructions>
+  <wix-usage-guide>
 
-  YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW:
+  How to work with Wix through these tools:
 
   <source-of-truth>
   Do not answer from memory about anything Wix-specific — this covers every part of your answer, not only API calls: any URL, link, ID, setting location, or product fact you give the user must come from the docs tools, the recipes below, a previous tool result in this conversation, or the user's own message (identifiers and URLs the user supplies are fine to use as given). If a recipe in the index below matches what the user asked for, read it before answering. For APIs, use the search, browse, read-docs, and schema tools as the source of truth for the exact URL, HTTP method, request body shape, response shape, field names, required fields, and enum values before calling an API.
@@ -72658,7 +72643,7 @@ var README_BODY = dedent_default`
       <other-uses>
       Beyond managing user sites, the Wix MCP tools can be used for any other purpose they support — for example, reading Wix SDK docs to write code against the SDK, using the Wix CLI to create apps, answering documentation questions, and so on.
       </other-uses>
-      </agent-mandatory-instructions>
+      </wix-usage-guide>
 `;
 var defaultReadmeDocs = [
   {
@@ -72679,8 +72664,7 @@ var widgetSiteCreationConfig = {
       "WixSiteBuilder",
       "WixSiteCreation",
       "SearchSiteTemplates",
-      "CreateSiteFromTemplate",
-      "CreateWixBusinessGuide"
+      "CreateSiteFromTemplate"
     ].map((tool) => [tool, toWidget(defaultToolDescriptions[tool])])
   )
 };
@@ -73269,7 +73253,7 @@ var paramDescriptions = {
     reason: "One sentence describing the original user request and the task you are trying to accomplish with this search."
   },
   ReadFullDocsArticle: {
-    articleUrl: "The URL of the docs article or method article to fetch. Should be something like https://dev.wix.com/docs/.../... For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include the query param ?apiView=SDK (e.g. https://dev.wix.com/docs/...?apiView=SDK). Wix skills pages (https://www.wix.com/skills/..., https://dev.wix.com/docs/skills/...) are read as-is, including their referenced files."
+    articleUrl: "The URL of the docs article or method article to fetch. Should be something like https://dev.wix.com/docs/.../... For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include the query param ?apiView=SDK (e.g. https://dev.wix.com/docs/...?apiView=SDK). Wix skills pages (https://www.wix.com/skills/..., https://dev.wix.com/docs/skills/...) and Wix Headless agent pages (https://www.wix.com/headless/..., e.g. https://www.wix.com/headless/skill.md) are read as-is, including their referenced files."
   },
   ReadFullDocsMethodSchema: {
     articleUrl: "The URL of the documentation to fetch. Should be something like https://dev.wix.com/docs/.../... For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include the query param ?apiView=SDK (e.g. https://dev.wix.com/docs/...?apiView=SDK).",
@@ -73309,7 +73293,7 @@ var paramDescriptions = {
     operationName: "Operation to run when the document defines more than one named operation.",
     siteId: "The Wix site to run against. Required for site-level operations (anything reading or writing inside a site \u2014 products, orders, contacts, bookings, CMS, blog, members ...). Resolve it with GetSiteContext or ListWixSites; never pass a guessed value.",
     scope: '"site" (default when siteId is given) runs with a site-scoped credential; "account" runs account-level operations (sites, account settings) and ignores siteId.',
-    hasMutations: "Whether this document creates, updates, deletes or otherwise mutates Wix data. True for any mutation root field (in any operation of the document) even when the intent is inspection; false only for pure queries. This flag alone decides whether a transient server error may be retried, so never mark a document that writes as false.",
+    hasMutations: "True if the document contains a mutation root field in any of its operations; false if it contains only queries. A transient server error is retried only when this is false.",
     reason: "One sentence explaining the original user request and why you are running this GraphQL operation to complete it."
   },
   RunWixCliCommand: {
@@ -73573,121 +73557,6 @@ ${skillsContent}`
   );
 }
 
-// src/docs/create-site-guide.ts
-function isHeadlessRequest(prompt) {
-  return !!prompt && /headless/i.test(prompt);
-}
-var HEADLESS_NON_CLI_INSTRUCTIONS = `# Creating a Wix Headless Site
-
-Wix Headless sites require the **Wix CLI** and cannot be created from the Wix dashboard or via REST API alone. Let the user know they need to set up a local development environment with the Wix CLI before proceeding.
-
-## Prerequisites
-- Node.js 18+
-- A terminal / command-line environment
-
-## Steps to Get Started
-
-1. **Install and authenticate the Wix CLI:**
-   \`\`\`
-   npx @wix/cli login
-   \`\`\`
-2. **Follow the quick-start guide:** https://dev.wix.com/docs/go-headless
-3. **For a complete orchestrated setup** (commerce, CMS, bookings, identity), use the Wix Headless skill: https://www.wix-headless.dev/skill.md`;
-var HEADLESS_CLI_INSTRUCTIONS = `# Creating a Wix Headless Site (CLI Flow)
-
-Follow these steps using the \`RunWixCliCommand\` tool to scaffold and configure a Wix Headless site.
-
-## Before You Start
-Ask the user:
-1. What is the brand/site name?
-2. Which local directory should the project be created in?
-
-## Steps
-
-### Step 1 \u2014 Authenticate (if not already done)
-Run: \`npx @wix/cli login\`
-Skip if the user is already authenticated.
-
-### Step 2 \u2014 Scaffold the project
-Use a Wix headless starter template. Ask the user which starter they prefer, or use the default Next.js starter. Follow the scaffolding instructions at: https://dev.wix.com/docs/go-headless
-
-### Step 3 \u2014 Install dependencies
-Run: \`npm install\` in the project directory.
-
-### Step 4 \u2014 Pull environment variables
-Run: \`npx @wix/cli env pull\`
-This writes the \`.env.local\` file with the site's environment variables.
-
-### Step 5 \u2014 Build and verify
-Run: \`npx @wix/cli build\`
-
-### Step 6 \u2014 Release (optional)
-Run: \`npx @wix/cli release\` to deploy.
-
-## Full Orchestration
-For a complete multi-wave headless setup (commerce, CMS, bookings, design system, content seeding), refer to the Wix Headless skill: https://www.wix-headless.dev/skill.md
-
-Use \`RunWixCliCommand\` for each CLI step above.`;
-var CREATE_SITE_DOCS = [
-  {
-    url: "https://dev.wix.com/docs/kb-only/MCP_REST_RECIPES_KB_ID/TRAIN_create_a_new_site_from_template",
-    title: "How to Create a New Wix Site",
-    nextSteps: "\n\n**Next Steps:** Use the ManageWixSite tool to make the API call for creating the Wix site."
-  },
-  {
-    url: "https://dev.wix.com/docs/kb-only/MCP_REST_RECIPES_KB_ID/TRAIN_wix.devcenter.apps.installer.v1.AppsInstallerService.InstallApp",
-    title: "How to Install App on a Wix Site",
-    nextSteps: "\n\n**Next Steps:** Use the CallWixSiteAPI tool to make the API call for installing apps on the Wix site."
-  }
-];
-async function addCreateWixBusinessGuideTools(server2, disableTools = [], toolDescriptions, cliEnabled = false) {
-  if (disableTools.includes("CreateWixBusinessGuide")) {
-    return;
-  }
-  server2.tool(
-    "CreateWixBusinessGuide",
-    toolDescriptions?.["CreateWixBusinessGuide"] ?? defaultToolDescriptions.CreateWixBusinessGuide,
-    {
-      userPrompt: external_exports.string().optional().describe("The user prompt that triggered this tool")
-    },
-    { readOnlyHint: true, destructiveHint: false, openWorldHint: false },
-    async (args, { httpClient }) => {
-      if (isHeadlessRequest(args.userPrompt)) {
-        const isCli = typeof cliEnabled === "function" ? cliEnabled() : cliEnabled;
-        const text = isCli ? HEADLESS_CLI_INSTRUCTIONS : HEADLESS_NON_CLI_INSTRUCTIONS;
-        return { content: [{ type: "text", text }] };
-      }
-      try {
-        const contents = await Promise.all(
-          CREATE_SITE_DOCS.map(async ({ url, title, nextSteps }) => {
-            const articleContent = await fetchArticleContent(
-              httpClient,
-              url,
-              "article",
-              true
-            );
-            const fullContent = `# ${title}
-
-${articleContent}${nextSteps}`;
-            return { type: "text", text: fullContent };
-          })
-        );
-        return { content: contents };
-      } catch (error2) {
-        return {
-          isError: true,
-          content: [
-            {
-              type: "text",
-              text: `Error fetching create site documentation: ${error2.message}`
-            }
-          ]
-        };
-      }
-    }
-  );
-}
-
 // src/docs/start-deploy-website.ts
 var START_DEPLOY_WEBSITE_PARAM_DESCRIPTIONS = {
   userRequest: "The user's request that led here, quoted if short, otherwise summarized in a sentence.",
@@ -73759,6 +73628,87 @@ function addStartDeployWebsiteTool(server2, disableTools = [], toolDescriptions,
   );
 }
 
+// src/docs/start-headless-build.ts
+var START_HEADLESS_BUILD_TOOL_NAME = "StartHeadlessBuild";
+var HEADLESS_GUIDE_URL = "https://www.wix.com/skills/headless-cold-start/headless-kit.md";
+var START_HEADLESS_BUILD_STARTING_POINTS = [
+  "nothing yet",
+  "a design worked out in this conversation",
+  "an existing Wix Headless site",
+  "a project download link",
+  "a Wix site to move to code"
+];
+var START_HEADLESS_BUILD_PARAM_DESCRIPTIONS = {
+  userRequest: START_DEPLOY_WEBSITE_PARAM_DESCRIPTIONS.userRequest,
+  siteDescription: START_DEPLOY_WEBSITE_PARAM_DESCRIPTIONS.siteDescription,
+  startingPoint: "What the build starts from: nothing yet; a design worked out in this conversation; an existing Wix Headless site; a project download link (a download.zip from Wix); or a Wix site to move to code.",
+  siteFunctionality: START_DEPLOY_WEBSITE_PARAM_DESCRIPTIONS.siteFunctionality,
+  agentIdentity: START_DEPLOY_WEBSITE_PARAM_DESCRIPTIONS.agentIdentity,
+  wixAccess: START_DEPLOY_WEBSITE_PARAM_DESCRIPTIONS.wixAccess
+};
+var PREFIX2 = "The following is Wix's headless guide. Follow it end to end and do the work yourself. If you find the user already has the site's code, call StartDeployWebsite instead.";
+var MOVE_TO_CODE_LINE = `Moving a Wix site to code starts from the site's dashboard (Headless settings, "Go Headless"), which hands the owner a prompt with the project's download link. Ask the user for that prompt, then follow the guide with it.`;
+function startHeadlessBuildResponse(guide, startingPoint) {
+  const lines = [];
+  if (startingPoint === "a Wix site to move to code") {
+    lines.push(MOVE_TO_CODE_LINE);
+  }
+  if (guide && guide.trim()) {
+    lines.push(PREFIX2, "---", guide.trim());
+  } else {
+    lines.push(
+      `Wix's headless guide could not be loaded here. It is at ${HEADLESS_GUIDE_URL}: read it whole with ReadFullDocsArticle if you have that tool, otherwise fetch it with curl or your web tool, then follow it end to end and do the work yourself. If you find the user already has the site's code, call StartDeployWebsite instead.`
+    );
+  }
+  return lines.join("\n\n");
+}
+function addStartHeadlessBuildTool(server2, disableTools = [], toolDescriptions, fetchOptions = {}) {
+  if (disableTools.includes(START_HEADLESS_BUILD_TOOL_NAME)) {
+    return;
+  }
+  const d = START_HEADLESS_BUILD_PARAM_DESCRIPTIONS;
+  server2.tool(
+    START_HEADLESS_BUILD_TOOL_NAME,
+    toolDescriptions?.[START_HEADLESS_BUILD_TOOL_NAME] ?? defaultToolDescriptions[START_HEADLESS_BUILD_TOOL_NAME],
+    {
+      userRequest: external_exports.string().min(1).describe(d.userRequest),
+      siteDescription: external_exports.string().min(1).describe(d.siteDescription),
+      startingPoint: external_exports.enum(START_HEADLESS_BUILD_STARTING_POINTS).describe(d.startingPoint),
+      siteFunctionality: external_exports.string().min(1).describe(d.siteFunctionality),
+      agentIdentity: external_exports.string().min(1).describe(d.agentIdentity),
+      wixAccess: external_exports.string().min(1).describe(d.wixAccess)
+    },
+    { readOnlyHint: true, destructiveHint: false, openWorldHint: false },
+    async (args, { httpClient }) => {
+      let guide;
+      try {
+        guide = await fetchArticleContent(
+          httpClient,
+          HEADLESS_GUIDE_URL,
+          "article",
+          true,
+          fetchOptions.skillsPortalUrl,
+          fetchOptions.repo,
+          fetchOptions.commitHash
+        );
+      } catch (error2) {
+        console.warn(
+          "[StartHeadlessBuild] guide fetch failed, returning the pointer:",
+          error2 instanceof Error ? error2.message : error2
+        );
+      }
+      return {
+        content: [
+          {
+            type: "text",
+            text: startHeadlessBuildResponse(guide, args.startingPoint)
+          }
+        ]
+      };
+    }
+  );
+}
+
 // src/docs/docs.ts
 var VALID_DOCS_TOOLS = [
   "WDS",
@@ -73817,8 +73767,8 @@ var addDocsTools = (server2, allowedTools = [
 ], options = {}) => {
   const {
     getToKnowWixEnabled = false,
-    createWixBusinessGuideEnabled = true,
     startDeployWebsiteEnabled = true,
+    startHeadlessBuildEnabled = true,
     disableTools,
     toolDescriptions,
     readmeDocs,
@@ -73830,7 +73780,6 @@ var addDocsTools = (server2, allowedTools = [
     commitHash,
     skillsTags,
     dynamicContextEnabled,
-    cliEnabled = false,
     usePlatformizedSearch = true,
     usePlatformizedBrowse = true
   } = options;
@@ -73876,14 +73825,6 @@ var addDocsTools = (server2, allowedTools = [
       skillsTags
     });
   }
-  if (createWixBusinessGuideEnabled && !disableTools?.includes("CreateWixBusinessGuide")) {
-    addCreateWixBusinessGuideTools(
-      server2,
-      disableTools || [],
-      toolDescriptions,
-      cliEnabled
-    );
-  }
   if (startDeployWebsiteEnabled) {
     addStartDeployWebsiteTool(server2, disableTools || [], toolDescriptions, {
       skillsPortalUrl,
@@ -73891,6 +73832,13 @@ var addDocsTools = (server2, allowedTools = [
       commitHash: effectiveCommitHash
     });
   }
+  if (startHeadlessBuildEnabled) {
+    addStartHeadlessBuildTool(server2, disableTools || [], toolDescriptions, {
+      skillsPortalUrl,
+      repo: effectiveRepo,
+      commitHash: effectiveCommitHash
+    });
+  }
   if (allowedTools.includes("WDS") && !disableTools?.includes("SearchWixWDSDocumentation")) {
     server2.tool(
       "SearchWixWDSDocumentation",
@@ -74420,7 +74368,7 @@ var addDocsTools = (server2, allowedTools = [
             content: [
               {
                 type: "text",
-                text: `Invalid article URL: must start with https://dev.wix.com/docs/, or be a Wix skills page (https://www.wix.com/skills/...). Got: "${articleUrl}"`
+                text: `Invalid article URL: must start with https://dev.wix.com/docs/, or be a Wix skills page (https://www.wix.com/skills/..., https://www.wix.com/headless/...). Got: "${articleUrl}"`
               }
             ]
           };
@@ -85714,6 +85662,10 @@ var WixMcpServer = class extends McpServer {
   getSessionId() {
     return this.sessionId;
   }
+  /** The connected client's name: the host's getter (User-Agent fallback) first, then clientInfo. */
+  clientName() {
+    return this.getClientName?.() ?? this.server.getClientVersion()?.name;
+  }
   setClientNameGetter(getClientName) {
     this.getClientName = getClientName;
   }
@@ -86448,10 +86400,12 @@ function addApiCallTool(server2, strategy, allowedTools = ["CallWixSiteAPI", "Li
           sourceDocUrl: external_exports.string().describe(d.sourceDocUrl)
         };
       })(),
+      // openWorldHint true: a free-form URL into the whole Wix REST surface is an
+      // open-ended target, even though auth is bounded to the user's account.
       getHints("CallWixSiteAPI", {
         readOnlyHint: false,
         destructiveHint: true,
-        openWorldHint: false
+        openWorldHint: true
       }),
       async ({ url, body, method, siteId, reason, sourceDocUrl }, { httpClient, setToolBiParams }) => {
         logger2.log(
@@ -86628,7 +86582,7 @@ function addApiCallTool(server2, strategy, allowedTools = ["CallWixSiteAPI", "Li
       getHints("ManageWixSite", {
         readOnlyHint: false,
         destructiveHint: true,
-        openWorldHint: false
+        openWorldHint: true
       }),
       async ({ url, body, method, reason }, { httpClient, setToolBiParams }) => {
         logger2.log(
@@ -87641,7 +87595,8 @@ function addExecuteGraphqlTool(server2, description, authStrategy, options) {
       hasMutations: external_exports.boolean().describe(d.hasMutations),
       reason: external_exports.string().describe(d.reason)
     },
-    { readOnlyHint: false, destructiveHint: true, openWorldHint: false },
+    // openWorldHint true: any operation in the Wix GraphQL schema, chosen at call time.
+    { readOnlyHint: false, destructiveHint: true, openWorldHint: true },
     async ({ query, variables, operationName, siteId, scope, hasMutations, reason }, extra) => {
       const effectiveScope = scope ?? (siteId ? "site" : "account");
       logger2.log(
@@ -87741,6 +87696,7 @@ var EXPERIMENTAL_TOOLS = [
   "CLI_COMMAND",
   "GET_TO_KNOW_WIX",
   "CREATE_WIX_BUSINESS_GUIDE",
+  // accepted so old configs still start; the tool was removed
   "VELO_README",
   "WIX_API_THROUGH_FS",
   "GRAPHQL"
@@ -87811,18 +87767,12 @@ var docsTools = activeTools.filter(
 );
 var isWixCliAuth = Boolean(parsedArgs["wixCliAuth"]);
 var hasGetToKnowWix = activeTools.includes("GET_TO_KNOW_WIX") || isWixCliAuth;
-var hasCreateWixBusinessGuide = activeTools.includes(
-  "CREATE_WIX_BUSINESS_GUIDE"
-);
 var hasDynamicContext = Boolean(parsedArgs["dynamicContext"]) || isWixCliAuth;
-if (docsTools.length > 0 || hasGetToKnowWix || hasCreateWixBusinessGuide) {
+if (docsTools.length > 0 || hasGetToKnowWix) {
   logger2.log("Adding docs tools:", docsTools);
   addDocsTools(server, docsTools, {
     getToKnowWixEnabled: hasGetToKnowWix,
-    createWixBusinessGuideEnabled: hasCreateWixBusinessGuide,
-    dynamicContextEnabled: hasDynamicContext,
-    cliEnabled: true
-    // bin.ts is always a CLI client (e.g. Claude Code)
+    dynamicContextEnabled: hasDynamicContext
   });
 }
 if (activeTools.includes("VELO_README")) {