@wix/mcp 1.0.91 → 1.0.93

package/build/bin-standalone.js

@@ -71098,9 +71098,12 @@ var runSemanticSearch = async (toolName, toolParams, maxResults = 20, rerank = f
   );
   return data?.results;
 };
-var runPlatformizedSemanticSearch = async (toolName, searchTerm, maxResults = 20, linesInEachResult) => {
+var runPlatformizedSemanticSearch = async (toolName, searchTerm, maxResults = 20, linesInEachResult, extraDocumentTypes) => {
   const startTime = Date.now();
-  logger2.log(`[SemanticSearch/v2] Tool: ${toolName}, Query: "${searchTerm}"`);
+  const documentTypes = extraDocumentTypes?.length ? [toolName, ...extraDocumentTypes] : void 0;
+  logger2.log(
+    `[SemanticSearch/v2] Tool: ${documentTypes ? documentTypes.join("+") : toolName}, Query: "${searchTerm}"`
+  );
   const response = await fetch(
     "https://www.wixapis.com/mcp-docs-search/v1/docs/search/markdown",
     {
@@ -71111,7 +71114,7 @@ var runPlatformizedSemanticSearch = async (toolName, searchTerm, maxResults = 20
       },
       body: JSON.stringify({
         search_term: searchTerm,
-        document_type: toolName,
+        ...documentTypes ? { document_types: documentTypes } : { document_type: toolName },
         maximum_results: maxResults,
         lines_in_each_result: linesInEachResult
       })
@@ -71140,14 +71143,16 @@ var runSemanticSearchAndFormat = async ({
   maxResults = DEFAULT_MAX_RESULTS,
   rerank,
   linesInEachResult,
-  usePlatformizedSearch = true
+  usePlatformizedSearch = true,
+  extraDocumentTypes
 }) => {
   if (usePlatformizedSearch) {
     return runPlatformizedSemanticSearch(
       toolName,
       toolParams.searchTerm,
       maxResults,
-      linesInEachResult
+      linesInEachResult,
+      extraDocumentTypes
     );
   } else {
     const results = await runSemanticSearch(
@@ -71679,9 +71684,11 @@ var SITE_CREATION_COPY = {
   }
 };
 var SITE_GUIDANCE = dedent_default`
-  A new-site request has 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.
+  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.
 
-  One case skips all of this: a finished page or site ALREADY EXISTS, in any form — hand-written HTML/CSS/JS, a static build, a zip, another AI builder's export, or a page you made earlier in this conversation. There is nothing to build, so don't offer AI or templates and don't call any site-creation tool: call StartDeployWebsite, which returns the recipe to publish the files yourself (the drop page is only its fallback).
+  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.
 
   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.
@@ -71778,13 +71785,14 @@ var ACCOUNT_SITE_EXECUTE_SCOPE = dedent_default`
     unzip(input: string | Uint8Array): Promise<Array<{ path: string; bytes: Uint8Array; text(): string }>>;
   };
   declare const siteId: string | undefined;
-  // Files from the ExecuteWixAPI \`files\` param. Text entries have \`content\`;
-  // an entry tagged \`=== FILE: <path> base64 ===\` has encoding:'base64' and
-  // base64 \`content\` (a binary file — image, font).
+  // Files from the ExecuteWixAPI \`files\` param, followed by the resolved
+  // \`attachments\`. Text entries have \`content\`; an entry tagged
+  // \`=== FILE: <path> base64 ===\` — and every attachment, path = its file name —
+  // has encoding:'base64' and base64 \`content\`.
   declare const files: Array<{ path: string; content: string; encoding?: "base64" }>;
   \`\`\`
 
-  FILE UPLOADS: put every file in the \`files\` param (never inline in \`code\`). 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\` 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):
   \`\`\`javascript
   // files param:
   //   === FILE: index.html ===
@@ -71799,6 +71807,12 @@ var ACCOUNT_SITE_EXECUTE_SCOPE = dedent_default`
     return res.data;
   }
   \`\`\`
+  A site zip passed through \`attachments\` is one base64 entry; unzip it and upload the entries:
+  \`\`\`javascript
+  // attachments: [site.zip] → files = [{ path: "site.zip", content: "<base64>", encoding: "base64" }]
+  const entries = await wix.unzip(files[0].content); // [{ path, bytes, text() }]
+  const mp = wix.multipart(entries);
+  \`\`\`
   DOWNLOAD + EDIT + RE-UPLOAD: fetch the zip as base64, \`wix.unzip()\` it, edit text via \`entry.text()\`, keep binary as bytes, and hand the entries back to \`wix.multipart()\`:
   \`\`\`javascript
   const r = await wix.request({ scope: "account", method: "GET", responseType: "base64", url: zipUrl });
@@ -72003,12 +72017,12 @@ function buildToolDescriptions(includeReadme, includeImageUploadGuidance = true)
     NEVER call this tool with a missing, empty, or guessed siteId — ask first instead.
 
     Parameters — provide image input via image and/or imageUrls, OR imageBase64:
-    • image (array): chat file ATTACHMENTS. Each item is an object with download_url and file_id (both required), plus optional file_name and mime_type. Pass ALL attachments in one call.
+    • image (array): chat file ATTACHMENTS — files the user attached, or files you created in your own file sandbox. Each item is an object with download_url and file_id (both required), plus optional file_name and mime_type. Pass ALL attachments in one call.
     • imageUrls (array): plain public image URLs the user pasted or other tools produced (no file_id). Pass ALL URLs in one call. Can be combined with image.
     • imageBase64 (string): base64-encoded image + mimeType. One image at a time. Do NOT combine with image/imageUrls.
 
     Delivering the bytes — this is where uploads most often fail:
-    • NEVER pass a local or sandbox file path (e.g. /mnt/..., /home/user/..., /Users/...) in any field — the server cannot reach your filesystem. Use a public http(s) URL (imageUrls) or the complete base64 (imageBase64).
+    • Pass a file as a file, in image: the platform resolves it into download_url and file_id before it reaches this tool — this includes files you created in your sandbox. This server does not share your filesystem, so a bare path string (e.g. /mnt/..., /home/user/..., /Users/...) is not a file. Without a file to pass, use a public http(s) URL (imageUrls) or the complete base64 (imageBase64).
     • imageBase64 must be the WHOLE file, not truncated. For large images prefer imageUrls, since long base64 is easily cut off and will be rejected as unreadable.
   `,
     SupportAndFeedback: dedent_default`
@@ -72505,14 +72519,14 @@ function buildToolDescriptions(includeReadme, includeImageUploadGuidance = true)
     WixSiteBuilder: dedent_default`
     ${SITE_GUIDANCE}
 
-    Tool for generating a Wix site with AI (creating / building a site in Wix Harmony).
+    Tool for generating a Wix site with AI (creating / building a site in Wix Harmony) from a description. It does not take pages or files you already have — those go to StartDeployWebsite.
 
     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\`.
 
-    Do NOT suggest HTML code, prompt templates, or alternative approaches — actually build the site through this tool.
+    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}
@@ -72556,8 +72570,8 @@ function buildToolDescriptions(includeReadme, includeImageUploadGuidance = true)
     Set \`hasMutations: true\` for any document containing a mutation root field.
   `,
     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: 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, or upload my site / index.html.
-    Also for updating a site deployed this way (replace its files; same site, same URL) and for implementing a backend on one (stores, bookings, CMS, members) 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.
+    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.
+    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).
@@ -73222,7 +73236,7 @@ var paramDescriptions = {
   },
   SearchWixRESTDocumentation: {
     searchTerm: `The search term to look up in the Wix REST API Documentation \u2014 a natural-language description of the endpoint, resource, or action you need across any Wix domain (Stores, eCommerce, Bookings, CRM, Members, CMS, Events, Blog, Forms, Media, site settings, etc.), e.g. "create a catalog item with inventory", "book a service", "update data collection items". Match the wording to how many entities you will act on: a plural term ("update products") surfaces the resource's bulk methods, which a singular term ("update a product") ranks lower or leaves out. Results are ranked by relevance, so describe the goal rather than guessing an exact API name.`,
-    maxResults: "The maximum number of results to return, default is 10, max is 15",
+    maxResults: "The maximum number of results to return (1\u201317, default 17). Results mix REST API documentation with matching recipes and skills.",
     reason: "One sentence describing the original user request and the task you are trying to accomplish with this search."
   },
   WixBusinessFlowsDocumentation: {
@@ -73243,7 +73257,7 @@ var paramDescriptions = {
   },
   SearchWixHeadlessDocumentation: {
     searchTerm: "The search term to search for in the Headless Documentation",
-    maxResults: "The maximum number of results to return, default is 10, max is 15"
+    maxResults: "The maximum number of results to return (1\u201317, default 17). Results mix Headless documentation with matching recipes and skills."
   },
   SearchWixVeloDocumentation: {
     searchTerm: "The search term to search for in the Velo Documentation",
@@ -73271,7 +73285,7 @@ var paramDescriptions = {
   },
   UploadImageToWixSite: {
     siteId: "The ID (UUID) of the Wix site to upload to. REQUIRED. If the user has not clearly specified which site, ASK them which site to upload to (or use ListWixSites to help them pick) BEFORE calling this tool. NEVER call this tool with a missing, empty, placeholder, or guessed siteId \u2014 ask first instead.",
-    image: "Array of file ATTACHMENTS the user uploaded in the chat. Each item requires download_url and file_id, and may optionally include file_name and mime_type \u2014 attached files are automatically resolved to these fields by the platform, so just include them here. For plain image URLs the user pasted, use imageUrls instead. ALWAYS pass ALL attachments together in a single call \u2014 NEVER call this tool once per image. Do NOT use together with imageBase64.",
+    image: "Array of file ATTACHMENTS: files the user uploaded in the chat, or files you created in your own file sandbox. Each item requires download_url and file_id, and may optionally include file_name and mime_type \u2014 the platform resolves a file passed here into these fields automatically, so just include the files. For plain image URLs the user pasted, use imageUrls instead. ALWAYS pass ALL attachments together in a single call \u2014 NEVER call this tool once per image. Do NOT use together with imageBase64.",
     imageUrls: "Array of publicly accessible image URLs (e.g. links the user pasted or URLs produced by other tools). Use this for plain URLs that are NOT chat attachments \u2014 no file_id is needed. ALWAYS pass ALL URLs together in a single call. Can be combined with image; do NOT use together with imageBase64.",
     imageBase64: 'Base64-encoded image data. Use when the client can read a file and encode it as base64. May include a data URL prefix (e.g. "data:image/jpeg;base64,...") or be raw base64. Do NOT use together with image.',
     mimeType: 'MIME type of the image (e.g. "image/jpeg", "image/png", "image/webp"). Required when imageBase64 does not include a data URL prefix.',
@@ -73675,7 +73689,17 @@ ${articleContent}${nextSteps}`;
 }
 
 // src/docs/start-deploy-website.ts
-var START_DEPLOY_WEBSITE_BRIEF_DESCRIPTION = "A few sentences covering: the user's request (quoted if short); what the site is \u2014 its purpose and who it is for \u2014 and its current form (HTML/CSS/JS files, a static build, a zip, another builder's export, a design created in this conversation), roughly how many files, and whether it includes images; what the site must be able to do for its visitors beyond showing pages, if anything \u2014 selling, bookings or reservations, tickets, menus and orders, rentals, forms, memberships or paid plans, donations, a blog, or anything else the user expects to work \u2014 described in your own words, or a note that it is a plain static site with no such needs; which agent or product you are and the harness you run in.";
+var START_DEPLOY_WEBSITE_PARAM_DESCRIPTIONS = {
+  userRequest: "The user's request that led here, quoted if short, otherwise summarized in a sentence.",
+  siteDescription: "What the site is: its purpose and who it is for. One or two sentences.",
+  siteForm: "The form the site exists in right now (HTML/CSS/JS files, a static build, a zip, another builder's export, a design created in this conversation, or something else), roughly how many files, and whether it includes images.",
+  siteFunctionality: "What the site must be able to do for its visitors beyond showing pages, if anything (for example selling, bookings or reservations, tickets, menus and orders, rentals, forms, memberships or paid plans, donations, a blog, or anything else the user expects to work), in your own words. If it is a plain static site with no such needs, say so.",
+  agentIdentity: "Which agent or product you are and the harness you run in.",
+  wixAccess: "How you can reach Wix from where you run: through this MCP only, or also from a shell whose network can reach wixapis.com; whether you can run the Wix CLI (npx @wix/cli) there and whether it is logged in; and which Wix identity you act with \u2014 the user's login through this MCP, a CLI login, or none."
+};
+var START_DEPLOY_WEBSITE_PARAMS = Object.keys(
+  START_DEPLOY_WEBSITE_PARAM_DESCRIPTIONS
+);
 var START_DEPLOY_WEBSITE_TOOL_NAME = "StartDeployWebsite";
 var START_DEPLOY_WEBSITE_RECIPE_URL = "https://dev.wix.com/docs/api-reference/account-level/sites/skills/upload-a-website-or-html-files.md";
 var DROP_PAGE_URL = "https://www.wix.com/headless/drop?utm_campaign=mcp";
@@ -73701,7 +73725,12 @@ function addStartDeployWebsiteTool(server2, disableTools = [], toolDescriptions,
     START_DEPLOY_WEBSITE_TOOL_NAME,
     toolDescriptions?.[START_DEPLOY_WEBSITE_TOOL_NAME] ?? defaultToolDescriptions[START_DEPLOY_WEBSITE_TOOL_NAME],
     {
-      brief: external_exports.string().min(1).describe(START_DEPLOY_WEBSITE_BRIEF_DESCRIPTION)
+      userRequest: external_exports.string().min(1).describe(START_DEPLOY_WEBSITE_PARAM_DESCRIPTIONS.userRequest),
+      siteDescription: external_exports.string().min(1).describe(START_DEPLOY_WEBSITE_PARAM_DESCRIPTIONS.siteDescription),
+      siteForm: external_exports.string().min(1).describe(START_DEPLOY_WEBSITE_PARAM_DESCRIPTIONS.siteForm),
+      siteFunctionality: external_exports.string().min(1).describe(START_DEPLOY_WEBSITE_PARAM_DESCRIPTIONS.siteFunctionality),
+      agentIdentity: external_exports.string().min(1).describe(START_DEPLOY_WEBSITE_PARAM_DESCRIPTIONS.agentIdentity),
+      wixAccess: external_exports.string().min(1).describe(START_DEPLOY_WEBSITE_PARAM_DESCRIPTIONS.wixAccess)
     },
     { readOnlyHint: true, destructiveHint: false, openWorldHint: false },
     async (_args, { httpClient }) => {
@@ -73926,7 +73955,7 @@ var addDocsTools = (server2, allowedTools = [
         const d = desc("SearchWixRESTDocumentation");
         return {
           searchTerm: external_exports.string().describe(d.searchTerm),
-          maxResults: external_exports.number().describe(d.maxResults).min(1).max(15).optional().default(15),
+          maxResults: external_exports.number().describe(d.maxResults).min(1).max(17).optional().default(17),
           reason: external_exports.string().describe(d.reason)
         };
       })(),
@@ -73941,9 +73970,12 @@ var addDocsTools = (server2, allowedTools = [
             toolParams: {
               searchTerm
             },
-            maxResults: Math.max(1, Math.min(maxResults ?? 15, 15)),
+            maxResults: Math.max(1, Math.min(maxResults ?? 17, 17)),
             linesInEachResult: 30,
-            usePlatformizedSearch
+            usePlatformizedSearch,
+            // Merge recipes/skills into the REST ranking — they live in a
+            // separate corpus the REST document_type doesn't cover on its own.
+            extraDocumentTypes: ["SKILLS"]
           });
           const grounding = result.includes(QUERY_CAPABILITY_MARKER) ? [
             REST_SEARCH_API_GROUNDING_REMINDER,
@@ -74206,7 +74238,7 @@ var addDocsTools = (server2, allowedTools = [
         const d = desc("SearchWixHeadlessDocumentation");
         return {
           searchTerm: external_exports.string().describe(d.searchTerm),
-          maxResults: external_exports.number().describe(d.maxResults).min(1).max(15).optional().default(15)
+          maxResults: external_exports.number().describe(d.maxResults).min(1).max(17).optional().default(17)
         };
       })(),
       { readOnlyHint: true, destructiveHint: false, openWorldHint: false },
@@ -74218,8 +74250,11 @@ var addDocsTools = (server2, allowedTools = [
             toolParams: {
               searchTerm
             },
-            maxResults: Math.max(1, Math.min(maxResults ?? 15, 15)),
-            usePlatformizedSearch
+            maxResults: Math.max(1, Math.min(maxResults ?? 17, 17)),
+            usePlatformizedSearch,
+            // Merge recipes/skills into the headless ranking — same separate
+            // corpus the WIX_HEADLESS document_type doesn't cover on its own.
+            extraDocumentTypes: ["SKILLS"]
           });
           return {
             content: [