Every Wix site has its own built-in MCP (Model Context Protocol) server. Anyone can connect their compatible AI agent to the MCP server of any Wix site. This allows users and site visitors to interact with Wix sites through AI, using natural language requests.
The site MCP server makes it easy for visitors to:
Get business details like contact information and location.
Discover the products and services the business has to offer.
Book services and make reservations.
Start a purchase process and be directed to the site to complete checkout.
Learn about a business by getting relevant answers to questions, instead of having to search the site.
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 MCP clients to 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 client 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 in order 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 do not 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 client on how to use the APIs.
Use this tool for querying products and services on a site (instead of SearchInSite).
Parameters:
searchTerm | The term to search for the site API documentation. |
Retrieves business and site details such as timezone, email, phone, address, etc.
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 client 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 client 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.