By Ira Bodnar, Ryze AI · Updated · Connector tested November 15, 2026
Quick answer
The main way to connect Grok to Webflow is the Ryze AI connector. A site administrator generates a site API token in Webflow and pastes it into the Webflow card in Ryze AI; you 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 Webflow tools for that site.
- Webflow: generate a site API token with CMS on Read and write and Sites on Read-only
- Ryze AI: Integrations, Connect on the Webflow card, paste the token, pick the site and collection
- grok.com/connectors: New Connector, Custom, paste the connector address
- Ryze AI page: sign in, pick the workspace, press Allow connection, then open a Grok chat
Grok to Webflow 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, xAI says to finish any required authentication. You sign in on the Ryze AI page and press Allow connection. No Webflow key goes into Grok |
| Webflow tools in Grok | 3: webflow__read, webflow__write and webflow__delete |
| Can Grok change the site | Yes: CMS items, live or draft, and with the optional Pages scope the SEO and Open Graph fields of static pages. 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 |
| Webflow sites per workspace | One. A site token sees only its own site, and a Ryze AI workspace holds one Webflow connection |
| 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. Grok Bot comes with Premium, Super and Ultra on The X Subscription, and Plus leaves it out |
| Ryze AI price | Free to add. The Webflow tools run on an active plan or trial, and SEO Starter is $129 per month with a 3-day free trial |
| Webflow's own option for Grok | Webflow's hosted MCP server at https://mcp.webflow.com/mcp, with OAuth. Webflow's install pages name Grok Build, in a form that describes Cursor, and do not name grok.com. It was not tested with Grok |
| Last checked | Webflow's developer pages on November 15, 2026 and xAI's pages on November 14, 2026. No Webflow call and no step inside Grok was run |
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 must add the connector in console.x.ai before members can use it. Grok Bot is a separate app that signs in with a Cursor account; Premium, Super and Ultra on The X Subscription include it, and Plus does not.
- Administrator rights on the Webflow site. Webflow lets only site administrators create a site token, and a token works on the one site it was made for. Tokens are made in Site settings, Apps & Integrations, under API access.
- An active Ryze AI plan or trial. Adding the connector is free, yet the 3 Webflow 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 into a Webflow CMS collection. Paying yearly takes 30% off the first year.
How to connect Grok to Webflow on grok.com
Steps 1 and 2 take place in Webflow and Ryze AI, steps 3 to 5 in Grok. Every account pastes the same address.
Generate a site token in Webflow
Open the site in Webflow, go to Site settings, then Apps & Integrations, and scroll to API access. Click Generate API token and name it. Set CMS to Read and write and Sites to Read-only. Add Pages on Read and write only if Grok should read or rewrite page titles and meta descriptions. Webflow's own button reads Generate token. Copy the value at once, because it is shown a single time.
Connect Webflow in Ryze AI
Sign in to Ryze AI, open Integrations and press Connect on the Webflow card. Paste the token, then choose the site that hosts your blog and the CMS collection that articles publish to.
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 that its systems can reach over the public internet, and this address qualifies.
Sign in to Ryze AI and allow the workspace
Grok asks you to complete authentication. On the Ryze AI page, sign in, choose the workspace that holds the Webflow connection and press Allow connection.
Ask Grok about the site
xAI says Grok discovers the tools of a new connector and makes them available in conversations. Open a chat and try: List the collections on my Webflow site and the 10 newest items in the blog collection.
On authentication, xAI's connectors page says only to complete whatever is required once the URL is entered. Its tunneling page adds that a server needing OAuth or API keys has that flow finished inside Grok. No xAI page names 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 Webflow side is covered in the Ryze AI Webflow guide. If the Webflow tools are missing because the site was connected after the connector was added, 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 Webflow token lives in Ryze AI, so none of them asks for it again.
Grok Business and Enterprise (admin)
Team plans put one step first: an admin registers the connector in xAI's console. Adding and removing connectors needs Team Read-Write permissions.
- Log in at console.x.ai, choose the team and open Grok Business, then Connectors.
- Press + Add Connector, choose Other and paste https://connector.get-ryze.ai/mcp.
- Complete any authentication the console asks for.
- xAI 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 ask your admin how members reach it.
Grok Bot
Grok Bot is its own desktop and phone app and signs in with a Cursor account. The Ryze AI help center lists Ryze AI as a built-in app on the Connect apps screen. xAI's documentation does not name Ryze AI and the screen was not opened for this guide, so these steps come from the Ryze AI help center.
- Open Connect apps in the Grok Bot sidebar. On the phone, tap your avatar at the top left, then Connect apps.
- Type Ryze AI into Search across apps and skills, open the entry with developer Ryze AI and press Add.
- Your browser opens Ryze AI. Sign in, choose workspaces and press Allow connection.
- When the Authorization complete message appears, press Open Grok Bot or Return to Grok Bot.
- Start a new chat and type @ to attach the app to a task.
If the search shows no Ryze AI entry, the desktop app has a manual form at the bottom of Connect apps called Add a custom connector: enter a name, set Type to Remote HTTPS, put the connector address in Server URL and press Add plugin. xAI also says a Bot can add a server by URL when asked. App connections belong to your account, so every Bot you run can use the Webflow site. The Ryze AI help center says an earlier hand-added copy of Ryze AI should be uninstalled to avoid duplicate tools.
Grok Build CLI
Grok Build, xAI's coding agent for the terminal, registers a remote server with one command.
- Run the command below.
- On first use 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 keeps OAuth tokens in ~/.grok/mcp_credentials.json and names tools <server>__<tool>, so the Webflow tools sit under the ryze server name. When no browser opens, /mcps shows the sign-in 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 prints the company name SpaceXSI) has 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 in config.toml under ~/.grok |
| Transports | A public URL. Grok rejects 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 computer 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 | A provider login in a browser tab, to be done in about 10 minutes. Cursor's connector backend holds the tokens | Browser login on first use, tokens kept 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 approve | 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 or Free | 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.
Webflow token and scopes
Grok never sees the Webflow token. Ryze AI stores it, and three facts about that connection decide what Grok can touch.
- Which site
- Webflow makes each site token for one site, and a Ryze AI workspace holds one Webflow connection. To switch sites, click View on the Webflow card, disconnect with the trash icon and connect again with the other site's token. A connection link is refused while a Webflow connection already exists.
- Which scopes
- Webflow pairs its scopes as cms:read and cms:write, sites:read and sites:write, pages:read and pages:write. Ryze AI asks for CMS on Read and write and Sites on Read-only, and treats Pages on Read and write as optional. Publishing fails when the token has no CMS write access.
- Which fields
- When the collection has other required fields, Ryze AI copies a valid value from existing items or names the field to make optional during setup. Required image, file and multi-reference fields cannot be filled for you; make them optional or give them a default.
The access of the Ryze AI connection on the Webflow side is the set of scopes on the site token. Webflow's endpoint reference names the scope each call needs; this table lines those up with the settings Ryze AI asks for. Two rows differ from what the Ryze AI facts alone suggest, and the notes say so.
| Scope | Webflow calls that need it | On the token Ryze AI asks for |
|---|---|---|
| cms:read | List Collections and List Items: collections, their field schema and their items | Yes, through CMS on Read and write |
| cms:write | Create, Update, Delete and Publish Items, plus Create Live Items, Update Live Items and Unpublish Live Items | Yes, through CMS on Read and write |
| sites:read | List Sites | Yes, through Sites on Read-only |
| sites:write | Publish Site. Webflow lists this scope for a whole-site publish; publishing CMS items needs only cms:write | No. Sites stays on Read-only, and a whole-site publish on this token was not tested |
| pages:read | List Pages and Get Page Metadata. Reading pages is therefore not covered by the minimum token | Only with the optional Pages scope |
| pages:write | Update Page Metadata: title, slug, SEO and Open Graph fields | Only with the optional Pages scope |
Left off the token: sites:write, and the scopes for assets, forms, components, ecommerce and comments. Webflow closes custom code endpoints to site tokens altogether, so no token setting adds them. Webflow calls that need any of these are outside the Ryze AI connection.
Sources: Webflow's site tokens, scopes, List Items, Create Items, List Pages, Update Page Metadata, Publish Site, checked November 15, 2026. Ryze AI side: see the Ryze AI Webflow guide linked in the setup section.
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 run grok mcp remove ryze. To end Ryze AI's own access, revoke the token in Webflow under Site settings, Apps & Integrations, API access, and disconnect Webflow on its card in Ryze AI.
What Grok can do in Webflow
Through Ryze AI, Grok gets 3 Webflow tools: one that reads, one that writes and one that deletes. Every call runs against the site whose token is connected in the workspace. Writes and deletes are separate tools, so an approval setting can treat them differently.
| Tool | Type | What it does |
|---|---|---|
| webflow__read | Read | Reads from the connected site through the Webflow Data API (GET): sites, collections and collection items, and static pages when the token has the Pages scope. |
| webflow__write | Write | Creates or updates resources on the site, such as CMS items, live or draft, and static page SEO and Open Graph fields. Ryze AI also lists publishing the site, which Webflow ties to sites:write. |
| webflow__delete | Delete | Deletes a resource on the site by its path, such as a CMS item. |
Whether Grok pauses before a change depends on the product, as the Grok table above shows. xAI describes no approval step on grok.com, so a line such as wait for my yes before writing is an instruction to the model. In Grok Build, allow and deny rules can name the Webflow tools. 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. Scheduled tasks run without an approval step.
Webflow and Grok limits
Webflow sets Data API limits by site plan and counts each API key on its own, so the token you gave Ryze AI has its own budget. Past the limit Webflow answers HTTP 429 with a Retry-After header. A long list of CMS items changed in one request is the likeliest way to reach it, so hand over big batches in smaller groups.
| Limit | Figure | Set by |
|---|---|---|
| Requests per minute | 60 on Starter and Basic, 120 on CMS, eCommerce and Business, custom on Enterprise, per API key | Webflow Data API |
| Over the limit | HTTP 429, error code too_many_requests, Retry-After typically 60 seconds. Responses carry X-RateLimit-Remaining and X-RateLimit-Limit | Webflow Data API |
| Publishing the site | One successful publish per minute | Webflow Data API |
| Items per read | Up to 100 per request, paged with offset. Up to 10 filter terms, 2 text-search terms and 3 sort fields | Webflow Data API |
| Bulk writes | Up to 100 items per create, update, live update or unpublish request; for creates every locale variant counts | Webflow Data API |
| Fields in a collection | Up to 60 | Webflow |
| Site tokens | Up to 5 per site; a token expires after 365 consecutive days without use | Webflow |
| 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: Webflow's rate limits, site tokens, List Items, Create Items, managing collections and items, checked November 15, 2026.
xAI's Grok Bot changelog, Grok Build MCP servers, checked November 14, 2026.
No call to Webflow was run for this guide, so there is no table of tested calls. The test record says what was and was not checked.
First 3 prompts to run
Each prompt says what to ask Grok and what the answer contains. Answers come from your own site, so this page prints no sample output.
1. Map the CMS before changing anything
List the collections on my Webflow site and, for the blog collection, show the fields of an item and which items are still drafts.
Tools used: webflow__read
What comes back: The collections, the field names on blog items and each item's publish status. The site is not changed.
2. Save a draft item
Create a draft item in the blog collection with the title, slug and excerpt I paste below. Leave it unpublished and tell me which fields you filled in.
Tools used: webflow__write
What comes back: A new item saved as a draft and a list of the fields that were filled. A required field that could not be filled is named in the reply.
3. Find static pages with empty SEO fields
Read the static pages of my Webflow site and list those with an empty title or meta description. Propose text, then wait for my yes before you update anything.
Tools used: webflow__read, then webflow__write once you agree
What comes back: The pages with empty fields and your proposed text. Both the read and the edit need the optional Pages scope on the token.
The yes in prompt 3 is an instruction to Grok. On grok.com xAI describes no approval step, so keep that line in every prompt that edits or deletes. These prompts were not run, so none has a result on this page.
10 jobs to hand to Grok
Ten jobs to give Grok, each with the Ryze AI tool behind it. The default connection means the token Ryze AI asks for, CMS on Read and write and Sites on Read-only, with no Pages scope. None of the jobs was run on a Webflow site for this guide.
| Job | What to ask Grok | Tool | On the default connection |
|---|---|---|---|
| CMS map | Which collections does the site have, and which fields does each define? | webflow__read | Works. Reading collections needs cms:read |
| Blog inventory | List the items of the blog collection with name, slug and publish status. | webflow__read | Works. Up to 100 items per request |
| Gap check | Which blog items have an empty summary or no featured image? | webflow__read | Works. The check runs on the returned field data |
| Site details | Show the site's name, custom domains and locales. | webflow__read | Works. Reading sites needs sites:read |
| New draft | Create a draft item from the title, slug and body I give you. | webflow__write | Works. Creating items needs cms:write |
| Item edit | Change the excerpt or body of the item with this slug. | webflow__write | Works |
| Live change | Create or update an item directly on the live site. | webflow__write | Works. Live items also need cms:write |
| Clean-up | Delete the CMS item with this slug. Set approval for this tool where the client offers it. | webflow__delete | Works |
| Page SEO audit | List static pages whose title or meta description is empty. | webflow__read | No. Page reads need the optional Pages scope |
| Page SEO rewrite | Rewrite a static page's title, meta description and Open Graph fields. | webflow__write | No. Needs Pages on Read and write |
7 ways to connect Grok to Webflow
Seven ways to give Grok access to a Webflow site are worth knowing. The Ryze AI connector is this guide's main way: one public address goes into grok.com, Grok Bot and Grok Build, the token is pasted into Ryze AI once and nothing runs on your computer. Webflow's own hosted server is the closest alternative. Webflow's install pages name Grok Build only in a form that describes Cursor, so none of these rows has a Webflow page written for grok.com. Each row reads as the vendor's pages stood on November 15, 2026, and none was set up for this guide. 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, added by an admin first 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 | One site per token: CMS collections and items to read, create (live or draft), update and delete, plus static page SEO and Open Graph fields with the Pages scope | Connector free. SEO Starter $129 per month, 3-day free trial; any active plan or trial unlocks the tools |
| Webflow's own remote MCP server | Hosted by Webflow at https://mcp.webflow.com/mcp | Webflow names no grok.com steps. xAI documents a URL form for any remote server on Grok Build, grok mcp add --transport http webflow https://mcp.webflow.com/mcp, which was not tested. Webflow signs in with OAuth, and only site owners and admins can authorize it. Whether grok.com completes that sign-in is not stated | Designer work (elements, styles, components, variables), CMS collections, fields and items, pages with SEO and schema markup, assets, forms, comments and custom code. Webflow's reference lists 37 tool names. One workspace per authorization | No price stated for the server. Webflow's pricing page lists it on the free Starter plan and on Basic. Analyze, Optimize and AEO tools need paid add-ons |
| Webflow Beta MCP server | Hosted by Webflow at https://mcp.webflow.com/beta/mcp | Manual only, as a server of its own. Webflow's examples cover Claude Code, not Grok | Experimental tools and early-access API features | No price stated |
| webflow-mcp-server (open source package) | On your computer, started with npx | Only Grok Build runs local servers by command on your machine: grok mcp add webflow -- npx -y webflow-mcp-server@latest, with WEBFLOW_TOKEN set. The README shows Cursor and Claude Desktop configs, so this pairing was not tested. Needs Node.js 22.3.0 or higher | Webflow's MCP server code run locally with your token. The README still prints the retired /sse address for remote use | Free, MIT licence. Version 1.0.0 from September 17, 2025 was still the newest on npm on November 15, 2026 |
| Zapier MCP | Hosted by Zapier | Zapier's quickstart lists Grok and Grok Bot among its clients: add Zapier as a connector and sign in. Zapier's page for Grok was not opened | Webflow actions you switch on. The Webflow page shows 8 before Load More, such as Create Item, Update Live Item and Find Item, and prints no total | Open to every Zapier account. One tool call uses 2 tasks; failed calls do not count |
| Composio | Hosted by Composio | The toolkit page names Claude, ChatGPT and Cursor, and the steps read were for ChatGPT and Claude Code. Grok is not named. You first register your own OAuth app with Webflow | 60 Webflow tools on the toolkit page, including bulk creates of up to 100 items, deletes, live items, orders, webhooks and assets | Free plan at $0 with $2 in one-time credits and 10,000 tool calls a month; Standard at $18 per seat per month |
| MCP Router by Kvalifik | A desktop app for macOS and Windows x64 | Its README names Codex, Claude Desktop, Claude Code, Cursor, VS Code and Gemini CLI, not Grok. Not set up for Grok | Webflow projects across several workspaces through one MCP connection, with per-project access. No tool count in the README | Free under a custom source-available licence, not OSI open source. The README says it is not affiliated with Webflow |
Options that do not fit this job
- Webflow's Grok Build plugin. Webflow's install page for Grok Build calls the client formerly Cursor and points at cursor.com/marketplace/webflow: a plugin with 22 skills and the webflow server, installed with /add-plugin webflow or Add to Cursor. Its steps use Cursor's .cursor/mcp.json, so they do not describe xAI's terminal agent.
- Webflow Skills. Workflow files such as bulk-cms-update, site-audit and safe-publish. Webflow names Grok Build as one place to get them, and they run on top of Webflow's MCP server with no connection of their own.
- Webflow app in ChatGPT, Claude's Webflow connector and Webflow in Slack and Postman. Packaged routes into other products. None of them is a Grok route.
- Webflow documentation MCP server and kapilduraphe/webflow-mcp-server. The first serves Webflow's developer docs with no site data. The second has two read-only tools, get_sites and get_site, and no CMS access.
- The old address https://mcp.webflow.com/sse. Webflow replaced it on November 24, 2025 and called it fully deprecated on January 17, 2026.
Which one to pick
Ryze AI is the best way to connect Grok to Webflow for reading, drafting and updating CMS items on one site from grok.com, Grok Bot or Grok Build, with one caveat: a token covers a single site, a workspace holds one Webflow connection and there are no Designer tools. Webflow's own server suits layout, style and component work and reaches several sites of a workspace, but Webflow's pages do not cover grok.com and the pairing was not tested. Zapier and Composio fit teams that already run other apps through them. The local package fits someone who wants the server on their own computer in Grok Build.
Sources: Webflow MCP overview, getting started, how it works, FAQs, Grok Build install page, beta server, Webflow Skills, Webflow pricing, webflow/mcp-server, webflow-mcp-server on npm, Zapier Webflow MCP, Zapier MCP quickstart, Composio Webflow toolkit, Composio pricing, Kvalifik/mcp-router, kapilduraphe/webflow-mcp-server, checked November 15, 2026.
xAI's xAI Grok connectors, Grok Build MCP servers, checked November 14, 2026. Ryze AI side: the Ryze AI help center pages linked above.
Webflow and Grok: dates that matter
| Date | What happened |
|---|---|
| April 8, 2025 | Webflow's changelog introduced its official MCP server. |
| September 4, 2025 | Webflow's MCP server gained Designer API support, with a companion app that installs during authorization. |
| November 24, 2025 | Webflow moved its MCP server from SSE to HTTP: https://mcp.webflow.com/mcp replaced the /sse address. |
| December 9, 2025 | Webflow opened the Beta MCP server at https://mcp.webflow.com/beta/mcp, then for Official Webflow MCP Testing partners only. |
| January 17, 2026 | Webflow's MCP v1.0.1 merged its 46 or more data tools into 19 and declared the /sse address fully deprecated. |
| February 2, 2026 | SpaceX announced that it had acquired xAI. xAI's docs now print the name SpaceXSI. |
| May 6, 2026 | Connectors arrived in Grok on the web, iOS and Android. The launch post also brought the custom MCP server option. |
| August 11, 2026 | Grok Bot launched as a beta. |
| September 21, 2026 | Webflow released MCP v2.1, its newest version with a changelog post: GSAP interactions, Webflow Cloud and Campaigns tools, CMS field groups. |
| October 2, 2026 | Grok Bot's Marketplace screen was renamed Connect Apps (V0.67.0). |
| October 12, 2026 | The X Subscription began, bundling Grok, Grok Bot, Cursor and X Premium. |
| November 2, 2026 | Grok Bot 1.0 was announced. Grok Build V1.0.74 put an MCP sign-in URL in the /mcps panel for when no browser opens. |
| November 13, 2026 | The webflow/mcp-server repository on GitHub received its latest push before this check. xAI's Grok Bot page on computer and apps was last changed and now describes the Add a custom connector form. |
Sources: Webflow's changelog posts of April 8, 2025, September 4, 2025, November 24, 2025, December 9, 2025, January 17, 2026, September 21, 2026, webflow/mcp-server on GitHub, checked November 15, 2026.
xAI news and changelogs: SpaceX, Grok connectors, Grok Bot, The X Subscription, Grok Bot 1.0, Grok Bot changelog, Grok Build changelog, checked November 14, 2026.
How this guide was tested
This record is short, because no call to Webflow was run. The Webflow facts come from developer pages, the GitHub and npm records opened on November 15, 2026, and the Grok facts from xAI's pages opened on November 14, 2026.
| Check | Result |
|---|---|
| Calls to Webflow through the Ryze AI connector | None. No Webflow test site was connected, so nothing on this page comes from a site, and no table of tested calls or exact error messages is shown. |
| The Webflow tool list | Not seen in a live connector. The three tool names come from the Ryze AI app's source code. |
| Webflow's pages | Developer docs on the MCP server, token scopes, rate limits and CMS endpoints, plus the changelog, GitHub and npm records, read on November 15, 2026. |
| xAI's pages | Documentation for connectors, connector management, Grok Bot and Grok Build, plus xAI's news and changelog pages, read on November 14, 2026. |
| Scope conflicts found while checking | The Ryze AI facts say the Webflow tools can read pages and publish the site. Webflow's reference ties page reads to pages:read and a whole-site publish to sites:write, so this guide treats both as untested on the minimum token. |
Nothing was tried inside Grok. No connector went into grok.com, the xAI console, Grok Bot or Grok Build, so the Grok steps rest on xAI's pages and the Grok Bot catalog steps on the Ryze AI help center. No Webflow token was generated, no Webflow call was made, and Webflow's own server and the other ways in the comparison were not set up. Whether grok.com accepts Webflow's own OAuth sign-in is not stated by either company.
Errors and fixes
No error message was captured in a test for this guide, so the list below comes from the Ryze AI facts, Webflow's rate limit page and xAI's pages.
- The Webflow tools are missing in Grok
- Connected Webflow in Ryze AI only after adding the connector? Delete the connector in Grok, add it again and start a fresh chat.
- grok.com will not save the connector
- Grok accepts only 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. On team plans an admin must add it in console.x.ai first.
- Publishing fails
- The token has no CMS write access. Generate a new token with CMS on Read and write and connect Webflow in Ryze AI again.
- Page titles or meta descriptions cannot be read or changed
- The token has no Pages scope. Generate one with Pages on Read and write and reconnect.
- Grok cannot see another Webflow site
- A site token covers only its own site and a workspace keeps one Webflow connection. Disconnect with the trash icon and connect again with a token from the other site.
- A new item is rejected for a missing field
- Required image, file and multi-reference fields cannot be filled automatically. Make them optional or give them a default in the collection settings.
- The Webflow connection link is refused
- Links are refused while the workspace already has a Webflow connection. Disconnect that one first.
- HTTP 429 from Webflow
- The token went over the Data API limit for the site plan. Wait for the Retry-After time, then continue in smaller groups. This is from Webflow's rate limit page and was not seen in a test.
- Grok Bot shows Ryze AI as Disabled by team admin
- Grok Bot applies the team's connector policy, and that policy blocks the app. Ask your 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 Webflow tools stay locked. Start 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.
- Site API token
- A key made in one Webflow site's settings that opens the Data API for that site alone, with the scopes picked at creation. Only site administrators can make one.
- Scope
- A permission on a Webflow token, usually in a read and write pair such as cms:read and cms:write, that decides which data it can reach.
- CMS collection and item
- A collection groups records that share a template, such as blog posts. An item is one record in it.
- Draft and Changes in draft
- An item saved as a draft and never published stays in Draft. A published item with draft edits shows Changes in draft, and the live version stays up until those changes are published.
- Connect apps
- Grok Bot's screen for adding apps and skills. It was called Marketplace until release V0.67.0 of October 2, 2026.
Sources: Webflow's site tokens, scopes, updating items, Webflow pricing, checked November 15, 2026. xAI's Grok connectors page and Grok Bot changelog, checked November 14, 2026.
Frequently asked questions
How do I connect Grok to Webflow?
Generate a site API token in Webflow under Site settings, Apps & Integrations, API access, with CMS on Read and write and Sites on Read-only, and paste it into the Webflow card in Ryze AI. 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 Webflow connector for Grok?
Webflow runs its own hosted MCP server at https://mcp.webflow.com/mcp, and the Ryze AI connector at https://connector.get-ryze.ai/mcp reaches Webflow through a site token. Webflow's install pages name Grok Build in a form that describes Cursor and do not name grok.com, so Webflow's server was not tested with Grok.
What is the Webflow MCP server URL for Grok?
Webflow's own server answers at https://mcp.webflow.com/mcp and its beta at https://mcp.webflow.com/beta/mcp. For the Ryze AI route the address is https://connector.get-ryze.ai/mcp, the same for every account. Grok takes a public URL as a custom connector.
Which Webflow connector should I use with Grok?
For CMS items and page SEO fields on one site, use the Ryze AI connector, since its sign-in runs through Ryze AI and Webflow needs only a token pasted once. For Designer work or several sites in a workspace, Webflow's own server covers more, though its pairing with grok.com is not documented.
What Webflow permissions do I need?
You must be a site administrator, because only administrators can generate a site token. Give the token CMS on Read and write and Sites on Read-only, and add Pages on Read and write only if Grok should read or change page titles and meta descriptions.
Which Grok plan do I need?
xAI says connectors, custom MCP connectors included, are available to all Grok users. 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.
Can Grok publish to Webflow?
Grok can create CMS items as drafts or directly on the live site, and update live items, through the webflow__write tool, within the scopes of the token. Ryze AI also publishes Content Plan articles into a collection as a separate feature on SEO Starter. A whole-site publish is tied to sites:write in Webflow's reference and was not tested.
Can Grok edit or delete Webflow content?
Yes. The write tool creates and updates CMS items and, with the Pages scope, static page SEO and Open Graph fields. The delete tool removes a CMS item. On grok.com xAI describes no approval step, so ask Grok to wait for your yes before each change.
Does Grok need the Webflow Designer open?
No for the Ryze AI connector, which works through Webflow's Data API and has no Designer tools. With Webflow's own server, only snapshots, image uploads and reading or changing the current selection, page, mode, branch, canvas and breakpoints need the Designer open.
Can I connect more than one Webflow site?
Not at the same time in one workspace. A site token covers one site and Ryze AI keeps one Webflow connection per workspace. To switch, click View on the Webflow card, disconnect with the trash icon and connect again with the other site's token.
Does this work in Grok Bot and Grok Build?
Yes, by the same address. Grok Bot: open Connect apps and add Ryze AI, or use the Add a custom connector form with Type Remote HTTPS. Grok Build: run grok mcp add --transport http ryze https://connector.get-ryze.ai/mcp. Neither was run for this guide.
Why do the Webflow tools not show up in Grok?
If you connected Webflow 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.
Why does saving a draft item fail on a required field?
Required image, file and multi-reference fields cannot be filled automatically. Make them optional or give them a default in the Webflow collection settings. Ryze AI fills other required fields with a valid value copied from existing items, or names the field to relax during setup.
How much does it cost to connect Grok to Webflow?
Adding the connector costs nothing, but the Webflow tools need an active Ryze AI plan or free trial. SEO Starter is $129 per month with a 3-day free trial, and annual billing takes 30% off the first year. Webflow's Data API allows 60 requests per minute on Starter and Basic and 120 on CMS, eCommerce and Business.
How do I disconnect Webflow 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, revoke the token in Webflow and disconnect the Webflow card in Ryze AI.