developer-tools Static interface comparison

Wix MCP

1.0.98 1.0.99

PASSAutomated static analysis

No policy-significant interface change detected.

View the upgrade review as Markdown

A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.

Tools15 → 15
Added0
Removed0
Schema changes0
Input schema changes0
Output schema changes0
Unclassified schema changes0
Description changes4
New write authority0
New destructive authority0
New unknown authority0
AnalysisPASS

INTERFACE DIFF

What changed, tool by tool

Classification from the recorded findings · definitions from the published snapshots

4 tools with recorded changes

  1. CheckDomainAvailabilityModifiedDescriptionINFO

    What changed

    • CheckDomainAvailability: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousChecks whether one or more domain names can be registered through Wix. Call this when the user asks if a specific domain is available, e.g. "is mybakery.com available?" or "check these: a.com, b.net". Pass every name in one call; do not call it once per name. Do not use this tool to come up with domain ideas or alternatives: call GetSuggestedDomains for that. Returns one `{ domain, status }` per name, in the order given. Answer in plain language, one line per domain, in that order: - AVAILABLE: it is available. - PREMIUM: it is available as a premium domain, which costs more than a standard one. - REGISTERED: it is already registered. - UNSUPPORTED_TLD: Wix doesn't support its extension, e.g. ".ws domains aren't supported by Wix". - UNABLE_TO_CHECK: you couldn't check it. Then ask one question that offers only the actions for the statuses present: - AVAILABLE or PREMIUM: get an available name for their Wix site. - REGISTERED: connect it to their Wix site if it's theirs, or see similar names. - UNSUPPORTED_TLD: try a supported extension. - UNABLE_TO_CHECK: retry the names you couldn't check. Say that a domain is premium only when its status is PREMIUM. Never state or estimate a price. Never name an error, a code or an API to the user. This tool only checks availability. It does not purchase or connect a domain, look up an owner or search for names: act on those only after the user answers your question.
    CurrentChecks whether one or more domain names can be registered through Wix. Call this only when the user asks if a specific domain is available, e.g. "is mybakery.com available?" or "check these: a.com, b.net". Pass every name in one call; do not call it once per name. This tool only checks availability. Do not use this tool when user's intent is to purchase or connect a domain. Do not use this tool to come up with domain ideas or alternatives: call GetSuggestedDomains for that. Returns one `{ domain, status }` per name, in the order given. Answer in plain language, one line per domain, in that order: - AVAILABLE: it is available. - PREMIUM: it is available as a premium domain, which costs more than a standard one. - REGISTERED: it is already registered. - UNSUPPORTED_TLD: Wix doesn't support its extension, e.g. ".ws domains aren't supported by Wix". - UNABLE_TO_CHECK: you couldn't check it. Then ask one question that offers only the actions for the statuses present: - AVAILABLE or PREMIUM: get an available name for their Wix site. - REGISTERED: connect it to their Wix site if it's theirs, or see similar names. - UNSUPPORTED_TLD: try a supported extension. - UNABLE_TO_CHECK: retry the names you couldn't check. Say that a domain is premium only when its status is PREMIUM. Never state or estimate a price. Never name an error, a code or an API to the user.

    Input schema

    Input schema unchanged.

    3 unchanged entries
    • (schema root)
    • domains
    • domains › [items]

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  2. StartDeployWebsiteModifiedDescriptionINFO

    What changed

    • StartDeployWebsite: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousCreates a website on Wix and puts it live, or replaces the files of one deployed earlier. You write the site's code, or take the files the user brought (HTML/CSS/JS, a static build, a zip, another builder's export), and this returns the guide to create the site and upload them. Updates keep the same site and URL. Works with or without a Wix login (anonymous deploy with a save link), through the Wix MCP alone or from a shell. Call it right away, without asking the user anything first. When a new site needs Wix business features (a store, bookings or appointments, rentals, events and tickets, a restaurant menu with online orders or reservations, a blog, a portfolio, pricing plans and memberships, donations, Wix Forms, members and login, a CMS, payments), call StartHeadlessBuild instead. When the user brought files and the site needs those features, upload the files here first; the upload's result then points to StartHeadlessBuild to connect them. Returns the guide; follow it and do the work yourself. Upload with UploadHeadlessWebsiteFiles once the site exists; the drop page is only the fallback. NOT for: a user who asked for Wix's editor, the Wix Harmony Editor, a template, Wix Studio or the Classic Editor (WixHarmonyEditorBuild, SearchSiteTemplates); 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 editor site; uploading images or documents to a site's media (UploadImageToWixSite).
    CurrentCreates a website on Wix and puts it live, or replaces the files of one deployed earlier. You write the site's code, or take the files the user brought (HTML/CSS/JS, a static build, a zip, another builder's export), and this returns the guide to create the site and upload them. Updates keep the same site and URL. Works with or without a Wix login (anonymous deploy with a save link), through the Wix MCP alone or from a shell. Call it right away, without asking the user anything first. When a new site needs Wix business features (a store, bookings or appointments, rentals, events and tickets, a restaurant menu with online orders or reservations, a blog, a portfolio, pricing plans and memberships, donations, Wix Forms, members and login, a CMS, payments), call StartHeadlessBuild instead. When the user brought files and the site needs those features, upload the files here first; the upload's result then points to StartHeadlessBuild to connect them. Returns the guide; follow it and do the work yourself. Upload with UploadHeadlessWebsiteFiles once the site exists; the drop page is only the fallback. NOT for: a user who asked for Wix's editor, the Wix Harmony Editor, a template, Wix Studio or the Classic Editor (WixHarmonyEditorBuild, SearchSiteTemplates); a Studio Two (Studio 2) site, which is not Wix Studio (StartStudioTwoSite); 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 editor site; uploading images or documents to a site's media (UploadImageToWixSite).

    Input schema

    Input schema unchanged.

    7 unchanged entries
    • (schema root)
    • agentIdentity
    • siteDescription
    • siteForm
    • siteFunctionality
    • userRequest
    • wixAccess

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  3. StartHeadlessBuildModifiedDescriptionINFO

    What changed

    • StartHeadlessBuild: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousReturns Wix's headless guide, for a site that needs Wix business features (a store, bookings or appointments, rentals, events and tickets, a restaurant menu with online orders or reservations, a blog, a portfolio, pricing plans and memberships, donations, Wix Forms, members and login, a CMS, payments), run by Wix as a Wix Headless site. You write the site; the guide creates it, connects the features, and uploads it. Also to add those features to an existing Wix Headless site (one deployed from files is one), from a project download link, or to move a Wix site to code. Call it right away: it only returns the guide, and the site's details are not needed first. NOT for: a site that needs no Wix business feature, or files the user brought that are not live yet (StartDeployWebsite: upload them first, then come back here for the features); a user who asked for Wix's editor, the Wix Harmony Editor, a template, Wix Studio or the Classic Editor, even when the site needs business features (WixHarmonyEditorBuild, SearchSiteTemplates); a Claude Design URL (import-claude-design-from-url).
    CurrentReturns Wix's headless guide, for a site that needs Wix business features (a store, bookings or appointments, rentals, events and tickets, a restaurant menu with online orders or reservations, a blog, a portfolio, pricing plans and memberships, donations, Wix Forms, members and login, a CMS, payments), run by Wix as a Wix Headless site. You write the site; the guide creates it, connects the features, and uploads it. Also to add those features to an existing Wix Headless site (one deployed from files is one), from a project download link, or to move a Wix site to code. Call it right away: it only returns the guide, and the site's details are not needed first. NOT for: a site that needs no Wix business feature, or files the user brought that are not live yet (StartDeployWebsite: upload them first, then come back here for the features); a user who asked for Wix's editor, the Wix Harmony Editor, a template, Wix Studio or the Classic Editor, even when the site needs business features (WixHarmonyEditorBuild, SearchSiteTemplates); a Studio Two (Studio 2) site, which is not Wix Studio (StartStudioTwoSite); a Claude Design URL (import-claude-design-from-url).

    Input schema

    Input schema unchanged.

    7 unchanged entries
    • (schema root)
    • agentIdentity
    • siteDescription
    • siteFunctionality
    • startingPoint
    • userRequest
    • wixAccess

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  4. WixREADMEModifiedDescriptionINFO

    What changed

    • WixREADME: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    Previous# Tool: WixREADME The context every other Wix tool assumes. Call it first, once per conversation, for any Wix task or question; for another site later in the conversation, call `GetSiteContext` instead of calling this again. A Wix task includes reading or changing a site's or account's data: products, inventory, carts, checkouts, orders, bookings, services, staff, time slots, rentals, restaurant menus, online orders, reservations, events, tickets, RSVPs, blog posts, CMS collections and items, pricing plans, subscriptions, portfolios, gift cards, coupons, donations, forms, form submissions, contacts, members, loyalty points, groups, reviews, inbox messages, CRM tasks, automations, email campaigns, payments, invoices, SEO, redirects, translations, locations, analytics, media files, site properties, installed apps, and the account's sites and domains (searching whether a domain is available, buying one, and connecting one bought elsewhere). These requests skip it and go straight to their own tool: - **Creating a new site.** Skip the docs too. A site is written in code and uploaded: StartDeployWebsite returns the upload guide; StartHeadlessBuild returns the headless guide, for a site that needs Wix business features (a store, bookings or appointments, rentals, events and tickets, a restaurant menu with online orders or reservations, a blog, a portfolio, pricing plans and memberships, donations, Wix Forms, members and login, a CMS, payments). Call one right away, without asking the user anything first: StartHeadlessBuild when the site needs Wix business features, otherwise StartDeployWebsite. WixHarmonyEditorBuild or SearchSiteTemplates only when the user asked for Wix's editor, the Wix Harmony Editor, a template, Wix Studio or the Classic Editor. Never create a site through ManageWixSite, CallWixSiteAPI or ExecuteWixAPI. - **Suggesting domain names**: call GetSuggestedDomains directly, with the business or site name as the query. - **Listing, showing or finding their Wix sites**: call ListWixSites directly. - **Uploading local or attached image files to a Wix site**: call UploadImageToWixSite directly, with no docs, schema or API calls. Do NOT use ExecuteWixAPI, SearchWixAPISpec, or any Media Manager REST API for image uploads. A question about one of those goes to the same tool ("can you show my sites?" is ListWixSites). Any other Wix question is answered from a Wix skill or the docs, never from memory, and never with a reply that you lack the tools to answer. It returns, in full: - **Source of truth**: nothing Wix-specific from memory. Every URL, ID, setting location, product fact, request shape and field name comes from the docs tools, a Wix skill, an earlier tool result in the conversation, or the user. - **The site**: the account's sites with their properties and installed apps. The `siteId` comes from there (ask when several fit); a business solution's API works only on a site with its app installed, and an app's version changes its endpoints. - **Find the method**: an earlier tool result, else a Wix skill's recipe (wix-manage to manage a site, wix-headless-kit to build a headless one), else the docs: SearchWixRESTDocumentation or BrowseWixRESTDocsMenu, then ReadFullDocsArticle; the SDK, CLI, headless and apps docs for code. - **The exact shape**: model a call only on an example that matches the case; fill the rest with SearchWixAPISpec on the method's docs URL (request and response schemas, `method.publicUrl` for REST, `method.sdk` for the JavaScript SDK). A query's filter and sort fields and operators are a closed list per method. - **The call, or the code**: ExecuteWixAPI runs one async function holding every step code can resolve, the reads and the writes they feed together. Code the user keeps (an app, a headless site, a script over REST or the JavaScript SDK) is written from the same shapes; the headless skills are a shortcut on that path. - **When a call fails**: the error says what was wrong and carries a Wix request id; fix that, never resend unchanged or guess. - **Wix skills**, what each is for and how to read one: from disk when installed (the Wix plugin, or `npx skills add wix/skills`, `--skill <name>` for one, `-g` for the user's home, into `.agents/skills/<skill>/` or a similar folder the client reads, such as `.claude/skills/<skill>/`), else online with ReadFullDocsArticle at `https://www.wix.com/skills/<skill>/<path>`. - **wix-manage**: REST recipes for managing a site's business solutions, one per task; follow the recipe and make its calls with ExecuteWixAPI, its docs URL in `sourceDocUrls`. Its list of recipes is `SKILL.md` in the installed skill, or online https://dev.wix.com/docs/api-reference/articles/ai-tools/wix-mcp/skills/wix-management-recipes-index.md, and each API area has its own `<API section>/skills.md` (for example https://dev.wix.com/docs/api-reference/business-solutions/bookings/skills.md). - **wix-headless-kit**: builds a Wix Headless site on shipped, verified code from wix-headless-templates, a `@wix/sdk` React core or the same data layer as plain REST calls: scaffold with the CLI, deploy, seed, design on the shipped hooks, release. https://www.wix.com/skills/headless-kit/SKILL.md - **wix-headless-templates**: the code wix-headless-kit builds from, one folder per Wix Business Solution. https://www.wix.com/skills/headless-templates/ When the user asks you to do something in Wix, do it yourself, in as few steps and questions as you can; don't tell them which docs to read or which API to call.
    Current# Tool: WixREADME The context every other Wix tool assumes. Call it first, once per conversation, for any Wix task or question; for another site later in the conversation, call `GetSiteContext` instead of calling this again. A Wix task includes reading or changing a site's or account's data: products, inventory, carts, checkouts, orders, bookings, services, staff, time slots, rentals, restaurant menus, online orders, reservations, events, tickets, RSVPs, blog posts, CMS collections and items, pricing plans, subscriptions, portfolios, gift cards, coupons, donations, forms, form submissions, contacts, members, loyalty points, groups, reviews, inbox messages, CRM tasks, automations, email campaigns, payments, invoices, SEO, redirects, translations, locations, analytics, media files, site properties, installed apps, and the account's sites and domains (searching whether a domain is available, buying one, and connecting one bought elsewhere). These requests skip it and go straight to their own tool: - **Creating a new site.** Skip the docs too. A site is written in code and uploaded: StartDeployWebsite returns the upload guide; StartHeadlessBuild returns the headless guide, for a site that needs Wix business features (a store, bookings or appointments, rentals, events and tickets, a restaurant menu with online orders or reservations, a blog, a portfolio, pricing plans and memberships, donations, Wix Forms, members and login, a CMS, payments). Call one right away, without asking the user anything first: StartHeadlessBuild when the site needs Wix business features, otherwise StartDeployWebsite. A Studio Two (Studio 2) site, new or existing (to build, change, export or import it): StartStudioTwoSite. WixHarmonyEditorBuild or SearchSiteTemplates only when the user asked for Wix's editor, the Wix Harmony Editor, a template, Wix Studio or the Classic Editor. Never create a site through ManageWixSite, CallWixSiteAPI or ExecuteWixAPI. - **Suggesting domain names**: call GetSuggestedDomains directly, with the business or site name as the query. - **Listing, showing or finding their Wix sites**: call ListWixSites directly. - **Uploading local or attached files (images, videos, audio, documents) to a Wix site**: call UploadImageToWixSite directly, with no docs, schema or API calls. Do NOT use ExecuteWixAPI, SearchWixAPISpec, or any Media Manager REST API for these uploads. A question about one of those goes to the same tool ("can you show my sites?" is ListWixSites). Any other Wix question is answered from a Wix skill or the docs, never from memory, and never with a reply that you lack the tools to answer. It returns, in full: - **Source of truth**: nothing Wix-specific from memory. Every URL, ID, setting location, product fact, request shape and field name comes from the docs tools, a Wix skill, an earlier tool result in the conversation, or the user. - **The site**: the account's sites with their properties and installed apps. The `siteId` comes from there (ask when several fit); a business solution's API works only on a site with its app installed, and an app's version changes its endpoints. - **Find the method**: an earlier tool result, else a Wix skill's recipe (wix-manage to manage a site, wix-headless-kit to build a headless one), else the docs: SearchWixRESTDocumentation or BrowseWixRESTDocsMenu, then ReadFullDocsArticle; the SDK, CLI, headless and apps docs for code. - **The exact shape**: model a call only on an example that matches the case; fill the rest with SearchWixAPISpec on the method's docs URL (request and response schemas, `method.publicUrl` for REST, `method.sdk` for the JavaScript SDK). A query's filter and sort fields and operators are a closed list per method. - **The call, or the code**: ExecuteWixAPI runs one async function holding every step code can resolve, the reads and the writes they feed together. Code the user keeps (an app, a headless site, a script over REST or the JavaScript SDK) is written from the same shapes; the headless skills are a shortcut on that path. - **When a call fails**: the error says what was wrong and carries a Wix request id; fix that, never resend unchanged or guess. - **Wix skills**, what each is for and how to read one: from disk when installed (the Wix plugin, or `npx skills add wix/skills`, `--skill <name>` for one, `-g` for the user's home, into `.agents/skills/<skill>/` or a similar folder the client reads, such as `.claude/skills/<skill>/`), else online with ReadFullDocsArticle at `https://www.wix.com/skills/<skill>/<path>`. - **wix-manage**: REST recipes for managing a site's business solutions, one per task; follow the recipe and make its calls with ExecuteWixAPI, its docs URL in `sourceDocUrls`. Its list of recipes is `SKILL.md` in the installed skill, or online https://dev.wix.com/docs/api-reference/articles/ai-tools/wix-mcp/skills/wix-management-recipes-index.md, and each API area has its own `<API section>/skills.md` (for example https://dev.wix.com/docs/api-reference/business-solutions/bookings/skills.md). - **wix-headless-kit**: builds a Wix Headless site on shipped, verified code from wix-headless-templates, a `@wix/sdk` React core or the same data layer as plain REST calls: scaffold with the CLI, deploy, seed, design on the shipped hooks, release. https://www.wix.com/skills/headless-kit/SKILL.md - **wix-headless-templates**: the code wix-headless-kit builds from, one folder per Wix Business Solution. https://www.wix.com/skills/headless-templates/ When the user asks you to do something in Wix, do it yourself, in as few steps and questions as you can; don't tell them which docs to read or which API to call.

    Input schema

    Input schema unchanged.

    1 unchanged entry
    • (schema root)

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
11 tools with no recorded change
  • BrowseWixRESTDocsMenu
  • ReadFullDocsArticle
  • ReadFullDocsMethodSchema
  • SearchBuildAppsDocumentation
  • SearchDevelopmentDocumentation
  • SearchWixCLIDocumentation
  • SearchWixHeadlessDocumentation
  • SearchWixHelpCenter
  • SearchWixRESTDocumentation
  • SearchWixSDKDocumentation
  • SearchWixWDSDocumentation

