By Ira Bodnar, Ryze AI · Updated · Connector tested November 19, 2026
Quick answer
The main way to connect Grok to Wix is the Ryze AI connector. Connect the Wix site in Ryze AI with an API key and the Site ID, then open grok.com/connectors, choose New Connector and Custom, paste https://connector.get-ryze.ai/mcp and sign in to Ryze AI when Grok asks. Grok then has 3 Wix tools for that site: one that reads, one that writes and one that deletes.
- Wix: install the Wix Blog app, create an API key in Account Settings and copy the Site ID from the dashboard URL
- Ryze AI: Integrations, Connect on the Wix card, then enter the API key and the Site ID
- grok.com/connectors: New Connector, Custom, paste the connector URL
- Ryze AI page: sign in, pick the workspace, press Allow connection, then open a Grok chat
Grok to Wix at a glance
| Fact | Detail |
|---|---|
| Main way to connect | Ryze AI's hosted MCP connector, which Grok takes by URL as a custom connector |
| Address to paste | https://connector.get-ryze.ai/mcp, the same for every account |
| How Grok signs in | After the URL, Grok asks you to finish authentication. You sign in on the Ryze AI page and press Allow connection |
| Wix tools in Grok | 3 in total: wix__read, wix__write and wix__delete. The names come from the Ryze AI app source and were not seen in a live tool list |
| Can Grok change the site | Yes, through the write and delete tools, within what the API key allows. xAI describes no confirmation step on grok.com; Grok Bot shows an approval card when Auto Review wants your OK, and Grok Build asks first by default |
| Other data in the same Grok chat | Tools for the other platforms connected in the same Ryze AI workspace come from the same address |
| Grok plan | xAI makes connectors available to all Grok users. On The X Subscription, Grok Bot comes with Premium, Super and Ultra, and Plus leaves it out |
| Ryze AI price | Free to add. The Wix tools run on any active plan or trial, and SEO Starter is $129 per month with a 3-day free trial |
| Wix's own option for Grok | The Wix MCP server at https://mcp.wix.com/mcp. Wix's pages name Claude, Cursor, GitHub Copilot, Windsurf and Claude Code, and do not name Grok. It was not tested with Grok |
| Wix access of the connection | A Wix API key plus the Site ID. The minimum to connect and publish is Blog, Media, Members and Site read. Data and Stores add collections and store products |
| Last tested | Connector checked from outside on November 19, 2026. No Wix site was connected and no step was run inside Grok |
Before you start
- A Grok account, Grok Bot or Grok Build. xAI says connectors are available to all Grok users, and its connectors page names no separate plan for custom MCP servers. On Grok Business and Enterprise an admin has to add the connector in console.x.ai before members can use it. Grok Bot is its own app that signs in with a Cursor account; Premium, Super and Ultra on The X Subscription include it, while Plus does not.
- A Wix API key and the Site ID. Only an account owner or co-owner can create an API key in Wix Account Settings. The site needs the Wix Blog app, because Ryze AI refuses the connection without it. The Site ID is the part of the site dashboard URL after /dashboard/, and the Account ID does not work in its place.
- An active Ryze AI plan or trial. Adding the connector is free, yet the 3 Wix tools answer only on a plan or trial. SEO Starter is $129 per month with a 3-day free trial and publishes Content Plan articles to the Wix Blog. Agency is $279 per month. Paying yearly takes 30% off the first year.
How to connect Grok to Wix on grok.com
Steps 1 and 2 take place in Wix and Ryze AI, steps 3 to 5 in Grok. Every account pastes the same address.
Create an API key in Wix and copy the Site ID
Check that the Wix Blog app is on the site. In Wix open Account Settings, then API Keys, press Generate API Key and name it. Leave Sites on All sites or include this one, tick All permissions and press Generate Key. Wix then sends a 6-digit code to the account email; enter it and press Verify & Generate Key, then copy the token, which Wix shows once. Copy the Site ID from the dashboard URL, the part after /dashboard/.
Connect the site in Ryze AI
Sign in to Ryze AI, open Integrations and press Connect on the Wix card. Enter the API key and the Site ID, then press Continue.
Add a custom connector on grok.com
Open grok.com/connectors, press New Connector and pick Custom. Paste https://connector.get-ryze.ai/mcp as the server URL. xAI accepts only servers its own systems can reach over the public internet, and this address is one of them.
Sign in to Ryze AI and allow the workspace
Grok then asks you to complete authentication. On the Ryze AI page, sign in, select the workspace that holds the Wix connection and press Allow connection.
Ask Grok about the blog
xAI says Grok discovers the tools a new connector offers and makes them available in conversations. Open a chat and try: List my 10 most recent Wix blog posts with the title, slug and status of each.
On authentication, xAI's connectors page says no more than to complete whatever is required once the URL is in. A second xAI page, on tunneling, says OAuth or API key flows for a custom server run inside Grok. No xAI page mentions dynamic client registration. The sign-in and Allow connection screens belong to Ryze AI, as the Ryze AI help center Grok page shows them, and they were not run on grok.com for this guide. The Wix side is described in the Ryze AI Wix guide. Ryze AI keeps one Wix connection per workspace, and a connection link is refused while one exists. To switch sites, open View on the Wix card, disconnect with the trash icon and connect again. If the Wix tools are missing because you connected the site after adding the connector, delete the connector in Grok, add it again and start a fresh chat.
Grok Business, Grok Bot and Grok Build
Three more places take the same address. The Wix key lives in Ryze AI, so none of them asks for it again.
Grok Business and Enterprise (admin)
Team plans put one step at the front: an admin registers the connector in xAI's console. xAI ties adding and removing connectors to Team Read-Write permissions, which admins usually hold.
- Log in at console.x.ai, choose the team, then open Grok Business and Connectors. One xAI page calls the same menu Grok Enterprise.
- Press + Add Connector, choose Other and paste https://connector.get-ryze.ai/mcp.
- Finish whatever authentication the console asks for.
- xAI's page tells members to link their own accounts at grok.com/connectors after a catalog connector is added. The custom server steps stop at authentication, so confirm with your admin how members reach it.
Grok Bot
Grok Bot is a desktop and phone app of its own, apart from grok.com, and it signs in with a Cursor account. According to the Ryze AI help center, Ryze AI is one of the built-in apps on Grok Bot's Connect apps screen. Ryze AI appears nowhere in xAI's documentation, and nobody checked that screen for this guide, so these steps come from the Ryze AI help center.
- Open Connect apps in the Grok Bot sidebar. In the phone app, tap your avatar in the top left corner and choose Connect apps.
- In the box labeled Search across apps and skills, enter Ryze AI. Open the entry whose developer line reads Ryze AI and press Add.
- A browser tab opens on Ryze AI. Sign in, pick the workspaces and press Allow connection.
- Once Authorization complete shows, press Open Grok Bot or Return to Grok Bot.
- Start a new chat. Typing @ lets you attach the app to the task.
No Ryze AI result in the search? The desktop app has a manual route at the foot of Connect apps, Add a custom connector. Give it a name, pick Remote HTTPS as the Type, put the connector URL in Server URL and press Add plugin. xAI also lets you ask a Bot to add the URL. An app you connect belongs to your account, so every Bot you run can reach the Wix site. If an older hand-added copy of Ryze AI is still installed, the Ryze AI help center says to uninstall it to avoid a double set of tools.
Grok Build CLI
Grok Build, xAI's coding agent for the terminal, registers a remote server with one command.
- Run the command below in a terminal.
- On first use of the server, a browser opens for the Ryze AI sign-in. Finish it there.
- In the terminal interface, /mcps (alias /connectors) opens the MCP tab. Select the ryze server and press i to authenticate it.
grok mcp add --transport http ryze https://connector.get-ryze.ai/mcpGrok Build stores the OAuth tokens in ~/.grok/mcp_credentials.json and namespaces tools as <server>__<tool>, so the Wix tools sit under the ryze server name. When no browser can open the sign-in page, /mcps shows its URL in a panel you can copy, a change from release V1.0.74.
Grok and MCP: the facts in one table
xAI (its documentation now names the company SpaceXSI) runs three products that take MCP servers, each with its own rules. Read across a row to compare them.
| Question | grok.com and team admins | Grok Bot | Grok Build |
|---|---|---|---|
| Where the address goes | New Connector, then Custom, at grok.com/connectors. On team plans an admin first uses + Add Connector, then Other, in the console | The Connect apps screen; for a server outside the catalog, the desktop form or a Bot asked to add it | The command grok mcp add, or a server table written into config.toml under ~/.grok |
| Transports | A public URL. Grok turns down localhost and private network addresses. xAI's tunneling notes mention SSE and Streamable HTTP servers | Remote HTTPS by URL. Command servers start on the cloud machine the Bot works on | HTTP by URL (the settings reference says HTTP/SSE), or stdio for a command on your machine |
| Sign-in | Whatever authentication the server needs, finished in Grok | Provider login in a browser tab, to be done in roughly 10 minutes. Cursor's connector backend keeps the tokens | Browser login on first use, with tokens saved in mcp_credentials.json under ~/.grok |
| Approval before a call | xAI describes none; tools are used when a question touches the service | Auto Review is on from the start and shows a card (Allow once, Always allow, Deny) for actions it wants you to OK | Ask is the starting mode. Allow and deny rules can name MCP tools through the MCPTool filter, and deny wins |
| Plan | Connectors are open to all Grok users | Premium, Super or Ultra on The X Subscription, not Plus | The MCP page names no plan |
| Managing a server later | Back on grok.com/connectors. If a server address changes, delete the old connector and create a new one | Click the connected count next to the Connect apps heading. Each app has Reconnect and Remove, and its tools can be turned off one by one | /mcps: Space switches a server on or off, x deletes it. From the shell, grok mcp remove |
Sources: xAI's Grok connectors, custom MCP tunneling, connector management, Grok Bot apps, Grok Bot approvals, Grok Bot plans, Grok Build MCP servers and Grok Build permissions, checked November 14, 2026. Ryze AI steps: the Ryze AI help center Grok page.
Wix API key access
Grok never sees the Wix API key. Ryze AI keeps it, and three choices made in Wix and Ryze AI decide what Grok can touch.
- The permissions ticked on the key
- Wix says most permissions give read and write access to the site's data, so tick only the areas you need. Ryze AI's help center suggests All permissions as the simple route. Wix describes All permissions as adding every account-level and site-level permission to the key, which is wider than this job needs.
- The sites the key can reach
- A key covers all sites in the account by default or only the sites you pick. A call to a site outside the key's site access is rejected, and site-level calls work only with keys made in the account that owns the site.
- Which site Grok works on
- One Wix connection per Ryze AI workspace, tied to one Site ID. To use a different site, disconnect the Wix card and connect again with the other key and Site ID.
The table maps each permission label that Ryze AI's connect guide names to the Wix scopes that its REST methods ask for. The match between the labels and the scope names comes from each method's page in the API reference, because the API Keys screen in Wix was not opened for this guide.
| Area | Access |
|---|---|
| Blog | Read Blog for List Posts and Query Posts, Read Draft Blog Posts for List and Query Draft Posts, and Manage Blog for Create, Update, Delete and Publish Draft Post |
| Media | Manage Media Manager, which Import File into the Media Manager asks for |
| Members | Read Members, which Query Members asks for |
| Site read | Not matched to a scope on the Wix pages opened. Ryze AI names it as part of the minimum set |
| Data (optional) | Read Data Items for Query Data Items, Write Data Items for Update, Remove and Bulk Insert Data Items, and Manage Data Collections for List Data Collections |
| Stores (optional) | Catalog V3: product read for Query Products and product write for Update Product, which carries the SEO data and slug. Catalog V1 uses Read Products and Manage Products. The Wix Stores app must be installed for the V3 Products API |
Key permissions and what they mean for Grok
Wix has no role ladder for this connection. The key carries the permissions it was given, so the closest thing to a scope list is the set of permissions chosen when you generate the key. Wix's permission types read like this.
| Key permission | What Wix says it does | What it means for Grok through Ryze AI |
|---|---|---|
| All permissions | Adds all available account and site-level permissions to the key | Everything the 3 tools can reach, and more. This is the route the Ryze AI help center suggests, so use a key kept for Ryze AI and rotate it when needed |
| Blog, Media, Members and Site read | Site-level permissions given one area at a time | The minimum Ryze AI documents to connect and publish: blog posts and drafts, with media and members read |
| Data | Site-level permission for the site's Wix Data collections | Needed before Grok can read or edit Wix Data collections and items |
| Stores | Site-level permission for Wix Stores data such as products, orders and currencies | Needed before Grok can read store products or edit their SEO data and slugs |
| Basic permissions | Returns the IDs of the account's sites. Selected by default and cannot be unselected | No action needed |
Not covered: without the Data and Stores permissions on the key, Grok cannot edit store products or collections. The connection is refused when the site lacks the Wix Blog app. Blog bodies written through the tools use Wix rich content (Ricos), not HTML or markdown. Wix documents a 403 Forbidden on an API-key call for a missing permission, a missing site header, a key that is not allowed on that site or a key from an account that does not own the site; that is Wix documentation and not something seen in a Ryze AI test. Whether the Wix Data APIs need the site's code editor switched on, as an app-developer note in the Wix Data docs says, is not stated for API-key calls, so this guide claims neither.
Sources: Wix's API keys help, API key security, authentication methods, permissions and API key calls, checked November 15, 2026. Connection steps: the Ryze AI Wix guide.
Removing access
To take the site away from Grok, remove the connector: delete it at grok.com/connectors, or have the team admin delete it in the console. Grok Bot users press Remove on the app; Grok Build users type grok mcp remove ryze. Ending Ryze AI's own access takes one more step: disconnect the site on its Wix card, then rotate or delete the key from the More Actions menu on the API Keys page in Wix. Rotating or deleting needs the 6-digit email code, and the old token stops working at once.
What Grok can do in Wix
Through Ryze AI, Grok gets 3 Wix tools: 1 that reads, 1 that writes and 1 that deletes. The tool names come from the Ryze AI app source, because no Wix site was connected to confirm them in a live tool list. Writes and deletes are separate tools, so the approval settings of a client can treat them differently.
| Tool | Type | What it does |
|---|---|---|
| wix__read | Read | Reads from the connected Wix site through the Wix REST API, such as blog posts, Wix Data collections and items, and store products. |
| wix__write | Write | Creates or updates resources on the connected Wix site, such as blog draft posts, Wix Data items, and store product SEO data and slugs. |
| wix__delete | Delete | Deletes a resource on the connected Wix site by path, such as a Wix Data item or a blog draft post. |
Whether Grok pauses before a change depends on the product, as the table of Grok facts above shows. xAI describes no approval step on grok.com, so a line such as wait for my yes is an instruction to the model. The chat inside Ryze AI is separate: its Tool approvals picker starts on Skip all approvals, and Approve write & delete or Manual approve make that chat ask first. Article publishing follows Publishing mode in SEO, Preferences, Publishing, which is Automatic by default or Manual. Scheduled tasks run without an approval step.
Wix limits
Wix publishes page sizes, content sizes and data quotas for its Blog, Data and Stores APIs, and the Ryze AI connection calls the Wix REST API with a key, so those per-method figures apply to its calls. No account-wide or per-key REST rate limit figure turned up on the Wix pages opened, which says nothing about whether one exists. Ryze AI adds one limit that holds in every client, Grok included: one Wix connection per workspace.
Limits in numbers
| Limit | Figure | Set by |
|---|---|---|
| Blog posts per request | List Posts and Query Posts return up to 100 published posts, default 50. List Draft Posts and Query Draft Posts take up to 100, default 50 | Wix Blog API |
| Size of a blog | At most 100,000 posts per blog and 400KB per post. A post can sit in up to 10 categories | Wix Blog API |
| Draft post fields | Title up to 200 characters and excerpt up to 500, with up to 10 category IDs, 30 tag IDs and 100 hashtags. A draft without a title cannot be published or scheduled | Wix Blog API |
| Wix Data collections and items | Up to 1,000 collections per site and 500 kb per item | Wix Data |
| Wix Data page and bulk sizes | Query Data Items takes a limit of up to 1000 per page and Bulk Insert Data Items takes up to 1000 items | Wix Data |
| Wix Data request time | 5 seconds for CMS collections on free sites and most premium plans, 10 seconds on Business Elite and Elite Premium, 15 seconds for external database collections | Wix Data |
| Wix Data requests per minute | Free sites: 1000 reads and 60 writes. Legacy premium plans: 3000 reads and 1500 writes. Over quota the request fails with WDE0014. Wix's page names the CMS, datasets and the Velo Wix Data API and does not name REST calls with an API key, so it is unclear whether this applies to Ryze AI | Wix Velo documentation |
| Wix Data read after a write | Reads go to the nearest mirror, so a recent change can take a few seconds to show. consistentRead true reads from the primary instance | Wix Data |
| Store products per request | Query Products takes up to 100 in catalog V3 and up to 100 per page in V1. A product slug is up to 300 characters | Wix Stores API |
| Members per request | Query Members returns up to 100 | Wix Members API |
| API key lifetime | Valid until revoked or rotated. The token is shown once, when the key is created | Wix |
| Request quota for the REST API | No figure on the Wix pages opened | Not stated |
| Grok Bot connector that stops answering | Times out after three minutes, per the release note of August 12, 2026 | xAI |
| Grok Build timeouts | 30 seconds for a server to start, 6,000 seconds per tool call; both are defaults | xAI |
Sources: Wix Blog introduction, Create Draft Post, List Posts, Wix Data introduction, Wix Data consistency, Velo data limits, Query Products and Query Members, checked November 15, 2026; Grok Bot apps, Grok Bot changelog and Grok Build MCP servers, checked November 14, 2026.
First 3 prompts to run
Each prompt says what to ask Grok. Answers come from your own site, and no sample output is shown here because no Wix call was run for this page.
1. List recent blog posts and their status
List my 20 most recent Wix blog posts with the title, slug and status of each, and point out any whose excerpt is empty.
Tools used: wix__read
What comes back: A table of posts with the three fields, and a note on the ones with an empty excerpt. The site is not changed.
2. Create a blog draft from an outline
Create a Wix blog draft with the title and outline I paste below. Leave it as a draft and show me what was saved.
Tools used: wix__write, then wix__read
What comes back: A draft post made through the write tool and a read of what was saved. The tool descriptions cover creating drafts, so ask for a draft and publish it from Wix.
3. Review product SEO text before changing it
Read my store products and list the ones with an empty SEO title or description. Do not change anything until I reply with the new text for each.
Tools used: wix__read, then wix__write once you agree
What comes back: A list of products with empty SEO fields. After your reply, the write tool can update the product SEO data. Needs the Stores permission on the key.
On grok.com the wait in prompts 2 and 3 is an instruction to Grok, since xAI describes no approval step there, so keep it in every prompt that edits or deletes. The prompts change data, so this page shows no result for them.
10 jobs to hand to Grok
Ten jobs to give Grok, each with the Ryze AI tool behind it. Jobs 6 to 10 need the Data or Stores permission on the key. None of the jobs was run for this page, and no Wix call was made.
| Job | What to ask Grok | Tool | On the default connection |
|---|---|---|---|
| Recent posts | List the most recent blog posts with title, slug and status. | wix__read | Works with the minimum key. Up to 100 posts per request |
| Thin metadata check | Find posts whose title is long or whose excerpt is empty. | wix__read | Works with the minimum key. The check runs on the fields that come back |
| New draft | Create a blog draft from an outline I give you. | wix__write | Works with the minimum key. Bodies use Wix rich content (Ricos) |
| Edit a draft | Update the title, excerpt or body of an existing draft. | wix__write | Works with the minimum key |
| Remove a draft | Delete a blog draft I no longer need. | wix__delete | Works with the minimum key. Wix moves a deleted draft to the trash bin unless permanent is set; which one the tool uses is not documented, so do not count on restoring it |
| Browse Wix Data | List the Wix Data collections on the site and the items in one of them. | wix__read | Needs the Data permission on the key |
| Edit a Data item | Change a field on a Wix Data item, such as a title or description. | wix__write | Needs the Data permission on the key |
| Delete a Data item | Delete the Wix Data item I name. | wix__delete | Needs the Data permission. Set approval for this tool where the client offers it |
| Products missing SEO text | Read store products and list those with an empty SEO title or description. | wix__read | Needs the Stores permission on the key |
| Product SEO data and slug | Update a product's SEO data or slug after I approve the new text. | wix__write | Needs the Stores permission on the key |
8 ways to connect Grok to Wix
Eight ways to give Grok access to Wix are worth knowing. The Ryze AI connector is this guide's main way, because one public address goes into grok.com, Grok Bot and Grok Build, the site is connected once in Ryze AI with a key you control, and nothing has to run on your computer. Wix's own hosted server is the closest alternative. Wix's MCP pages name other assistants and do not name Grok, and no way in the table was tested with Grok. Four more options that do not fit follow the table.
| Way | Runs where | How to add it in Grok | What it reaches | Cost |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted. One address for every account | A custom connector with https://connector.get-ryze.ai/mcp at grok.com/connectors, after an admin adds it on team plans. Grok Bot: Connect apps per the Ryze AI help center, or a Remote HTTPS custom connector. Grok Build: grok mcp add --transport http. Then the Ryze AI sign-in | Blog posts and drafts, Wix Data collections and items, and store product SEO data and slugs, through 3 tools and the Wix REST API with the permissions on your key | Connector free. SEO Starter $129 per month, 3-day free trial; any active plan or trial unlocks the tools |
| Wix MCP (Wix's own remote server) | Hosted by Wix | https://mcp.wix.com/mcp. Wix's setup page shows a JSON entry with type http for clients that take remote servers, and by default the agent signs in through your Wix account. Whether grok.com completes that sign-in was not tested | Wix's docs list 18 tools: documentation search, REST calls on a selected site (CallWixSiteAPI), scripted chains of calls (ExecuteWixAPI), account-level actions such as creating or publishing a site, and image upload. The Claude directory listing shows 12 tool names. Needs Node.js 19.9.0 or higher per the setup page | The press release says developers can start coding with it at no cost; the docs state no price |
| @wix/mcp (local server) | On your computer, started with npx | Grok Build can start a local command server. Wix's docs show setup for Claude Code, Codex, Cursor, Claude Desktop and VS Code and do not name Grok. Run npx @wix/cli login once, then the server with --wixCliAuth | The same tools as the hosted server, apart from a few that work only there. With no auth flag it serves documentation and onboarding tools only | No price on the npm page. Version 1.0.100 was published November 13, 2026 |
| Wix Site MCP (per-site endpoint) | Hosted on each Wix site's own domain at /_api/mcp, with no sign-in | A public address, so a custom connector can take it in principle. Wix's help center names ChatGPT, Claude and Cursor IDE. Not tested with Grok | Visitor view only: business details, products and services, bookings, a purchase that finishes on the site and site search. It does not read or change drafts, CMS items or product SEO fields as the site owner | Free, per Wix's help center, and on by default for every site |
| Composio | Hosted | Composio's pages for other clients show a custom MCP server entry, and its framework pages include Grok Build. The Wix toolkit page says Wix requires you to configure your own OAuth credentials. Grok steps were not opened | The Wix toolkit lists 142 tools covering orders, products, contacts, bookings, events and CMS tasks. A text search of that page found no tool that mentions a blog | Free plan: $0, 10,000 tool calls per month. Standard: $18 per seat per month. Extra calls $0.005 each |
| Zapier MCP | Hosted | Zapier's quickstart lists Grok among the clients it works with. Add Zapier as a connector and sign in. Zapier's page for Grok was not opened | Zapier's Wix pages show trigger groups for orders, bookings, events, blog and forms. No Wix action or search was visible in the page text, so which Wix actions Zapier MCP can run is unverified | One MCP tool call uses 2 tasks from your Zapier plan |
| Pipedream | Hosted | Its MCP page gives a static URL for chat clients, https://mcp.pipedream.net/v2, and asks you to connect a Wix account with an API key. Which chat clients the page names did not render, so Grok support is unverified | 6 actions: Add Products To Collection, Create Contact, Create Product, Get Contact, List Site Options and Publish Draft Post. 3 triggers | Free tier is for development only. Startup $99 per month billed annually or $150 monthly |
| Truto | Hosted | Aimed at companies building Wix into their own product. You create an MCP server in Truto's dashboard or API and paste the generated URL into the client. Grok steps were not opened | Its integration page says 210+ MCP-ready tools and lists blog draft tools such as create_a_wix_draft_post. Its FAQ also says Wix tools are built on request | From $999 per connector per year, with a free 30-day sandbox |
4 options that do not fit this job
- Wix connector in Claude. Wix's hosted server added to Claude's own connector directory. It is for Claude users and Wix's blog names no other client.
- Wix app in ChatGPT. Wix's app in ChatGPT, launched March 2, 2026. It lives inside ChatGPT, so Grok cannot use it.
- Wix Plugin and Wix Skills. Instruction bundles plus the Wix MCP for Claude Code, Cursor, Codex, VS Code and Gemini CLI. Grok is not on that list, and the repository marks the project experimental.
- Wix WebMCP and @wix/mcp-remote. WebMCP registers tools on a site's pages for AI agents running in a visitor's browser, so it serves shoppers and not site owners. @wix/mcp-remote is a local proxy whose README calls it a working proof of concept; its last release was June 5, 2025.
Which one to pick
Ryze AI is the best way to connect Grok to Wix for managing blog drafts, Wix Data items and store product SEO from grok.com, Grok Bot or Grok Build, with one caveat: its 3 tools were not tested against a live Wix site for this guide, and publishing a draft live is outside what the tool descriptions document. If you need Wix's documentation search, site creation or scripted API chains, read Wix's own MCP page, which does not name Grok and was not tested with it. Choose Zapier or Composio when your team already runs its Wix automations there, and @wix/mcp when you work from Grok Build on your own machine and want Wix's full tool set.
Sources: The Wix MCP, About the Wix MCP, Wix Site MCP, Wix WebMCP, Wix Plugin, Wix blog on Claude, Wix help on AI platforms, @wix/mcp on npm, Composio Wix toolkit, Zapier Wix MCP, Zapier MCP quickstart, Pipedream Wix MCP and Truto Wix integration, checked November 15, 2026; xAI Grok connectors and Grok Build MCP servers, checked November 14, 2026. Ryze AI side: the Ryze AI Wix guide.
Wix and Grok: dates that matter
| Date | What happened |
|---|---|
| April 16, 2025 | @wix/mcp 1.0.0 was first published on npm. |
| May 7, 2025 | Wix announced the launch of its Model Context Protocol server, naming Claude, Cursor and Windsurf. |
| January 2026 | The Wix connector was added to Anthropic's Claude directory. The listing gives the month and no day. |
| February 2, 2026 | SpaceX announced that it had acquired xAI. xAI's docs now print the name SpaceXSI. |
| March 2, 2026 | Wix launched its app in ChatGPT, built with OpenAI's Apps SDK. |
| May 6, 2026 | Connectors arrived in Grok on the web, iOS and Android. The launch post also brought Bring Your Own MCP, the custom server option. |
| August 11, 2026 | Grok Bot launched as a beta. |
| October 2, 2026 | Grok Bot's Marketplace screen took the name Connect Apps (V0.67.0). |
| October 12, 2026 | The X Subscription began, bundling Grok, Grok Bot, Cursor and X Premium into one plan. |
| November 2, 2026 | Grok Bot 1.0 was announced. Grok Build V1.0.74, out that day, puts an MCP sign-in URL in the /mcps panel when no browser opens. |
| November 13, 2026 | @wix/mcp 1.0.100 was published, the latest version on npm when checked. The Grok Bot page on computer and apps was last changed and describes the Add a custom connector form. |
| November 15, 2026 | The Wix Plugin and @wix/agent-skills stood at version 1.41.5. |
Sources: Wix's MCP server announcement, Claude directory listing, ChatGPT app announcement, @wix/mcp and @wix/agent-skills on npm, checked November 15, 2026; xAI news on SpaceX, Grok connectors, Grok Bot, The X Subscription and Grok Bot 1.0, and the Grok Bot changelog, checked November 14, 2026.
How this guide was tested
No Wix site was connected for this guide, so the record is short. The Ryze AI connector was checked from outside on November 19, 2026. The Wix facts come from pages read on November 15, 2026 and the Grok facts from pages read on November 14, 2026.
| Check | Result |
|---|---|
| Request to https://connector.get-ryze.ai/mcp with no sign-in, November 19, 2026 | HTTP 401 with a WWW-Authenticate header that points to the sign-in details and reports a missing or invalid access token |
| The connector's sign-in details, November 19, 2026 | The authorization server file loaded. It names authorize, token and register endpoints, the authorization code and refresh token grants, PKCE with the plain and S256 methods, and the scopes mcp:read and mcp:write |
| Calls to Wix | None. No Wix test account was connected, so no Wix call was run and no Wix error message was captured |
| The three Wix tool names | Taken from the Ryze AI app source code. They were not seen in a live tool list |
Not run for this guide: any step inside Grok. Nobody added the connector in grok.com, the xAI console, Grok Bot or Grok Build, finished the Ryze AI sign-in from Grok or sent a prompt, so the Grok steps follow xAI's pages as they read on November 14, 2026, and the Grok Bot catalog steps follow the Ryze AI help center. No Wix API key was generated and no Site ID was entered in Ryze AI. Wix's own server, @wix/mcp and the other ways in the comparison were not set up either, and whether grok.com can complete Wix's own sign-in was not checked.
Errors and fixes
No Wix call was run for this guide, so there are no captured error messages. These are the problems that the Ryze AI and Wix documentation describe.
- The Wix tools are missing in Grok
- Connected the site in Ryze AI only after adding the connector? Delete the connector in Grok, create it again and start a fresh chat.
- grok.com will not save the connector
- Grok only takes servers it can reach on the public internet, which the Ryze AI address is, so look for a typo in https://connector.get-ryze.ai/mcp. Team plans need an admin to add it in console.x.ai before anyone else can.
- Ryze AI refuses the Wix connection
- The site needs the Wix Blog app, and without it the connection is refused. Check that you pasted the Site ID, the part of the dashboard URL after /dashboard/, and not the Account ID.
- A link to connect Wix is refused
- A connection link is refused while a Wix connection already exists in the workspace. Disconnect the existing one with the trash icon under View on the Wix card first.
- Wix returns a 403 on a call
- Per Wix's docs this means a missing permission on the key, a missing site header, a key not allowed on that site or a key from an account that does not own the site. Check the permissions and site access on the key.
- Grok cannot read store products or Wix Data
- Without the Data and Stores permissions on the API key, the agent cannot edit store products or collections. Make a key with those permissions, or tick All permissions, and connect again.
- The key was lost
- Wix shows the token once and it cannot be recovered. Generate a new key, enter it in Ryze AI and delete the old one.
- Blog body looks wrong after a write
- Blog bodies written through the tools use Wix rich content (Ricos), not HTML or markdown. Ask Grok to describe the body it will send before it writes.
- Grok edits the wrong site
- One workspace holds one Wix connection, tied to one Site ID. Check which site's Site ID is on the card in Ryze AI.
- Grok Bot shows Ryze AI as Disabled by team admin
- Grok Bot applies the team's Cursor connector policy, and that policy blocks the app. Ask your Cursor team admin to turn it on.
- The same tools appear twice in Grok Bot
- Two copies are installed, the built-in Ryze AI app and an earlier hand-added server. Uninstall the hand-added one.
- The tools say a subscription is required
- Without an active Ryze AI plan or free trial the Wix tools stay locked. Begin the trial, then ask Grok again.
- Grok Build cannot open the sign-in page
- From V1.0.74 the /mcps panel prints the sign-in URL. Press c to copy it and paste it into a browser.
Terms on this page
- Custom connector
- Grok's name for an MCP server you add yourself by URL, outside its built-in list and its catalog.
- MCP
- The Model Context Protocol, an open standard that lets AI apps call tools on outside systems. grok.com, Grok Bot and Grok Build all accept MCP servers.
- Wix API key
- A long-lived key made in Wix Account Settings by an account owner or co-owner. Its permissions decide what it can do, its site access decides which sites it reaches, and it stays valid until rotated or deleted.
- Site ID
- The ID of one Wix site, sent with each site-level call. It is the part of the site dashboard URL after /dashboard/, and it differs from the Account ID.
- Ricos
- Wix's standardized format for rich content. A draft post takes its body as a Ricos document in the richContent field.
- Draft post
- A blog article that is not yet published. Wix's Blog APIs create, update and delete drafts separately from published posts.
- Wix Data collection
- A schema of fields for the items a site stores in its database. An item is one entry in a collection.
Sources: Wix's authentication methods, Blog introduction and Ricos documents, checked November 15, 2026; xAI's Grok connectors and the Grok Bot changelog, checked November 14, 2026.
Frequently asked questions
How do I connect Grok to Wix?
First connect the site in Ryze AI: create an API key in Wix Account Settings, copy the Site ID from the dashboard URL and enter both on the Wix card. On grok.com/connectors pick New Connector, then Custom, and enter https://connector.get-ryze.ai/mcp. Finish by signing in to Ryze AI, choosing the workspace and pressing Allow connection.
Is there a Wix MCP server for Grok?
Yes, several. The Ryze AI connector at https://connector.get-ryze.ai/mcp has 3 Wix tools and goes into Grok as a custom connector. Wix runs its own server at https://mcp.wix.com/mcp, and its pages name Claude, Cursor, GitHub Copilot, Windsurf and Claude Code but not Grok. It was not tested with Grok.
What is the Wix MCP server URL?
For the Ryze AI connector the address is https://connector.get-ryze.ai/mcp, the same for every account. Wix's own remote server is https://mcp.wix.com/mcp. Every Wix site also has a per-site endpoint at its own domain followed by /_api/mcp, which acts as an anonymous visitor.
Does Wix have an official MCP server?
Yes. Wix announced its Model Context Protocol server on May 7, 2025. It is hosted at https://mcp.wix.com/mcp and signs the agent in through your Wix account by default. Wix's setup pages list Claude, Cursor, GitHub Copilot, Windsurf and Claude Code, and none of them names Grok.
Can Grok publish blog posts to Wix?
Grok can create and update blog draft posts through the wix__write tool, within the permissions on your key. The tool descriptions document drafts, so this guide does not claim Grok publishes a post live. Ryze AI also publishes Content Plan articles to the Wix Blog as a separate feature on SEO Starter.
Can Grok edit Wix store product SEO?
Yes, when the key has the Stores permission. The write tool can update store product SEO data and slugs, and the read tool can read store products. Without that permission the agent cannot edit store products. The tools that change a site were not run for this page.
Do I need a Wix API key?
Yes. Ryze AI connects to Wix with an API key and the Site ID, and there is no OAuth install on the Wix side. Only an account owner or co-owner can create a key, and the site needs the Wix Blog app.
Which permissions does the Wix key need?
The Ryze AI help center suggests All permissions. The documented minimum to connect and publish is Blog, Media, Members and Site read. Add Data to read or edit Wix Data collections and Stores to read or edit store products. Wix advises adding only the permissions you need.
Which Grok plan do I need?
xAI says connectors, custom MCP connectors included, are available to all Grok users, and that on Grok Business and Enterprise an admin must add the connector in the console first. Grok Bot is included in Premium, Super and Ultra on The X Subscription, and Plus does not include it.
Is the Site ID the same as the Account ID?
No. The Site ID is the part of the site dashboard URL after /dashboard/. The Account ID does not work for Ryze AI.
Can I connect more than one Wix site?
Not in one workspace. Ryze AI keeps one Wix connection per workspace. To switch sites, open View on the Wix card, disconnect with the trash icon and connect again with the other site's key and Site ID.
How much does it cost to connect Grok to Wix?
Adding the connector costs nothing, but the Wix tools need an active Ryze AI plan or free trial. SEO Starter is $129 per month with a 3-day free trial, Agency is $279 per month, and annual billing takes 30% off the first year.
How do I disconnect Wix from Grok?
Delete the connector at grok.com/connectors, press Remove on the app in Grok Bot, or run grok mcp remove ryze in Grok Build. To end Ryze AI's access too, disconnect the site on its Wix card and rotate or delete the API key in Wix, which needs a 6-digit email code.
Why do the Wix tools not show up in Grok?
If you connected the site in Ryze AI after adding the connector, delete the connector in Grok, add it again and start a fresh chat so the tool list refreshes.