Wix MCP Server

The Wix MCP server connects AI assistants to the Wix platform. Anyone who runs a website, online store, or booking site on Wix, or builds them for clients, can give the assistant tasks like "Give all products in the store 15 percent off for one week", "Create a data collection for contact labels", or "Show me example code to block a member". The assistant does not just suggest code: according to the vendor it can search the matching documentation, look up the exact APIs, and run calls against the selected Wix site. The server is operated by Wix itself.

What is the Wix MCP server?

The server implements the Model Context Protocol (MCP), an open standard through which AI applications talk to tools and data sources. Wix provides it as a hosted remote server at https://mcp.wix.com/mcp. Clients that do not support remote MCP directly can, according to the documentation, use the bridge package @wix/mcp-remote via npx; that requires Node.js version 19.9.0 or higher. Whether you enter http or sse as the transport depends on the client. The documentation names Claude, Cursor, Copilot, and Windsurf among the clients; automation tools such as n8n can be connected as well.

Which tools the server brings

According to the tool list in the documentation, all of which are enabled by default, the server falls into three groups. First, documentation: there are search tools for the REST documentation, the SDK documentation, the Wix Design System, the guides on building apps, and the headless offering, plus tools to read whole articles or the exact request and response schemas of an API. Second, sites: the assistant can list the sites of an account, fetch a site's context with its installed apps, run single REST calls for a selected site, or chain several calls in a script and page through results. According to the documentation the latter is the default route for business data such as bookings, store, or CMS. Third, management: a dedicated tool performs account-level actions such as creating, updating, or publishing a site, and another uploads images to a site's media manager. A starter tool picks the right tool or recipe for the task, and a feedback tool completes the set.

What it is concretely good for

The official examples range from site maintenance to development. On the operational side Wix names creating discounts and coupons, building data collections with fields marked as personal data, adding staff members in the bookings app, listing and booking services, sending messages to customers, and creating and publishing blog posts. On the development side the server helps set up a Wix headless project, write login pages, event registrations, or list views from the CMS, and generate example code for the APIs in languages such as Node.js or Python. The advantage over simply reading the documentation: the assistant does not have to guess the right API but looks it up, and can run the call in the same conversation.

Setup and sign-in

You need a Wix account. The simplest variant is browser sign-in: you enter the address of the remote server in the client and sign in to Wix on first connect. For Cursor the documentation offers an install link that applies the configuration. Alternatively the server can be addressed with an API key and the account ID as headers, which is meant for n8n or agent-to-agent scenarios. If the connection drops after a long pause or after switching accounts, the documentation recommends deleting the locally stored sign-in folder .mcp-auth and signing in again.

Security and limits

The server is not merely a reference. According to the documentation it can create and publish sites, install apps, and change business data on a real site through the API, such as products, coupons, bookings, or posts. Wix itself points out that depending on your instructions the client may change local code files or the live site, and recommends turning off auto-run mode in the client so that every tool execution needs your approval first. Take that seriously for production sites: phrase tasks precisely, name the site and the Wix app explicitly, and test flows on a development site first. Also keep in mind that customer data the assistant queries enters the language model's context and thereby reaches the model provider. If you use an API key, give it only the permissions it needs.

Costs

The documentation does not bill the MCP server separately. By Wix's own account there is a free start where a website can be created without a credit card, alongside paid Premium plans with a custom domain and without Wix branding, and enterprise solutions for large projects. Which Wix apps you use on the site determines which functions and costs the assistant can trigger at all. Current terms are on the official pricing page. Costs of your AI client may come on top.

Who is the Wix MCP server for?

It is worthwhile for agencies and freelancers who maintain several Wix sites, for store and booking operators who want to handle recurring maintenance by conversation, and for developers building Wix apps or headless projects who want a reliable link to the documentation. Anyone not using Wix gains nothing. If you only change content now and then, the editor often gets you there just as quickly; the benefit shows with bulk changes, chained calls, and development against the APIs.

A Wix account and an MCP client that supports remote servers; for clients without remote support Node.js version 19.9.0 or higher.

The Wix MCP server runs hosted by Wix. This guide walks through setup, sign-in, and the first tasks without letting an assistant accidentally change your live site.

Step 1: Prerequisites

You need a Wix account with at least one site and an MCP client that supports remote servers. Clients without remote support need Node.js version 19.9.0 or higher.

Step 2: Set up in Claude Code

Run claude mcp add --transport http wix-mcp-remote https://mcp.wix.com/mcp and then call /mcp in Claude Code to complete the Wix sign-in in the browser.

claude mcp add --transport http wix-mcp-remote https://mcp.wix.com/mcp

Step 3: Set up in Cursor

Use the install link from the Wix documentation or enter a server in the MCP configuration with type set to http and url set to https://mcp.wix.com/mcp. To sign in with an API key, add the headers Authorization and wix-account-id.

Clients without remote support

Enter npx as the command with the arguments -y, @wix/mcp-remote@latest, and https://mcp.wix.com/mcp. If startup fails, check the Node version and the full path to Node. After switching accounts it helps to delete the .mcp-auth folder in your user directory.

Work safely

Turn off auto-run mode in the client so every tool execution needs approval first. Name the site and the Wix app in every task, for example "Wix Stores on the site Party Costume Store". Try tasks on a test site first and give API keys only the permissions they need.

Step 4: First tasks

Start read-only: have the sites of your account listed or the services of a site shown. After that a small change such as a draft for a blog post is a good next step. For development, ask for example code for an API and state explicitly which file it should be written to.

Sign-in to the Wix account in the browser (default) or an API key in the Authorization header together with the account ID in the wix-account-id header.

Documentation search, listing sites, REST calls on selected sites (read and write), account-level management such as creating, updating, and publishing sites, and uploading images. Permissions follow the account or the API key.

The server runs hosted by Wix. Site data that is queried enters the AI client context and therefore reaches the model provider.

Write changes to live sites (prices, coupons, bookings, publishing), unexpected changes to local files in auto-run mode, overly broad API keys, and customer data reaching the model provider.