Wix MCP

Questions & Answers

What is the Wix MCP?

The Wix MCP is a server run by Wix that lets an AI assistant work directly with the Wix platform. It is built into Claude as a connector and also works with tools like Cursor, GitHub Copilot, Windsurf and Claude Code. Once connected, the assistant can read the real Wix documentation, write code against the Wix APIs, and take real actions on a live site.

What can the Wix MCP actually do?

Four things. It searches and reads the Wix developer docs, it writes REST or SDK code for the platform, it calls APIs to take real actions on your sites such as updating SEO tags or adding a bookings staff member, and it manages sites, apps and projects at account level like creating and publishing sites.

Can the Wix MCP change a live Wix site?

Yes, and that is both the point and the risk. The actions it takes are real and they hit the live site, so it is a tool for people who understand what they are changing. I used it to rewrite the titles, meta descriptions and structured data across fifteen live pages in one session.

Can it change my page titles, and what about my headings?

It can set titles, meta descriptions, canonical links, social tags and structured data, the things in the head of the page. It does not touch the visible content, so your H1 and your on-page section headings are not controlled by it. Those stay in the Wix Editor.

What is the biggest risk with the Wix MCP?

On a classic Wix site, publishing a change through the API updates only the live version, not the saved draft. So a routine publish from the Editor can quietly push the old draft back over your work. The fix is to write every change to both the live version and the draft so an Editor publish cannot undo it.

Who is the Wix MCP for?

The documentation and code tools help any developer building on Wix. The parts that take live actions reward agencies and specialists making the same changes across many sites. For a casual owner making the odd change, the dashboard is safer.