Wix MCP: The Official Hosted Server, Explained
Yes — Wix has an official MCP server. It’s a hosted, remote server at https://mcp.wix.com/mcp that Wix maintains, so any MCP-compatible AI tool can search the Wix documentation, write code for the Wix platform, and make API calls against your live sites. Wix has even shipped it as a first-party connector inside Claude, so for many people there’s nothing to configure at all. If you searched “Wix MCP,” the connection you want exists and Wix built it.
The thing worth knowing before you set it up: an MCP server hands your Wix account to an AI inside a conversation you start. It’s a doorway, not a worker. Nothing watches your site for you, nothing fires when an order comes in or a form is submitted, and nothing runs while the chat is closed. Here’s exactly what the Wix MCP does, how to turn it on, where it stops — and what to use when you want Wix work that runs on its own.
See also: the full MCP server list — which apps have one, and what each can reach.
What the Wix MCP server does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, ChatGPT, Cursor, Copilot, Windsurf, and others — talk to an outside app through a shared interface. Wix runs one official server, and it wears two hats: a documentation-and-code assistant for people building on the platform, and a bridge to your actual sites through Wix’s REST API.
With it connected, an AI client can:
- Search and read the Wix docs — pull the right REST, SDK, or Wix Design System reference into the chat instead of hunting through dev.wix.com yourself.
- Write code for your site — scaffold Velo code, headless setups, or a custom app, grounded in the current API schemas rather than a guess.
- List and act on your live sites — the
ListWixSitesandCallWixSiteAPItools let the AI query a specific site and perform actions on it: read products, prices, and stock, check orders, update blog posts, or manage bookings and store content. - Create and manage sites —
ManageWixSitecan even spin up a new site at the account level.
It’s genuinely useful for ad-hoc work: ask “what did my store sell last week,” have it draft and publish a blog post, or add a product — answered and executed against your real Wix data, no dashboard clicking.
How to set up the Wix MCP server
The remote server is the quick path — no hosting, and in Claude, barely any setup:
- In Claude, the easy route: open the connectors panel in settings, find the built-in Wix connector, click Connect, and authorize with your Wix account through the OAuth prompt. That’s it.
- In any other MCP client (Cursor, Copilot, Windsurf, VS Code), add a remote MCP server pointing at
https://mcp.wix.com/mcp— Cursor has a one-click install — then sign in through the OAuth flow when prompted. - For tools without remote MCP support, Wix provides an
npx @wix/mcp-remotecommand instead; you’ll need Node.js 19.9 or higher installed. You can also authenticate with a Wix API key and account ID for setups like n8n. - Confirm the tools appear in your client, then start a chat and ask it to read or update something on your site.
Wix’s MCP docs cover every flow; the built-in Claude connector is the one most non-developers want.
Where the Wix MCP stops
None of this is a knock on MCP — it’s just the shape of the protocol. Four limits show up the moment you want more than a conversation:
- It only works inside a chat you start. Close the window and nothing happens. The AI doesn’t watch your Wix site; it waits for you to ask.
- No triggers. A new store order, a form submission, a booking, a contact added — none of these can start anything through MCP. There’s no “when this happens on my Wix site, do that.”
- It’s one app at a time. The Wix MCP knows Wix. Getting a new order into QuickBooks, a Slack channel, and a Google Sheet means wiring up (and authing) a separate MCP server for each, then hoping your client can juggle them in one turn.
- You own the plumbing and the scopes. OAuth tokens, refresh, API keys, and the blast radius of read/write access to your live site are all on you.
So the Wix MCP is a great way to ask your site things, generate code, and make one-off edits. It is not a way to make Wix run — to have work happen on a schedule or in reaction to an event, across the other tools an order or booking touches.
Running Wix work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits. Carly connects to Wix natively — no MCP server to configure, no OAuth plumbing to maintain — and to the ~260 other apps it supports, plus anything with a public API through your own key. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so Wix work happens whether or not anyone has a chat window open.
A few things that MCP can’t do but a Carly workflow can:
- When a new order comes in on your Wix store → create the customer in QuickBooks, post it to the
#ordersSlack channel, and add a row to your fulfillment sheet — automatically, the moment it happens. - Every morning → summarize yesterday’s Wix orders and new bookings and send the recap to your inbox.
- When a contact fills out a Wix form → enrich the lead, add it to your CRM, and draft a first follow-up email for approval.
The non-AI steps — the moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone of the workflow. The AI steps (drafting, summarizing, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the Wix connection and everything downstream.
If you just want to interrogate your site or generate code from a chat, Wix’s official MCP server is the right tool and it’s free to connect. If you want Wix to actually do things — on a trigger, on a schedule, across every app an order or booking flows through — that’s the job MCP wasn’t built for, and it’s the one Carly was.
FAQ
Does Wix have an official MCP server?
Yes. Wix maintains a hosted, remote MCP server at https://mcp.wix.com/mcp that lets MCP-compatible AI tools search Wix documentation, write platform code, and make API calls on your live sites. It’s also available as a first-party built-in connector inside Claude.
Is the Wix MCP server free? Connecting the MCP server is free — you’re authorizing an AI client against your existing Wix account and scopes. You still need whatever Wix plan your site and business features live on, and heavier business operations like accepting payments require a Premium plan.
Can the Wix MCP trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven Wix work across apps, you need a workflow tool like Carly rather than an MCP server.
Can I connect Wix to AI without coding or hosting a server? Yes. You don’t have to touch MCP config at all. Carly connects to Wix for you and lets you build the automation in plain language — describe what you want to happen and it wires up the site and the other apps involved, with no server to configure and no code to write.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
