Wix provides a Model Context Protocol (MCP) server that allows you to work with Wix tools and services in your chosen AI client. By configuring the Wix MCP server, you enable your client to search the Wix documentation, write code for the Wix platform, and make API calls on Wix sites. This saves you the time and effort of finding and applying the information in the documentation yourself.
For examples on how to use the Wix MCP server, see our sample prompts.
Note: The Wix MCP is also available as a built-in connector in Claude. If you're using Claude, you can access all Wix MCP tools without any additional configuration.
This section shows you the basic configuration you need to add to your AI tool to use the Wix MCP server. Watch our video to see a demo of how to set up the MCP:
Wix provides multiple ways to configure the Wix MCP server. In most cases, you need to manually add one of the following JSON objects to your MCP server configuration file:
For tools that support remote MCP:
The supported values for the type field are "sse" and "http". The type you select depends on your agent. Agents that support remote MCP include Claude, Cursor, GitHub Copilot, Windsurf, and Claude Code.
For tools that don't support remote MCP:
You can also authenticate to the MCP using an API key and your Wix account ID. This is useful for tools like n8n.
To authenticate with an API key, use one of the following configurations:
For tools that support remote MCP:
The supported values for the type field are "sse" and "http". The type you select depends on your agent. Use this configuration to set up the MCP in n8n, or in Cursor if you want to authenticate with an API key.
For tools that don't support remote MCP:
Depending on your client, you may be able to configure the MCP server through the client settings, or even ask the client itself to add the configuration.
If you're working with Claude Code, run the following command to add the Wix MCP:
You can also add the configuration manually to your ~/.claude/settings.json:
If you're working with Cursor and not using an API key to authenticate, you no longer need to configure the MCP manually. Click below to install the Wix MCP.
You can also add the Wix MCP from the Cursor MCP library.
For other agents, see their MCP setup documentation:
The Wix MCP provides tools for the following sorts of actions, all enabled by default:
When you connect the Wix MCP to your AI client, you can ask your client to list the available tools at any time.
Share your feedback
Want to share feedback about your MCP experience? Tell your AI client to submit feedback to Wix. The client will prompt you for your message and send it directly to us. We review all feedback as part of our ongoing effort to improve.
If you're getting errors when running the MCP server, try the following:
Check the IDE logs.
Check if the error is related to your package manager. Make sure you have the latest node version as the default on the path.
Check that you entered the npx arguments correctly in the configuration. Make sure you included -y and the correct npm registry.
Include the full path to Node.
Restart the IDE.
Locate the MCP server in your IDE settings and log out, then log back in to reconnect to the server.
Run the MCP server directly on the command line:
The connection to the server may be lost after a long period of inactivity, or if you switch the Wix account you're authenticating with. In that case, it may help to delete ~/.mcp-auth (on Mac) or C:\Users\<username>\.mcp-auth (on Windows).
If the server still isn't working, check the MCP debugging guide for more help.
Last updated: 31 August 2026