Evidence and provenance

Static findings
PASS from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
Human review
Automated static analysis. No reviewer decision is recorded for this comparison.
Published evidence
Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
Comparison
wix/1.0.98~1.0.99The published comparison identifier.
Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 15, 2026, 3:16 AM UTC.
Distribution
npm
Previous release
@wix/mcp@1.0.9815 tools · published by the registry Nov 3, 2026, 9:56 AM UTCArtifact integritysha512-ujQ8QB94tF7ckO9TrA22Kg2HaTFCg35Arwt/HMkup94KyxNr95HxCgNf60JRPMDj6NWU/eNfSYmc/d0h9a9ugw==Interface fingerprintsha256:bd82565a3e8c311c1796f3109f3b9959360ef042b7cee6c811559a5436557a3aExact interface snapshot (JSON)
Current release
@wix/mcp@1.0.9915 tools · published by the registry Nov 12, 2026, 10:20 PM UTCArtifact integritysha512-j+riWTWK9FgoGZd+ZKaNvj/qBOanU4CUlLNITSamU1VLACFyOsYLn7GXI4vzzwIt6cLSU30tpdXAECAc6B1kRw==Interface fingerprintsha256:c52e983f05b10a0ebaafd62d260f68a7688477ea8ea87871e4fa1799fdef6207Exact interface snapshot (JSON)

The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.

MODELARA ANALYSIS OUTPUT

Interface findings

Analyzed with Modelara v0.1.8 · Nov 15, 2026

Informational

4 findings
  • CheckDomainAvailabilityINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • StartDeployWebsiteINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • StartHeadlessBuildINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • WixREADMEINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
What do these results mean?
PASS
No policy-significant interface change detected.
REVIEW
Interface changes require inspection.
FAIL
A policy-significant change was detected.
INVALID
The comparison could not be evaluated reliably.
← Back to Wix MCP release history