Wix Announced a New MCP Server - What's That?

Your field report from first boot‑up to full‑stack headless app

TL;DR – Key takeaways

• MCP lets AI talk to Wix as if it were an API built for models, not humans.

• Setup is copy‑paste simple but choose a capable LLM for smooth sailing.

• No‑code tasks (create sites, coupons, collections) already feel like wizardry.

• Dev workflows benefit too, though SDK edge‑cases still need manual fixes.

• Great documentation is now mission‑critical—AI can’t guess what isn’t written.

• Is this the beginning of the end for the drag and drop editor?

1 | Wait… what’s MCP again?

Model Context Protocol (MCP) is an open standard from Anthropic that gives AI models a USB‑C‑style port into real‑world software. An MCP server exposes three predictable call‑outs—resources, tools and prompts—so a large‑language model (LLM) can discover what it can do the moment it connects. It’s an AI‑first wrapper that sits in front of a classic API; the human‐friendly developer docs are still there, but the model gets a machine‑readable self‑description instead. Early adopters already exist, such as the community‑built Spotify MCP wrapper.

2 | What Wix just shipped (quietly)

Wix nudged a terse doc page live on 7 May 2025 announcing its own MCP endpoint—no splashy blog, just a JSON snippet and a line saying “works in Claude, Cursor, WindSurf and VS Code.” The server lets an AI:

• Search the entire Wix SDK and Headless documentation.

• Act on live sites—create coupons, add CMS collections, approve members, spin up whole sites.

• Scaffold code for front‑end or server projects using the official JavaScript SDK.

Setup is literally copy‑and‑paste: drop a 12‑line JSON block into any MCP‑aware client and restart.

Dual usage:

• No‑code users can literally tell Claude “make me a store called Space Cats” and watch it appear in their account.

• Devs can stay in their IDE, ask the agent to spin up a headless React app, and have it wire authentication, data queries and UI for them.

  
  

  

  Claude in action with the MCP

  
  

3 | Wix MCP Setup attempts – blow‑by‑blow

I made two successful attempts at implementing the MCP server in an AI Client and IDE. There were a few challenges along the way...

Attempt A — Claude Desktop (no‑code focus)

Setup + challenges

1. Dropped the JSON into File → Settings → Developer → Edit config and relaunched. Claude died with an “invalid JSON” toast; a hidden Unicode glyph from the docs was the culprit. I ran the snippet through VS Code’s formatter, saved, and relaunched—no crash.

   
   

   

   Copy Pasta woes

   
   

2. Still no hammer icon (the “tools loaded” badge). Claude keeps a background daemon, so I killed the process in Task Manager and started fresh. The MCP now works! (The icon never appeared though).

   

   It appeared! (Sort of)

What we actually did

• “Create an online store.” → Claude called listWixSites, authenticated itself and spun up My Site 62 with Stores pre‑installed.

• “Add a Muppets CMS collection with five items.” → Five records popped straight into the dashboard.

• “Rename the site to The Best Store Ever.” → Claude tried but got stuck hunting the right endpoint, then hit its conversation‑length cap—so I shelved Claude and moved on.

  
  

Important Note:

While troubleshooting Claude I fired up Windows CMD and ran the one‑liner Wix provides:

npx @wix/mcp --remote https://mcp.wix.com

That script does two things behind the scenes:

1. Spins up the MCP helper locally. It pulls the @wix/mcp package, launches a tiny Node server on localhost, and proxies every request to Wix’s remote MCP endpoint.

2. Kicks off OAuth. On first run it opens a browser tab asking you to log in to your Wix account. Once you approve, the helper stores a short‑lived access token (plus a refresh token) in your user profile directory.

It seemed that because those tokens now sit on disk, any MCP‑aware client—Claude, Cursor, the CLI itself—can reuse them. That’s why Claude never asked for credentials later: it simply piggy‑backed on the helper’s cached token and sailed straight into my account.

Attempt B — Cursor IDE (dev focus)

Setup + challenges

1. Asked Cursor to “configure this MCP server.” It obligingly wrote ./mcp.json—wrong place. I relocated it to ~/.cursor/mcp.json, toggled the switch under Preferences → Cursor Settings  →  MCP. Tool list appeared.

   
   

   

   This was a happy moment

   
   

What we actually did

• Prompted Cursor to build a React front‑end. It scaffolded Vite + TypeScript but defaulted to raw REST calls. I said, “Use the Wix SDK".

• It built a front end no problem but Cursor was running into some challenges implementing the SDK. It insisted it didn't need some critical code:

  
  

  

  Let me in on the shrooms this LLM was taking

• Switched over to Gemini and with some coxing induced some epiphanies regarding the need for @wix/data

• Re‑ran npm run dev—the build succeeded error free!

4 | How long did it actually take?

• Config wrangling: ~12 minutes (most of it chasing a hidden Unicode character).

• No‑code site ops via Claude: about 8 minutes for three prompts.

• Headless scaffold inside Cursor: 10 minutes from first prompt to compiling React.

• Debug loop, model swap, env vars: another quarter‑hour.

  
  

Grand total: roughly ten lines of real typing across both attempts.

Total human effort: maybe ten lines of real typing across both attempts.

Call it forty‑five minutes from blank slate to a working headless front‑end—plus a brand‑new Wix store humming in the background.

Watch the both attempts in full here

5 | Five hard‑earned lessons

1. The LLM you pick changes everything. Claude Sonnet hallucinated SDK calls; Gemini Pro parsed the docs correctly. Keep model‑hopping in your toolbox.

2. Docs quality matters more than ever. An MCP server is only as smart as the documentation it exposes—typos or stale endpoints send the agent into hallucination loops.

3. Leave the approval toggles on. It’s too easy to publish or delete something when the agent is one click away from full access.

4. MCP ≠ magic. For complex headless work you still need to know your way around env files and basic debugging. The agent turbocharges you; it doesn’t replace you—yet.

5. Watch for invisible characters. Copy‑pasting JSON snippets straight from docs can smuggle hidden Unicode glyphs that break the config. Drop everything through a code editor or formatter first.

   
   

6 | So, should you care?

If you build sites for a living: spinning up demos is suddenly a half‑day exercise, not a week‑end sprint.If you manage dozens of client stores: imagine telling Claude, “apply 10 % off everything till Monday,” and going for coffee.If you’re deep into custom dev: the headless scaffold still needs your brain for auth and CORS quirks, but the boilerplate disappears.

7 | Wix MCP is Here, What Next? 🚀

Within a couple of years the drag‑and‑drop editor could shift from “where you build” to “where you inspect.” If an AI can place, resize and restyle elements from text, human designers might dip into the canvas only for pixel‑perfect touch‑ups or brand sign‑off. Wix’s real moat would then be its business APIs—auth, payments, contacts, content—not the visual builder itself. If the editor can't be controlled by AI, it risks becoming obsolete.

A not so far future might look something like this: 

1. An agent monitors rival prices via public APIs.

2. It tweaks your Wix Store discounts through MCP calls.

3. It fires a Rescue email campaign through the CRM.

4. It tops up a Google Ads budget via yet‑another MCP wrapper.

5. The loop repeats every hour—no human in the chain.

   
   

There may be danger ahead: That future demands MCP firewalls, signed tool policies, and warnings before critical actions; otherwise a poisoned or (just ill drafted) prompt could silently empty a store’s payout balance. Will we get more control over the MCP with AI settings and permissions in our Wix accounts?

Bottom line: MCP isn’t a cute plugin. It’s a fault‑line. On one side lie traditional site builders; on the other, AI‑native app fabrics. Wix just jumped hard to the latter. Can it keep going?