Claude Wix connectorWhat Claude can do in your Wix account.
The Claude Wix connector exposes 12 tools. 9 read your site list and Wix's developer documentation, 3 act on your account or send something over to Wix. Here: what Claude reaches, what stays out of reach, and who decides.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can reach your Wix account
Two kinds of people get something out of this connector. A site owner can ask Claude about their sites and have it act on one, from publishing to a store update, without opening the dashboard. A developer gets Claude answering from Wix's own documentation, with the exact method formats, instead of from memory.
The right site, then the right data. ListWixSites tells Claude which sites your account holds, and CallWixSiteAPI then runs a request on the one you mean: this week's bookings, a product's stock, a blog post's status.
Publishing without the dashboard. ManageWixSite handles account-level jobs such as creating, updating or publishing a site, so a finished landing page can go live from the conversation.
Answers from the source for developers. The five search tools cover the REST, SDK, Headless, Build Apps and Design System docs, and ReadFullDocsMethodSchema shows what a method expects before anything is called.
Now what it does not do. ManageWixSite cannot touch a site's business data; that only goes through the site API. Wix's page describes six more tools, including an image upload and another way to call a site's business-data APIs, that the Claude sheet does not list, so do not count on them here. And nothing runs by itself: no tool wakes up when an order lands. For that kind of background job, see the Wix Make integration, a different trade altogether.
The vocabulary in one minute
Five words you will meet while plugging Wix in.
- Connector
- The link you set up once between Claude and an account you already have, so it can work in that account while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself; the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Wix.
Plug Wix into Claude in three steps
- 01
Find Wix in Claude
In Claude's settings, open Customize, then Connectors, and look for Wix in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on first, then each member connects on their own.
- 02
Start the connection
Click Connect on its row and sign in to Wix in the window Wix opens itself. If the link breaks later, use Disconnect and plug it back in from the same row.
- 03
Read the authorization screen
Read the screen before you accept. It belongs to Wix, not to Claude, and it sets what the access covers. You can withdraw that access later from your Wix account as well.
The 12 Claude Wix connector tools, grouped by what they do
Wix gives Claude 12 tools: 9 that read your account, 3 that change something in it.
Two groups: what Claude reads, and what acts on your account or leaves your conversation. The names stay exactly as Claude shows them.
- 9 read
- 3 write
What Claude reads (9)
9 toolsTools that look up your sites or Wix's developer documentation without touching anything.
WixREADME
Acts as Wix's own signpost: Claude opens it first on most Wix jobs and it points to the right tool or ready-made recipe for the task. It returns guidance, not data from your sites.
SearchWixWDSDocumentation
Searches the documentation of the Wix Design System, the library of interface components Wix apps are built with, and brings the relevant pages into the conversation.
SearchWixRESTDocumentation
Searches Wix's REST documentation, the reference for the web requests that read or drive a Wix site from outside, so Claude answers from the official pages rather than from memory.
SearchWixSDKDocumentation
Looks through the documentation of the Wix SDK, the code library developers use inside Wix sites and apps, and surfaces the pages that match the question.
SearchBuildAppsDocumentation
Queries the Build Apps documentation, the part of Wix's developer site about making apps other Wix users install, and returns the matching sections.
SearchWixHeadlessDocumentation
Searches the Wix Headless documentation, for projects that keep Wix as the back office while the visible site is built elsewhere.
ReadFullDocsArticle
Retrieves the whole text of a documentation article from its address, once a search has pointed to it, so Claude reads the full page instead of a snippet.
ReadFullDocsMethodSchema
Gets the complete request and response format of one API method: which fields go in, which come back, and their types.
ListWixSites
Queries the sites attached to your Wix account, which is how Claude knows which site you mean before it looks at anything else.
What Claude can act on (3)
3 toolsTools that reach into your account or send something to Wix. No source gives any of them its own confirmation rule: the general rule below applies.
CallWixSiteAPI
Approval: see the ruleRuns one REST request against a chosen site of your account. Wix names it as the route for reading or changing a site's business data, such as bookings or store records.
ManageWixSite
Approval: see the ruleCarries out account-level actions on a site, such as creating one, updating it or publishing it. It works with your account's credentials only.
SupportAndFeedback
Approval: see the rulePrompts you for a message and passes it to Wix as feedback on the connector. Wix explains that your client asks for the text and sends it straight to their team.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. The request shows up in the conversation, at the moment it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organisation, keeping the documentation lookups and closing publishing, for example. That setting applies to everyone and nobody overrides it from their own account. And Claude works with your rights and nothing more: a site your Wix account cannot open stays closed to it too.
Which plans it is available on
None of the 819 directory sheets shows availability by plan. The answer, connector by connector, is not published anywhere: it is a real gap in the catalogue.
The general rule is published, though. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens the connector for the organisation before members can connect individually. For the current state, check Wix's sheet in the official directory. One more point: this connector is documented only by Wix itself, with no Claude help page of its own.
Where the Claude Wix connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when an order arrives, a booking is cancelled or a form is submitted.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The directory's partner badge is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as announced. Plug in only what comes from a publisher you trust. Wix states that all of its tools are enabled by default on its side; what limits them here is Claude's approvals and your organisation's settings. Other connectors are gathered on the Integrations hub.
Need help connecting Wix to Claude?
A person reads every message.
