Connect Wix to Claude Code

Have Claude update products and move orders in Wix. From the terminal, inside the sessions where you already work.

How do you connect Wix to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Wix, you add a Wix MCP server: a small hosted service that exposes Wix's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Wix account. No API keys pasted into config files.

claude mcp add --transport http wix https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Wix once connected?

Full read-write Wix access lets Claude update product titles, prices, and descriptions, adjust inventory quantities, edit order fulfillment status, manage collections, and prepare listing drafts for your review. The catalog and order work that used to mean clicking through the Wix dashboard happens where the store already runs, with your approval.

Update a product's title, description, price, or SKU in Wix Stores
Adjust inventory quantities for a product or its variants
Update an order's fulfillment status or write custom metadata to its extended fields
Draft a new product listing for you to review before it publishes
Organize products into a collection to support a sale
Pull orders matching a query and propose batched updates

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Wix access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Wix API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Wix changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Wix connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Wix connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Wix account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Wix's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Wix?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Wix account it signs in with. Revoking access is one click in Wix.

More on the Wix connector

Wix connector for claude.ai Ecwid + Claude Code Etsy + Claude Code Amazon Seller Central + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us