How to use Claude Code with a Wix site

Claude Code can work on a Wix site in two ways. It can connect to the Wix MCP server, which lets it search Wix's developer docs, write code for the Wix platform and call Wix APIs on your sites, including creating, updating and publishing them. Or, for Wix Editor and Wix Studio sites with custom code, it can edit that code on your computer through Wix's GitHub integration and the CLI for Sites, with a person previewing and publishing.

What you can do depends on the kind of Wix site you have. Wix Editor and Studio sites support site code. Wix Harmony, Wix's AI-powered editor, doesn't, apart from small HTML, JavaScript and CSS snippets. And a headless project, where Wix runs the business back end and you build the front end, is a normal code project that suits Claude Code well. This guide covers each case as Wix documents it in October 2026.

Which kind of Wix site do you have?

Start here, because it decides what Claude Code can touch. Wix's site types page lays out the differences.

Wix also points out that on Editor and Studio sites, "Frontend code works through Wix's APIs rather than the DOM." Generic JavaScript that manipulates page elements directly isn't how Wix site code works. Put that in your CLAUDE.md so Claude uses Wix's APIs.

Setting up the Wix MCP in Claude Code

MCP (Model Context Protocol) is an open standard that lets Claude call tools in other systems. The Wix MCP page says the server lets your AI client "search the Wix documentation, write code for the Wix platform, and make API calls on Wix sites."

1. Check Node.js. Wix asks for Node.js 19.9.0 or higher.
2. Add the server. Run claude mcp add --transport http wix-mcp-remote https://mcp.wix.com/mcp.
3. Sign in. Run /mcp in Claude Code, select the Wix server and log in with the Wix account you want it to use.
4. List the tools. Ask Claude to list the Wix tools it can call. Wix says you can do this at any time.
5. Add ask rules for writes. Because publishing is enabled by default, set ask rules so Claude Code stops and asks before it calls site-changing or publishing tools. Wix's page doesn't list tool names, so read them in /mcp first. If you can't tell which tools write, put the whole server behind one ask rule, mcp__wix-mcp-remote. Our guide to MCP servers for website teams explains rule scoping.

Wix also offers the same server through npx @wix/mcp-remote@latest for clients without remote MCP support, and the Wix MCP is a built-in connector in Claude's chat app. Wix's page also suggests adding the configuration by hand to ~/.claude/settings.json. Claude Code's own docs keep MCP servers in other files, so use the claude mcp add command instead. If a connection drops after a long idle period, Wix suggests deleting the ~/.mcp-auth folder and signing in again.

Don't confuse this with the Wix Site MCP. Wix says every Wix site has its own built-in MCP server for visitors, at your site's address plus /_api/mcp, and a client that connects to it "acts as an anonymous site visitor." That's for shopping and booking agents, not for building your site.

Wix shows no beta or GA label for the Wix MCP. Anthropic doesn't security-audit or manage any MCP server, so review what the server can do before you connect a live account.

Editing site code with GitHub and the CLI for Sites

For Editor and Studio sites with custom code, the safest Claude Code workflow uses Wix's Git integration. Your site code lives in a GitHub repository, so every change Claude makes is a diff a person can review. Note that Wix has two CLIs: "The CLI for Sites is a different tool from the Wix CLI used for apps and headless projects."

1. Connect the site to GitHub in Wix's Git integration, then clone the repository to your computer.
2. Create a branch for the change. If git is new to you, read git basics for Claude Code first.
3. Write a short CLAUDE.md with the site's rules: use the Wix JavaScript SDK, work through Wix's APIs rather than the DOM, and never run wix publish.
4. Plan, then edit. Ask Claude to propose the change in plan mode before it edits files.
5. Preview locally. wix dev "Opens a site's Local Editor," which syncs with your local changes in real time.
6. Build a preview. wix preview creates a shareable version of the site. It works only if the site has been published before.
7. Review and merge. A person reviews the diff and the preview, then merges into the default branch.
8. A person publishes. Run wix publish from the default branch, or publish from the editor.

Two details from Wix's CLI for Sites reference matter here. First, wix publish can publish either the repo's default branch or your local code. Publishing local code puts the live site and the repo out of sync, and a later publish from the repo can overwrite and lose that local code. Always publish from the reviewed branch. Second, a preview "uses the live versions of any HTTP functions exposed on your site," so it can't test changes to those functions. Wix suggests functional testing in the editor for that.

Wix also offers test sites, "a separate published copy that doesn't affect your live site." Some features, such as backend events and scheduled jobs, only run on a published site. For changes that touch them, a test site is the honest check. Our guide to setting up a staging copy explains why a copy comes first.

Velo or the SDK?

Wix site code can use the Velo API or the newer Wix JavaScript SDK. Wix now says "You can now use the Wix JavaScript SDK instead of the Velo API for most functionality" and encourages the SDK "in all new and ongoing development projects," while existing Velo code "will continue to work." Some Velo APIs don't have an SDK equivalent yet.

For Claude Code, that means two things. Tell it which one your site uses, in CLAUDE.md, so it doesn't mix them. And when it writes new code, ask it to check Wix's docs through the MCP rather than relying on what it remembers, since the naming has changed. Wix's own docs still title one section "Extend Websites with Velo," so expect both names for a while.

Headless Wix and Wix apps

A headless project is where Claude Code is most at home on Wix. Wix describes headless as a way to "build a custom frontend on any stack you choose and power it with production-ready Wix business APIs." Your front end is ordinary code in git, so the usual Claude Code workflow applies: branches, plan mode, tests, previews and reviewed merges.

• Wix-managed headless is what Wix recommends for most projects. Wix hosts it, and Astro is the recommended framework with full integration. Wix says frameworks whose server output can't run on Cloudflare Workers aren't supported.
• Self-managed headless is for when you need your own hosting or an existing app. You handle hosting and deployment.
• Apps use the Wix CLI, which "scaffolds new projects, generates extensions, runs a local dev server, and deploys code to Wix's cloud."

Wix's development docs don't state plan requirements for headless or the Wix CLI, so confirm with Wix for your account. If you're comparing headless options more broadly, see Claude Code with a headless CMS.

Good jobs and poor fits

If your site has no custom code and you're happy in the editor, you may not need Claude Code at all. Our comparison of Claude Code and website builders covers that choice, and our Wix hub has more on the platform itself.

Safety basics for Wix work

• Keep publishing human. Both the MCP and the CLI can publish. Use ask rules and say so in CLAUDE.md.
• Use the right account. Connect the MCP with an account whose access fits the job, not an owner account with access to every site.
• Keep secrets out of prompts. Wix has a Secrets Manager for API keys. Don't paste keys into chat or CLAUDE.md.
• Check customer data handling. Wix's MCP can call APIs on business data such as stores and bookings. Read whether Claude Code is safe for a live website before connecting it to a site with real customers.

Conclusion

On Wix, Claude Code is most useful where there's real code: Editor and Studio sites with custom code kept in GitHub, headless front ends and Wix apps. Connect the Wix MCP for docs and API work, add ask rules because publishing is on by default, preview with wix dev and wix preview, and publish from the reviewed default branch. On Harmony sites, expect to work through the MCP, not code. If you'd like help with a custom Wix build or a headless project, see our Claude Code development services. More guides are in our Claude Code Guide.

Frequently asked questions