Wix

Yes, and Wix documents it as a headline use. ManageWixSite performs account-level actions including creating, updating and publishing a site, and Wix's own sample prompts show publishing a named site and installing an app on it. Publishing pushes the current draft to the public domain, so a change an agent made becomes visible to visitors without a second confirmation step.

Yes. ExecuteWixAPI and CallWixSiteAPI reach the Wix REST API on a chosen site, and the Stores Catalog V3 API includes Update Product, Bulk Update Products By Filter, Delete Product and inventory item writes. Wix's own sample prompt applies a fifteen percent discount to every product on a named store, so a single instruction can reprice a whole catalogue.

Yes, on both counts. The same REST passthrough reaches eCommerce Orders — including Cancel Order, Update Order and Refund Payments — and the CRM Contacts V5 API, which includes Create Contact, Delete Contact and Bulk Delete Contacts By Filter. Refunds move real money and contact deletion is not reversible from the connector.

Eighteen, by Wix's own count. Anthropic's directory snapshot lists twelve of those names. The six it omits are ExecuteWixAPI, UploadImageToWixSite, GetSiteContext, BrowseWixRESTDocsMenu, SearchWixAPISpec and WixBusinessFlowsDocumentation. Every directory name appears in Wix's list, so the directory is a strict subset rather than a contradiction.

One scope, and it grants nothing. The server's RFC 9728 descriptor declared scopes_supported of offline_access on 2026-08-22, which only permits refresh tokens. Wix expresses real API permissions as scopes for apps and API keys and as roles for Wix users, so an interactive sign-in inherits your entire Wix role instead of a narrowed grant.

Authenticate with an API key rather than an interactive login. Wix states an API key's permissions combine two independent dimensions: scopes that define which operations it can perform, and site access that defines which sites it can target. Wix advises giving each key the narrowest set of sites its integration needs. Only account owners and co-owners can create keys.

Yes, through the REST passthrough. Wix's published sample prompts include sending an inbox email message to a named contact on a named site with an image attached, and describe the agent creating the contact first if it cannot find one. That is an outbound message reaching a real person, triggered by one natural-language instruction.

Auto-run mode. Wix's own documentation warns that depending on the prompt, your AI client may make changes to your local code files or live site, and recommends disabling auto-run so the client must request permission for each tool call. That gives you a review step before a write reaches the public site.

No, they are opposite directions. This connector links your agent to your Wix account. Wix also gives every site a built-in MCP server at your-domain/_api/mcp that needs no authentication and lets visitors' agents browse products, book services and start a checkout. That one is a public read and booking surface on a site you own.