Wix

Wix

Wix provides a first-party MCP server that lets AI clients search Wix docs, write Wix code and make API calls on Wix sites, via OAuth or API key.

Content, CMS, creative & DAMSystem of engagementAgent-accessible SaaS
An illustration of access surfaces surrounding a governed system.
System roleSystem of engagement
Access maturityAgent-accessible SaaS
MCP supportOfficial MCP server
Reference updatedNot stated by publisher
BYO-UI reviewedOct 31, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Wix sites and business solutions (stores, bookings, CRM, blog, events, etc.) via Wix APIs.

02 · Data you can retrieve

Documentation search and site API reads.

03 · Actions and write paths

API calls on Wix sites per Wix MCP tools.

04 · Authentication and permissions

Wix account sign-in (remote) or API key plus account ID.

05 · Monitoring, approval, and recovery

Client-side; not individually verified.

06 · Limits and caveats

Mixes developer-context and site-operation tools.

Agent access

MCP support

Official MCP serverWix remote MCP (developer and site-API tools)Current documented service

Support: Official MCP server

Read scope: Docs and site data via APIs.

Write scope: Site API calls.

Authentication: Wix login or API key.

Approval boundary: Writes should require human confirmation in the client.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access3
Identity3
Governance3
Agent access4
UI extensibility4
Portability3
Observability3
Documentation4

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Wix ships them.

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

2 recorded sources
HomepageSource inventory
https://www.wix.com/ ↗

First-party product homepage.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Oct 31, 2026

Content reopened and reviewed in the 2026-10-31 research refresh.

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.