How to Connect Wix to Claude with MCP

You can connect Wix to Claude in a few minutes using the Model Context Protocol (MCP), and once it’s connected, Claude can read and update your site’s content, bookings, and products without you copying things in and out of the Wix dashboard. Wix is also one of the more straightforward servers to connect — its OAuth just works with a new client, unlike several other tools in this series. This guide covers both ways to do it: Wix’s official remote MCP server connected directly, and connecting it through a gateway if you use more than one AI client.

What the Wix MCP server actually does

Wix publishes an official remote MCP server at mcp.wix.com/mcp. It exposes your site’s content, bookings, and products as tools Claude can call directly. In practice that means prompts like:

“List every booking scheduled for next week and flag any double-bookings.”
“Add a new product to the store with this name, price, and description.”
“What’s the current inventory count on the items that are low in stock?”
“Update the copy on the homepage hero section.”

Claude reads and writes through the same permissions your Wix account already has — it isn’t a separate export or a static copy of your site, it’s your account acting on your behalf, site by site. That includes creating or canceling a booking and changing a product’s price, which is the part worth pausing on before you connect a site that’s actually taking orders or appointments.

Option 1: Connect Wix to Claude directly

Claude supports remote MCP servers natively. The short version of the setup:

Open Claude’s connector or MCP settings.
Add a remote server pointing at Wix’s MCP endpoint.
Sign in with your Wix account when prompted — this is standard OAuth, so Claude never sees your Wix password, and you can revoke access from Wix’s own account settings at any time.

That’s enough for one person using Wix inside Claude. The tradeoffs show up once you add a second tool or a second person: every additional AI client (ChatGPT, Cursor, an agent) needs its own copy of that same connection, its own OAuth grant, and its own place where the config can go stale or get lost.

Option 2: Connect it once, through a gateway

If you’re already juggling more than one MCP server, or more than one AI client, wiring each pair directly gets old fast — that’s the connection sprawl we wrote about in what an MCP gateway is. The alternative is connecting Wix (and everything else) to one gateway URL, then pointing every AI client at that single URL instead of reconfiguring each one.

With gate specifically, connecting Wix looks like this: add gate’s gateway URL to Claude once, then pick Wix from the Wix server page in the directory and sign in with OAuth the same way you would directly. From then on, Wix’s tools are available in every client connected to your gate URL — Claude, ChatGPT, or Cursor — without a second setup step. You can see the full list of servers set up this way on the MCP servers page.

Why the connection method matters for a live storefront

Wix isn’t a draft or a staging copy — for a lot of accounts it’s the live site customers are booking and buying from right now. A few things worth checking before or right after you connect:

Is it the official endpoint? Connect Wix’s documented server (mcp.wix.com), not a third-party mirror claiming to proxy it.
Which sites can it actually reach? An MCP connection to Wix typically covers every site your account can open, not just the one you had in mind. Know what’s in scope before you hand Claude a broad prompt against “the site.”
What can it write, not just read? A connection with write access can have bookings created or canceled, product prices changed, and content published at whatever pace it’s prompted to. Those changes are visible to real customers immediately, so treat write access here with at least as much caution as you would a production deploy.
Who else on your team can reach it? If more than one teammate connects Wix to their own AI client, you likely want a shared, revocable setup rather than everyone holding their own token — the same access-control question we cover in MCP access control for teams.

You can run a quick, no-signup check on any server’s tool list — including ones that require OAuth, once connected — with gate’s free MCP security scanner, which looks for prompt injection and hidden instructions in tool descriptions before you rely on a server day to day.

Troubleshooting the connection

A few things that commonly go wrong when connecting any remote MCP server, Wix included:

OAuth loop or sign-in fails. Make sure you’re signed into the right Wix account before authorizing — a mismatched account is the most common cause, especially if you manage sites for clients under separate logins.
Claude can’t find a site you know exists. Wix’s tools respect your permissions in Wix itself — if a site is owned by a different account or you’ve only been given editor access to part of it, Claude won’t see more than you can.
Tools disappear after a Wix update. Remote servers can change their tool list without warning. If you’re connected through a gateway, that kind of change is exactly what drift detection is meant to catch.

The bottom line

Connecting Wix to Claude with MCP takes a few minutes either way: point Claude directly at Wix’s server and sign in, or connect it once through a gateway if you want the same Wix access available in every AI client you use, with the server’s tools checked before they go live. Either way, treat write access to a live site — one that actually takes bookings and orders — the same way you’d treat any other tool that can change something a real customer sees or pays for.