Installation guide

How to install Wix MCP Server

Q: The tools can read site data but I get unexpected results with account actions. Why?

ManageWixSite works only at the account level, for actions like creating, updating or publishing a site, and cannot read or write per-site business data. For Stores, Bookings or CMS data, the client should use CallWixSiteAPI or ExecuteWixAPI with a site ID. Ask it to run ListWixSites first.

In Claude, ChatGPT, Gemini, Microsoft Copilot, Perplexity, Cursor and Claude Code, with what to check before you start and the first prompts to run.

The Wix MCP server is hosted by Wix at `https://mcp.wix.com/mcp`. Clients that support remote MCP connect by URL and sign in to Wix through the browser (OAuth). Clients that do not support remote MCP can use the `@wix/mcp-remote` package through `npx`, which needs Node.js 19.9.0 or higher. An API key plus Wix account ID is also supported, mainly for tools like n8n.

The person who connects it should be a Wix account owner or a collaborator with access to the sites to be managed, signing in with that Wix account. The server can change a live site (publish, edit store data, upload media), so start with read-only questions and approve write actions one at a time.

Wix MCP Server setup guide: Wix's MCP documentation page on dev.wix.com, shown in a browser frame (store platform MCP server for e-commerce) — Wix MCP Server setup guide preview: Wix’s documentation on dev.wix.com, captured Oct 13, 2026. The page may have changed since; the link opens the live version.

Before you start

A Wix account with access to the site or sites you want to work with.
Node.js 19.9.0 or higher, required for the npx @wix/mcp-remote@latest route (clients without remote MCP support).
An MCP client that can add a remote server by URL, or one that can run a local npx command.
Optional: a Wix API key and your Wix account ID, only if you authenticate without OAuth (for example n8n, or Cursor with an API key). Take the exact way to create them from the Wix documentation.
A test or staging site, if available, for your first supervised write actions.

How it runs: Remote, added by URL
Access: Varies by tool
Server address: https://mcp.wix.com/mcp

Wix MCP Server in Claude

Open Claude.ai in the browser or the Claude Desktop app and go to Settings > Connectors.
Choose the option to add a custom connector and enter the URL https://mcp.wix.com/mcp. The Wix docs link to separate instructions for Claude Web and Claude Desktop, so check those pages if your menu differs.
Save the connector and complete the Wix sign-in in the browser window that opens.
Choose the Wix account that owns the sites you want to use.
Start a new chat, enable the Wix connector, and run a read-only prompt first.

Connector URL

https://mcp.wix.com/mcp

Wix MCP Server in ChatGPT

The Wix docs do not cover ChatGPT, so use ChatGPT's standard route for custom MCP servers.
Enable Developer mode in ChatGPT settings, then open the connectors area and add a custom MCP connector.
Enter https://mcp.wix.com/mcp as the server URL and choose OAuth if asked for an authentication method.
Complete the Wix sign-in and select the right Wix account.
In a new chat, enable the connector and start with read-only questions. Confirm current menu names in OpenAI's documentation.

Server URL

https://mcp.wix.com/mcp

Wix MCP Server in Gemini

The Wix docs do not mention Gemini. For Gemini CLI, use its standard mcpServers block in the settings JSON file.
Because remote support varies by client, the safe choice is the npx entry that uses @wix/mcp-remote@latest, which needs Node.js 19.9.0 or higher.
Add the entry below to your Gemini CLI settings file and save it.
Restart Gemini CLI and complete the Wix sign-in in the browser when prompted.
Run a read-only prompt to confirm the Wix tools load.

Gemini CLI settings (mcpServers)

{
  "mcpServers": {
    "wix-mcp-remote": {
      "command": "npx",
      "args": [
        "-y",
        "@wix/mcp-remote@latest",
        "https://mcp.wix.com/mcp"
      ]
    }
  }
}

Wix MCP Server in Microsoft Copilot

The Wix docs list VS Code and Copilot as supporting remote MCP, with separate VS Code instructions. They do not cover Copilot Studio.
For GitHub Copilot in VS Code, create or open .vscode/mcp.json in your workspace.
Add a server entry with the URL https://mcp.wix.com/mcp, as shown below.
Start the server from the MCP controls in VS Code and complete the Wix sign-in in the browser.
For Copilot Studio, add an MCP tool or custom connector using the same URL, and check Microsoft's documentation for the exact steps.

.vscode/mcp.json

{
  "servers": {
    "wix-mcp-remote": {
      "type": "http",
      "url": "https://mcp.wix.com/mcp"
    }
  }
}

Wix MCP Server in Perplexity

The Wix docs do not cover Perplexity, so use the standard way to add a connector in the Perplexity desktop app.
Open the Perplexity app settings and find the connectors section for adding a custom or remote MCP server. Availability depends on your plan and version.
Enter https://mcp.wix.com/mcp as the server URL.
Complete the Wix sign-in in the browser and select the correct Wix account.
Ask a read-only question to confirm the connection.

Server URL

https://mcp.wix.com/mcp

Wix MCP Server in Cursor

Without an API key, the Wix docs say you no longer need to edit config manually. Use the install button in the Wix docs, or add Wix MCP from the Cursor MCP library.
To configure it by hand, open Cursor MCP settings and edit the mcp.json file.
Add the entry below, then save.
Complete the Wix sign-in when Cursor prompts you.
If you want API key authentication instead, use the headers variant from the Wix docs with Authorization and wix-account-id.

Cursor mcp.json

{
  "mcpServers": {
    "wix-mcp-remote": {
      "type": "http",
      "url": "https://mcp.wix.com/mcp"
    }
  }
}

Wix MCP Server in Claude Code

Open a terminal.
Run the command below to add the Wix server over HTTP.
Start claude and run /mcp to see the server status.
Complete the Wix sign-in in the browser if the server asks for authentication.
Run a read-only prompt to confirm the tools are available.

Terminal

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

Check that it works

Start with questions that only read data. If these answer from your real account, the connection is good.

List my Wix sites.
Get the site context for my site named <site name> and tell me which apps are installed.
Search the Wix REST documentation for how to query products in Wix Stores. Do not make any changes.

Troubleshooting

+The server fails to start or shows errors in my client. What should I check?

Check the IDE logs first. Confirm Node.js 19.9.0 or higher is the default on your path, the `npx` arguments are correct including `-y`, and try the full path to Node. Restart the IDE. You can also run `npx -y @wix/mcp-remote@latest https://mcp.wix.com/mcp` directly in a terminal.

+Sign-in loops, or the connection dropped after a while or after switching Wix accounts. How do I reconnect?

In your client's MCP settings, find the Wix server, log out, then log in again. If that does not work, delete the cached auth folder: `~/.mcp-auth` on Mac or `C:\Users\<username>\.mcp-auth` on Windows. Then restart the client and sign in with the intended Wix account.

+The tools can read site data but I get unexpected results with account actions. Why?

`ManageWixSite` works only at the account level, for actions like creating, updating or publishing a site, and cannot read or write per-site business data. For Stores, Bookings or CMS data, the client should use `CallWixSiteAPI` or `ExecuteWixAPI` with a site ID. Ask it to run `ListWixSites` first.

Written Oct 13, 2026 from the vendor documentation. Exact menus, addresses and commands change; the official documentation is the source of truth.