@wix/mcp 1.0.90 → 1.0.92

package/build/esm/toolkit.js

@@ -12124,7 +12124,7 @@ function buildSystemReminderGuidelines(includeReadme, includeImageUploadGuidance
       "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 DeployWebsite right away \u2014 not a site-creation tool, not the docs.",
+      "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."
     );
   }
@@ -12204,9 +12204,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 DeployWebsite, 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.
@@ -12598,7 +12600,7 @@ function buildToolDescriptions(includeReadme, includeImageUploadGuidance = true)
   `,
     "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 DeployWebsite instead; it returns the recipe to publish the files yourself.
+    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.
   `,
     RunWixCliCommand: dedent_default`
     Executes Wix CLI commands for Wix app development and management.
@@ -13030,14 +13032,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}
@@ -13080,9 +13082,9 @@ function buildToolDescriptions(includeReadme, includeImageUploadGuidance = true)
     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.
   `,
-    DeployWebsite: 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.
+    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.
+    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).
@@ -13090,7 +13092,7 @@ function buildToolDescriptions(includeReadme, includeImageUploadGuidance = true)
     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 DeployWebsite, 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.
+    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
 
@@ -14237,39 +14239,57 @@ ${articleContent}${nextSteps}`;
   );
 }
 
-// src/docs/deploy-website.ts
-var DEPLOY_WEBSITE_TOOL_NAME = "DeployWebsite";
-var DEPLOY_WEBSITE_RECIPE_URL = "https://dev.wix.com/docs/api-reference/account-level/sites/skills/upload-a-website-or-html-files.md";
+// 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.",
+  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";
 var FALLBACK_LINE = `Only if you cannot run it (you can't reach the file bytes, or a step fails and you can't fix it): send the user to ${DROP_PAGE_URL} \u2014 give that URL exactly as written, keeping the utm_campaign=mcp parameter.`;
-function deployWebsiteResponse(recipe) {
+function startDeployWebsiteResponse(recipe) {
   return [
-    `The following is the content of ${DEPLOY_WEBSITE_RECIPE_URL}. Follow it end to end and do the publishing yourself \u2014 do not hand the user instructions.`,
+    `The following is the content of ${START_DEPLOY_WEBSITE_RECIPE_URL}. Follow it end to end and do the publishing yourself \u2014 do not hand the user instructions.`,
     FALLBACK_LINE,
     "---",
     recipe.trim()
   ].join("\n\n");
 }
-var DEPLOY_WEBSITE_POINTER_RESPONSE = [
-  `Read and follow this recipe end to end: ${DEPLOY_WEBSITE_RECIPE_URL}`,
+var START_DEPLOY_WEBSITE_POINTER_RESPONSE = [
+  `Read and follow this recipe end to end: ${START_DEPLOY_WEBSITE_RECIPE_URL}`,
   "It covers creating the site and uploading the files (with or without a Wix login), updating a site deployed this way, and implementing a backend on it (stores, bookings, CMS, members) as a Wix Headless project. Do the publishing yourself \u2014 do not hand the user instructions.",
   FALLBACK_LINE
 ].join("\n\n");
-function addDeployWebsiteTool(server, disableTools = [], toolDescriptions, fetchOptions = {}) {
-  if (disableTools.includes(DEPLOY_WEBSITE_TOOL_NAME)) {
+function addStartDeployWebsiteTool(server, disableTools = [], toolDescriptions, fetchOptions = {}) {
+  if (disableTools.includes(START_DEPLOY_WEBSITE_TOOL_NAME)) {
     return;
   }
   server.tool(
-    DEPLOY_WEBSITE_TOOL_NAME,
-    toolDescriptions?.[DEPLOY_WEBSITE_TOOL_NAME] ?? defaultToolDescriptions[DEPLOY_WEBSITE_TOOL_NAME],
-    {},
+    START_DEPLOY_WEBSITE_TOOL_NAME,
+    toolDescriptions?.[START_DEPLOY_WEBSITE_TOOL_NAME] ?? defaultToolDescriptions[START_DEPLOY_WEBSITE_TOOL_NAME],
+    {
+      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 }) => {
-      let text = DEPLOY_WEBSITE_POINTER_RESPONSE;
+      let text = START_DEPLOY_WEBSITE_POINTER_RESPONSE;
       try {
         const recipe = await fetchArticleContent(
           httpClient,
-          DEPLOY_WEBSITE_RECIPE_URL.replace(/\.md$/, ""),
+          START_DEPLOY_WEBSITE_RECIPE_URL.replace(/\.md$/, ""),
           "article",
           true,
           fetchOptions.skillsPortalUrl,
@@ -14277,11 +14297,11 @@ function addDeployWebsiteTool(server, disableTools = [], toolDescriptions, fetch
           fetchOptions.commitHash
         );
         if (recipe && recipe.trim()) {
-          text = deployWebsiteResponse(recipe);
+          text = startDeployWebsiteResponse(recipe);
         }
       } catch (error) {
         console.warn(
-          `[DeployWebsite] recipe fetch failed, returning the pointer:`,
+          `[StartDeployWebsite] recipe fetch failed, returning the pointer:`,
           error instanceof Error ? error.message : error
         );
       }
@@ -14338,7 +14358,7 @@ var addDocsTools = (server, allowedTools = [
   const {
     getToKnowWixEnabled = false,
     createWixBusinessGuideEnabled = true,
-    deployWebsiteEnabled = true,
+    startDeployWebsiteEnabled = true,
     disableTools,
     toolDescriptions,
     readmeDocs,
@@ -14404,8 +14424,8 @@ var addDocsTools = (server, allowedTools = [
       cliEnabled
     );
   }
-  if (deployWebsiteEnabled) {
-    addDeployWebsiteTool(server, disableTools || [], toolDescriptions, {
+  if (startDeployWebsiteEnabled) {
+    addStartDeployWebsiteTool(server, disableTools || [], toolDescriptions, {
       skillsPortalUrl,
       repo: effectiveRepo,
       commitHash: effectiveCommitHash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/mcp",
-  "version": "1.0.90",
+  "version": "1.0.92",
   "description": "A Model Context Protocol server for Wix AI tools",
   "bin": "./build/bin-standalone.js",
   "dependencies": {
@@ -133,5 +133,5 @@
       ]
     }
   },
-  "falconPackageHash": "d562cd11d61654cd119a10a3385e83892fd93dcb6ed41d7d119bc2e4"
+  "falconPackageHash": "54656e5ebcb80096bd722cc5f9776c97996d45e5c6701b4288e04af9"
 }

package/build/dts/docs/deploy-website.d.ts

@@ -1,13 +0,0 @@
-import { WixMcpServer } from '../wix-mcp-server.js';
-export declare const DEPLOY_WEBSITE_TOOL_NAME = "DeployWebsite";
-export declare const DEPLOY_WEBSITE_RECIPE_URL = "https://dev.wix.com/docs/api-reference/account-level/sites/skills/upload-a-website-or-html-files.md";
-export declare const DROP_PAGE_URL = "https://www.wix.com/headless/drop?utm_campaign=mcp";
-export declare function deployWebsiteResponse(recipe: string): string;
-export declare const DEPLOY_WEBSITE_POINTER_RESPONSE: string;
-export interface DeployWebsiteFetchOptions {
-    skillsPortalUrl?: string;
-    repo?: string;
-    commitHash?: string;
-}
-export declare function addDeployWebsiteTool(server: WixMcpServer, disableTools?: string[], toolDescriptions?: Record<string, string>, fetchOptions?: DeployWebsiteFetchOptions): void;
-//# sourceMappingURL=deploy-website.d.ts.map

package/build/dts/docs/deploy-website.js

@@ -1,45 +0,0 @@
-import { defaultToolDescriptions } from '../config/default-config.js';
-import { fetchArticleContent } from './fetch-article.js';
-export const DEPLOY_WEBSITE_TOOL_NAME = 'DeployWebsite';
-export const DEPLOY_WEBSITE_RECIPE_URL = 'https://dev.wix.com/docs/api-reference/account-level/sites/skills/upload-a-website-or-html-files.md';
-export const DROP_PAGE_URL = 'https://www.wix.com/headless/drop?utm_campaign=mcp';
-const FALLBACK_LINE = `Only if you cannot run it (you can't reach the file bytes, or a step fails and you can't fix it): send the user to ${DROP_PAGE_URL} — give that URL exactly as written, keeping the utm_campaign=mcp parameter.`;
-// The tool exists to take the agent's attention at routing time; the work itself
-// is the recipe, so the response IS the recipe — fetched live and returned whole,
-// so the agent never has to decide whether to go read it.
-export function deployWebsiteResponse(recipe) {
-    return [
-        `The following is the content of ${DEPLOY_WEBSITE_RECIPE_URL}. Follow it end to end and do the publishing yourself — do not hand the user instructions.`,
-        FALLBACK_LINE,
-        '---',
-        recipe.trim()
-    ].join('\n\n');
-}
-// When the recipe can't be fetched, the pointer still routes correctly.
-export const DEPLOY_WEBSITE_POINTER_RESPONSE = [
-    `Read and follow this recipe end to end: ${DEPLOY_WEBSITE_RECIPE_URL}`,
-    'It covers creating the site and uploading the files (with or without a Wix login), updating a site deployed this way, and implementing a backend on it (stores, bookings, CMS, members) as a Wix Headless project. Do the publishing yourself — do not hand the user instructions.',
-    FALLBACK_LINE
-].join('\n\n');
-export function addDeployWebsiteTool(server, disableTools = [], toolDescriptions, fetchOptions = {}) {
-    if (disableTools.includes(DEPLOY_WEBSITE_TOOL_NAME)) {
-        return;
-    }
-    server.tool(DEPLOY_WEBSITE_TOOL_NAME, toolDescriptions?.[DEPLOY_WEBSITE_TOOL_NAME] ??
-        defaultToolDescriptions[DEPLOY_WEBSITE_TOOL_NAME], {}, { readOnlyHint: true, destructiveHint: false, openWorldHint: false }, async (_args, { httpClient }) => {
-        let text = DEPLOY_WEBSITE_POINTER_RESPONSE;
-        try {
-            // Same path ReadFullDocsArticle takes for this page: the rawdocs article
-            // API, addressed without the .md suffix, header scaffolding stripped.
-            const recipe = await fetchArticleContent(httpClient, DEPLOY_WEBSITE_RECIPE_URL.replace(/\.md$/, ''), 'article', true, fetchOptions.skillsPortalUrl, fetchOptions.repo, fetchOptions.commitHash);
-            if (recipe && recipe.trim()) {
-                text = deployWebsiteResponse(recipe);
-            }
-        }
-        catch (error) {
-            console.warn(`[DeployWebsite] recipe fetch failed, returning the pointer:`, error instanceof Error ? error.message : error);
-        }
-        return { content: [{ type: 'text', text }] };
-    });
-}
-//# sourceMappingURL=deploy-website.js.map