Developer-tools MCP server
Wix MCP
Version history of discovered tools, schemas, and declared agent authority.
OBSERVED INTERFACE
Capability surface
Modelara’s observed declarations are shown separately from its derived effect classifications.
- 15
- 0
- 0
- 0
Unknown means Valyd could not determine the capability's effect confidently from the declared interface and static evidence. It is not treated as safe.
- Package
- @wix/mcp@1.0.100
- Registry
- npm
- Published
- Nov 13, 2026
- Integrity
sha512-2p6Dna5BHz02s5aILwaLoJIMHwyAqxyiDxNMIZHjvuNIqMhikipJhQVwWU1NSCSSAd77kpk4ls1RnziYszmWrA==- Analyzer
- modelara v0.1.8 · policy not recorded
15 capabilities
| Capability | Type | Derived effect | First observed in Valyd coverage | Last changed |
|---|---|---|---|---|
BrowseWixRESTDocsMenuwix:tool:BrowseWixRESTDocsMenuObserved interface and hashesBrowse the Wix REST API documentation menu hierarchy. Alternative to SearchWixRESTDocumentation - use this to explore and discover APIs by navigating the menu structure instead of searching by keywords. - Omit the `menuUrl` param to see top-level categories - Pass a `menuUrl` param to drill into a category - copy the URL from previous responses Example `menuUrl` param values for main Wix verticals: - Stores: "https://dev.wix.com/docs/api-reference/business-solutions/stores" - Bookings: "https://dev.wix.com/docs/api-reference/business-solutions/bookings" - CMS: "https://dev.wix.com/docs/api-reference/business-solutions/cms" - CRM: "https://dev.wix.com/docs/api-reference/crm" - eCommerce: "https://dev.wix.com/docs/api-reference/business-solutions/e-commerce" - Events: "https://dev.wix.com/docs/api-reference/business-solutions/events" - Blog: "https://dev.wix.com/docs/api-reference/business-solutions/blog" - Pricing Plans: "https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans" - Restaurants: "https://dev.wix.com/docs/api-reference/business-solutions/restaurants" - Media: "https://dev.wix.com/docs/api-reference/assets/media" - Site Properties: "https://dev.wix.com/docs/api-reference/business-management/site-properties" Input schemasha256:73e35876cb2152f4359f75dcd00fc8c5836e57993a5ecf4c4b5bc132cfa02398Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.0.98 | No change observed | |
CheckDomainAvailabilitywix:tool:CheckDomainAvailabilityObserved interface and hashesChecks 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 schemasha256:ef2e819c999fb88becbefe63ae961171ea7710c222e0c7d321c38db69c049078Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.0.98 | 1.0.99 | |
ReadFullDocsArticlewix:tool:ReadFullDocsArticleObserved interface and hashesFetches 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) — 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. It returns the whole file. For part of a long skills file, ExecuteWixAPI can fetch the same URL, split the text into lines and return only the lines needed ("How to read a skill" in WixREADME has the code). In ExecuteWixAPI, a dev.wix.com docs page needs `.md` added to its URL, and Help Center articles are not reachable: those are read only with this tool. For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include ?apiView=SDK. Input schemasha256:cc7e30bf01ddf7223ac65bb4ec88f780fd6b9bfc98ac148f843522db1c704e28Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.0.98 | No change observed | |
ReadFullDocsMethodSchemawix:tool:ReadFullDocsMethodSchemaObserved interface and hashesFetches the full method schema for a given method. This will give you the entire request/response schema with all the fields and their descriptions. For REST and SDK API-reference methods, prefer SearchWixAPISpec when it is available: it can fetch and inspect the exact method schema by docs URL, return the request/response shape, the JavaScript SDK call (`method.sdk`: package, namespace, method, positional parameters, examples), and inspect selected nested component schemas without dumping unrelated fields. Use ReadFullDocsMethodSchema only when SearchWixAPISpec is unavailable or did not provide the needed detail. For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include ?apiView=SDK. Input schemasha256:489d519e4fad403fec9d46015865cc403666fefd35e5cf24b85848eb8349e95dOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.0.98 | No change observed | |
SearchBuildAppsDocumentationwix:tool:SearchBuildAppsDocumentationObserved interface and hashesSearches the Wix Build Apps documentation. Input schemasha256:9bedfc43cef8bd7485c0a6340bf8e8a4bb9b7ce7a4135d1cbc93f9867dfa58e9Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.0.98 | No change observed | |
SearchDevelopmentDocumentationwix:tool:SearchDevelopmentDocumentationObserved interface and hashesBroad Wix development documentation (platform concepts, developer guides, getting started). **Last resort — development tasks only.** Skip it entirely for general, business, support, or Wix-editor questions; for those, use `SearchWixHelpCenter`. Call it only after the specific search for your task returned nothing useful: `SearchWixRESTDocumentation` (REST), `SearchWixSDKDocumentation` (JS SDK), `SearchWixCLIDocumentation` (CLI), `SearchBuildAppsDocumentation` (apps), `SearchWixHeadlessDocumentation` (Headless), `SearchWixWDSDocumentation` (WDS). Never use it as a first search. Input schemasha256:8eea61aa854ffe039a2d655de05b97e084e3bb78a2684717cde7b4aa92f2d8feOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.0.98 | No change observed | |
SearchWixCLIDocumentationwix:tool:SearchWixCLIDocumentationObserved interface and hashesSearches the Wix CLI documentation for website development and CLI commands. Use this tool when you need information about Wix CLI commands, local development workflows, or CLI-based website development. Specify what you need information about (e.g., 'wix dev command', 'local development setup', 'CLI authentication', 'wix deploy'). If you can't find what you need, try to rephrase your search term or use bigger maxResults value. Input schemasha256:c86cd47e1fbe05708017240dbad01358c1dbde7f72426283c81707a57d8ce38aOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.0.98 | No change observed | |
SearchWixHeadlessDocumentationwix:tool:SearchWixHeadlessDocumentationObserved interface and hashesSearches the Wix Headless documentation. Input schemasha256:3db56a67096addef19bdcf96edd8d1bc07586d92e14995419acdfb9a3908f071Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.0.98 | No change observed | |
SearchWixHelpCenterwix:tool:SearchWixHelpCenterObserved interface and hashesSearches the Wix Help Center (support.wix.com): how site owners do things in the Wix dashboard and editors, such as connecting a domain, managing a Premium plan, setting up a store or bookings, and fixing account or site issues. The Help Center is written for people doing things by hand in Wix's dashboard and editors. To act on a site yourself, the Wix developer docs come first: find the method with SearchWixRESTDocumentation or BrowseWixRESTDocsMenu. Use it for "how do I ... in Wix" questions about the product, or to give the user click-by-click steps for something no API covers. Not for building with code: for Wix APIs, SDK, CLI, apps, or Headless, use the matching developer documentation search. Results are excerpts; read a full article by passing its support.wix.com link to `ReadFullDocsArticle`. Input schemasha256:892cc44d64ed569f55d29718860406aae3e1a9603d229c8d2e4e9c2a0e7060aeOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.0.98 | No change observed | |
SearchWixRESTDocumentationwix:tool:SearchWixRESTDocumentationObserved interface and hashes**Searches the official Wix REST API documentation — the starting point for any Wix REST API task.** Unless you already have the exact method `docsUrl` in context, begin the task here; this is how you discover the right endpoint. Reach for it before `SearchWixAPISpec`, and avoid writing code that scans or filters `lightIndex` to find an endpoint (e.g. `lightIndex.filter(...)`, `lightIndex.flatMap(...)`, or substring-matching on `docsUrl`/`name`/`summary`) — that has no relevance ranking and silently misses composite and method-level operations. This is the ranked semantic-search discovery tool over the Wix REST API docs: describe your intent in natural language and it returns the matching REST endpoints/methods (with their `docsUrl`) ranked by relevance. It is the first step whenever you need to do something on a Wix site via HTTP and don't already have the exact `docsUrl` in context — for creating, reading, updating, or deleting any kind of Wix entity, across every business domain. It covers all Wix REST domains equally, every product'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), and the rest. Just describe the resource, action, or goal in plain words (e.g. 'add a catalog item with inventory', 'book a service', 'update a data collection item', 'create a discount', 'list contacts', 'get site details endpoint', 'REST authentication'); the ranking handles matching your wording to the right API regardless of domain. **Next step after this tool:** take the `docsUrl` it returns and inspect that method's exact request/response schema with `SearchWixAPISpec` (`getResourceSchemaByUrl(docsUrl)`), then execute. `SearchWixAPISpec` is only for INSPECTING a `docsUrl` you already have — it is NOT a discovery tool. Skipping this step to hand-search `lightIndex` yourself is a mistake: raw index filtering has no relevance ranking and misses operations this ranked search finds. Discover here first, every time. If you can't find what you need, rephrase your search term or use a bigger maxResults value. Input schemasha256:9e9f5012c0581921a548704281105308f1126ed28174492084039e3e28aaaed0Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.0.98 | No change observed | |
SearchWixSDKDocumentationwix:tool:SearchWixSDKDocumentationObserved interface and hashesSearches the Wix JavaScript SDK documentation. Next step for an API-reference method it returns: pass its docs URL (with or without `?apiView=SDK`) to `SearchWixAPISpec`'s `getResourceSchemaByUrl` when available, and read `method.sdk` for the exact import, call signature, typed parameters, return type, and examples. Input schemasha256:aff014ada1ccd547f36e35d24e8fc5fa33edc228be7f2af657d60eca75d11f31Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.0.98 | No change observed | |
SearchWixWDSDocumentationwix:tool:SearchWixWDSDocumentationObserved interface and hashesSearches the Wix Design System (WDS) documentation. Input schemasha256:3415f2b51ccc1545150e270e186ecedf500a33cb1c5281403227cbaf26e2c308Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.0.98 | No change observed | |
StartDeployWebsitewix:tool:StartDeployWebsiteObserved interface and hashesCreates 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 schemasha256:5f93f58aa5f2627b04bf48b694cd1f34325a5a7e472f456140891c70d01c6885Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.0.98 | 1.0.99 | |
StartHeadlessBuildwix:tool:StartHeadlessBuildObserved interface and hashesReturns 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 schemasha256:2b33d7e8d878168a53f68744d76c0fcf5701e7060478a4bf950e770b35a6fc9dOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.0.98 | 1.0.99 | |
WixREADMEwix:tool:WixREADMEObserved interface and hashes# 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 schemasha256:73fc3af6ba54a1293c44f954cf944c40d069a764ef7974e6fc74addd4231b225Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.0.98 | 1.0.99 |
No capabilities match these filters.
STATIC COMPARISONS
Release history
- 1.0.99 1.0.100PASS0 added0 removed0 schema0 write0 destructive0 unknown
- 1.0.98 1.0.99PASS0 added0 removed0 schema0 write0 destructive0 unknown