Every Wix site has its own built-in MCP server. MCP stands for Model Context Protocol. Anyone can connect a compatible AI agent to the MCP server of any Wix site. This lets site owners and site visitors interact with the site through AI, using natural language requests.
The endpoint belongs to the Wix site, not to a particular editor. Studio Two, Wix Studio, Wix Editor, and Wix-managed headless sites each expose it on the site domain. A self-managed headless project exposes it on the Wix site, not on the frontend hosted outside Wix.
Note: An AI agent that connects to the site's MCP server from outside the browser acts as an anonymous site visitor. It can only see and do what a regular visitor can on the live site, so it doesn't access password-protected pages, members-only areas, or private backend data. The Wix WebMCP is the in-browser path. After a member logs in, that agent gets the member's experience.
The site MCP server makes it easy for visitors to:
Every Wix site has a unique endpoint, but they all use the following format:
In your code, replace <wix-site.com> with the domain of the site you want to connect to. For example, if you want to communicate with the MCP server of https://andream.wixsite.com/andreas-kitchen, the endpoint is:
Make client requests as POST calls that follow MCP architecture. You don't need to include authentication for site MCPs.
For example:
Wix site MCP servers make the following tools available to AI agents that interact with a site.
Fetches a complete article from the Wix developer documentation portal.
Parameters:
articleUrl | A string in uri format that contains the URL of an article in the Wix developer documentation portal. |
Fetches the full schema for a Wix API method. The agent should call this before calling the actual method.
Parameters:
articleUrl | A string in uri format that contains the URL of a reference article for a Wix API method. |
Calls API methods on a site to perform actions on a site visitor's behalf, such as querying site data or booking an appointment.
Parameters:
visitorToken | Visitor access token. If you have this in context, always use it and don't create a new one. If you don't have it in your context, use the GenerateVisitorToken tool to get it. |
url | A string in format uri that contains the URL of the API method to call. Retrieve this URL using the SearchSiteApiDocs tool or from the conversation context. Must be an absolute URL. Typically starts with https://www.wixapis.com. |
method | The HTTP method to use for the API call. |
body | A string representing the request body as a valid JSON object. |
Creates a new visitor session and obtains a visitor access token for the site. If you don't have a visitor token yet, use this tool before making a tools/call request with CallWixSiteAPI.
Retrieves the API documentation for the Wix business solutions installed on a site, and informs the agent on how to use the APIs.
Use this tool for querying products and services on a site. Use SearchInSite to search page content.
Parameters:
searchTerm | The term to search for the site API documentation. |
Retrieves business and site details such as time zone, email, phone, and address.
Searches the site for information.
Parameters:
searchTerm | The term to search for in the site. |
You can also make a tool discovery request from your agent to retrieve the list of tools.
The tools/list call returns the name, description, and input schema of each tool.
Note: The MCP server notifies your agent when the tools are updated. To receive the latest tool updates, make sure to implement a tools/list call upon receipt of a tool update notification.
Last updated: 10 November 2026