wix-readme
The Wix plugin
The plugin is two things: skills, folders of instructions and shipped code for building on Wix, each with a SKILL.md at its root; and the Wix MCP server at https://mcp.wix.com/mcp, whose tools read and change the user's Wix sites and account. The skills say how; the tools do.
How to work with Wix through the plugin
Every Wix task ends in one of two places: a call made now with the user's account, or code the user keeps that makes the same calls (an app, a headless site, a script). The way there is the same.
- Start with
WixREADME, once per conversation. It returns this flow in full and the account's sites with their installed apps. - Pick the site. The
siteIdcomes from the site context; when several fit, ask. A business solution's API works only on a site with that app installed, and an app's version changes its endpoints, so check the site's apps first. - Find the method. The first source that gives it: an earlier tool result in the conversation; else the skill that covers the task (the index below says what each is for), whose example is the model when it matches the case; else the docs,
SearchWixRESTDocumentationorBrowseWixRESTDocsMenufor REST, the SDK, CLI, headless and apps searches for code, thenReadFullDocsArticleon the method's page. - Get the exact shape. A request is modeled on an example that matches the case: a skill's recipe or template, or the method's docs page, when it shows the fields the case needs. That is enough. The schema is for what no example shows: a field, an enum, a filter or sort key (a closed list per method).
SearchWixAPISpecon the method's docs URL returns the request and response schemas, the REST URL and the JavaScript SDK call;ReadFullDocsMethodSchemawhen it is not available. - Make the call, or write the code. To do it now:
ExecuteWixAPI, one function holding every step of the task, the reads and the writes they feed. For code the user keeps: write the call from the shape found in step 4, REST or SDK.wix-headless-templatesis that code already written and verified, one folder per business solution, andwix-headless-kitbuilds a site on it.
Throughout: nothing Wix-specific from memory. Every URL, id, setting location, product fact, request shape and field name comes from a skill, the docs tools, an earlier tool result or the user.
Creating a site
A new Wix site is written in code and uploaded. StartDeployWebsite returns the guide for a site the agent writes or files the user brought; StartHeadlessBuild returns the guide for a site that needs Wix business features (a store, bookings, a CMS, members, payments and the rest). Each guide creates the site, uploads it and says what comes next; call one and follow it.