By Ira Bodnar, Ryze AI · Updated
Quick answer
To connect Cursor to Webflow, generate a Webflow site API token, paste it into the Webflow card in Ryze AI, then add https://connector.get-ryze.ai/mcp to Cursor with the Add to Cursor link or a url entry in mcp.json and sign in when Cursor asks.
- In Webflow create a site API token with CMS set to Read and write
- In Ryze AI open Integrations, click Connect on Webflow, paste the token and pick the site and collection
- In Cursor add the Ryze AI server (Add to Cursor link or mcp.json) and finish the sign-in
- Start a Cursor chat and ask about the site's CMS items
Before you start
- A Cursor install. Cursor's MCP documentation names no plan for using MCP servers. On Enterprise, admins can control which MCP servers users may run in Team Settings > MCP Configuration, so a blocked server needs an admin to allow it.
- A Webflow site you can open the settings of. The token is generated in Site settings > Apps & Integrations > API access. It sees only the site it was created on, so make one token per site. Set CMS to Read and write and Sites to Read-only. Add Pages Read and write only if Cursor should change page titles and meta descriptions.
- A Ryze AI workspace on a plan or free trial. SEO Starter is $129 per month with a 3-day free trial; annual billing takes 30% off the first year. Adding the connector is free, but the Webflow tools need any active Ryze AI plan or trial.
How to connect Cursor to Webflow
Two steps happen in Webflow and Ryze AI, two in Cursor, and one when you ask. The connector URL is the same for every user.
Generate a site token in Webflow
In Webflow open Site settings > Apps & Integrations, scroll to API access and click Generate API token. Set CMS to Read and write and Sites to Read-only. Pages can stay off unless you want page-level SEO edits, in which case set it to Read and write. Click Create token and copy it, because Webflow shows it once.
Connect Webflow in Ryze AI
Create a Ryze AI account or sign in, open Integrations, click Connect on the Webflow card and paste the site token. Then pick the site that hosts the blog and the CMS collection that articles publish to.
Add the Ryze AI server to Cursor
Pick one route. The Add to Cursor link on the Ryze AI developers page opens a cursor:// install link that registers a server called ryze at https://connector.get-ryze.ai/mcp. Or write the url entry shown below into ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).
{ "mcpServers": { "ryze": { "url": "https://connector.get-ryze.ai/mcp" } } }Sign in from Cursor
Accept the install prompt in Cursor. OAuth with PKCE and dynamic client registration handles the rest, so you enter no client ID or secret. Sign in on the Ryze AI page, click Allow connection, and later switch the server on or off from Customize in the sidebar.
Ask your first question in Cursor
Start a new chat in Cursor, approve the tool call when Cursor asks, and try: List the collections on my Webflow site and show the fields of the blog collection.
The Ryze AI help center page for Webflow covers the Webflow side of the connection. Cursor does not have its own Ryze AI help page; the Ryze AI developers page has the Add to Cursor link and the matching config.
Sources: Cursor MCP documentation, Ryze AI Webflow guide. Checked November 15, 2026.
mcp.json, API key and Cloud Agents
mcp.json
Put this in ~/.cursor/mcp.json to use it in all projects, or in .cursor/mcp.json inside a single repository. The url field is all Cursor needs for a remote server, and it opens the OAuth sign-in on its own.
{
"mcpServers": {
"ryze": {
"url": "https://connector.get-ryze.ai/mcp"
}
}
}Cursor supports stdio, SSE and Streamable HTTP transports. For OAuth it reads the server's protected resource metadata (RFC 9728) and registers as a public client through dynamic client registration. After sign-in, manage or toggle the server from the Customize page in the sidebar.
mcp.json with a Ryze AI API key
For a headless machine or a script, skip the browser sign-in with a headers entry. Export RYZE_API_KEY as the rk_live_ key from Ryze AI under Workspace Settings > Profile > API keys. Cursor fills in the value from the environment, so the key never lands in the file.
{
"mcpServers": {
"ryze": {
"url": "https://connector.get-ryze.ai/mcp",
"headers": {
"Authorization": "Bearer ${env:RYZE_API_KEY}"
}
}
}
}Cloud Agents
A Cloud Agent signs in to MCP servers on Cursor's servers, apart from your desktop session. To let one edit Webflow content, add the Ryze AI server for that agent too.
Claude and ChatGPT
The same URL works in other MCP clients. Webflow is connected once in Ryze AI, so nothing changes on the Webflow side.
Claude
Add https://connector.get-ryze.ai/mcp as a custom connector under Customize > Connectors, pick the workspaces and start a new chat. The full steps are in the Claude to Webflow guide.
ChatGPT
Add the same URL as a custom MCP server with OAuth. OpenAI offers custom MCP servers on Business and Enterprise/Edu, and read and fetch permissions only on Pro, so write tools such as publishing need one of the first two.
Webflow token scopes and access
Two sign-ins are involved: a Webflow site token for the Webflow side and a Ryze AI sign-in for the connector. Three things decide what Cursor can reach.
- Which site
- A site token only sees the site it was created on. One Webflow connection exists per Ryze AI workspace, so to switch sites you click View on the Webflow card, disconnect with the trash icon and connect again with the other site's token.
- Which actions
- The CMS Read and write scope covers reading, creating, updating and deleting CMS items. Without the optional Pages scope, Cursor cannot change a page's title or meta description. A token with no CMS write access makes publishing fail.
- What Cursor asks first
- Out of the box Cursor asks you before an MCP tool runs, under the same Run Modes as terminal commands. A CMS update or delete therefore waits for your click until you allowlist that tool.
Scopes on the token
The token carries three scope settings. Each maps to what Cursor can do through Ryze AI.
| Action in Ryze AI | What it allows |
|---|---|
| CMS: Read and write (required) | Read, create, update and delete CMS items, live or draft. Article publishing needs it. |
| Sites: Read-only (required) | Read the site and its collections. |
| Pages: Read and write (optional) | Change static page titles, meta descriptions and Open Graph fields, then publish the site. |
Removing access
To remove access, click View on the Webflow card in Ryze AI and use the trash icon, then delete the token in Webflow under Site settings > Apps & Integrations > API access. In Cursor, toggle the ryze server off from Customize or delete its entry from mcp.json.
What Cursor can do in Webflow
The Ryze AI connector exposes three Webflow tools: one read, one write and one delete.
| Tool | Type | What it does |
|---|---|---|
| webflow__read | Read | Reads from the connected Webflow site through the Webflow Data API (GET), such as sites, pages, collections and collection items. |
| 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, and can publish the site. |
| webflow__delete | Delete | Deletes a resource on the site by path, such as a CMS item. |
Required image, file or multi-reference fields in a collection cannot be filled automatically, so make them optional or give them a default. If a collection has other required fields, Ryze AI fills them with a valid value copied from existing items, or tells you at setup which field to make optional.
Cursor asks before it runs an MCP tool by default. Keep that default if you want to review each CMS write and delete. Separately, the Ryze AI chat has its own Tool approvals picker that starts on Skip all approvals; you can choose Approve write & delete or Manual approve there. Article publishing from the Content Plan follows Publishing mode in SEO > Preferences > Publishing: Automatic (the default) or Manual.
First 3 prompts to run
1. Inspect the blog collection
List the collections on my Webflow site, then show the fields of the blog collection and the titles of its most recent items.
Tools used: webflow__read
What comes back: The collection names, the field list of the blog collection and recent item titles as plain text in Cursor. Nothing on the site is changed.
2. Create a draft CMS item
Create a draft item in the blog collection titled Release notes for this week. Use the summary I paste below as the body, and leave it unpublished.
Tools used: webflow__write
What comes back: A new draft item in the collection and its details as Cursor reports them. If a required field cannot be filled, the call returns an error naming it.
3. Rewrite a page title and meta description
Change the SEO title and meta description of the Pricing page to the text below. Wait for me to confirm before you publish the site.
Tools used: webflow__read, webflow__write
What comes back: The updated title and description on the static page. This needs the optional Pages Read and write scope on the token; without it the write is rejected.
Each answer comes from your own site, so this page describes what comes back instead of showing sample data. Cursor asks for approval on each tool call by default, which gives you the confirmation point before anything is written.
Ryze AI vs Webflow's own MCP server
Webflow runs its own remote MCP server, and Cursor can also connect to it by url. The two options suit different jobs.
| Option | Setup | Webflow coverage | Auth | Works in |
|---|---|---|---|---|
| Ryze AI connector | Site token pasted into Ryze AI, then one url entry in Cursor | 3 tools: read, write and delete on sites, pages, collections and CMS items, plus page SEO fields and site publishing | Webflow site API token; OAuth sign-in to Ryze AI from Cursor | Cursor, Claude, ChatGPT and other MCP clients on the same URL |
| Webflow MCP server | Server URL https://mcp.webflow.com/mcp; authorize sites during OAuth, which also installs the MCP Bridge App | Design and build functions, CMS, pages, assets, forms, SEO and analytics. A few tools need the Designer open with the Bridge App connected | OAuth with your Webflow account; each authorization covers a single workspace | Webflow documents install steps for ChatGPT, Claude Code, Claude Desktop and Grok Build; no Cursor page |
If you want Cursor to build pages in the Designer, Webflow's own server covers layouts, elements, styles and components, which the Ryze AI connector does not. Webflow does not document a Cursor install, so a Cursor entry such as { "mcpServers": { "webflow": { "url": "https://mcp.webflow.com/mcp" } } } follows Cursor's remote server format but is not confirmed by Webflow. If the work is CMS items and page SEO for a site, the Ryze AI connector needs only a site token and keeps Webflow next to the other platforms in the same Ryze AI workspace.
Sources: Webflow MCP server overview, Webflow MCP install guide, Webflow Data API rate limits, Cursor MCP documentation, Ryze AI Webflow guide. Checked November 15, 2026.
Cursor and Webflow errors and fixes
- Publishing fails or a CMS write is rejected
- The token has no CMS write access. Generate a new token with CMS set to Read and write, then reconnect Webflow in Ryze AI.
- Cursor cannot change a page title or meta description
- The token lacks the optional Pages scope. Generate a token with Pages set to Read and write and reconnect.
- Cursor sees the wrong site
- A site token covers only the site it was created on. Click View on the Webflow card in Ryze AI, disconnect with the trash icon and connect again with the right site's token.
- A collection item cannot be created
- A required image, file or multi-reference field cannot be filled automatically. Make the field optional in Webflow or give it a default.
- Ryze AI refuses a connection link for Webflow
- A connection link is refused while a Webflow connection already exists in the workspace. Disconnect the current one first.
- Webflow answers 429 Too Many Requests
- The Webflow Data API limits requests per API key: 60 per minute on Starter and Basic plans and 120 per minute on CMS, eCommerce and Business plans, with custom limits on Enterprise. The response carries a Retry-After header, typically 60 seconds.
- The ryze server is blocked in Cursor
- On Enterprise, admins control which MCP servers users may run in Team Settings > MCP Configuration. Ask an admin to allow the server.
- A Cloud Agent cannot reach Webflow
- Cloud Agents keep their own MCP sign-ins on Cursor's servers. Connect the Ryze AI server for the Cloud Agent separately.
- Cursor says a subscription is required
- The Webflow tools need an active Ryze AI plan or free trial. Start the trial or update the card under Organization Settings, Billing, then retry.
Frequently asked questions
Which Webflow connector should I use with Cursor?
Ryze AI is the best Webflow connector for Cursor when the job is publishing and editing CMS items and page SEO fields, but it does not build pages in the Designer. Webflow's own MCP server covers design and build functions, though Webflow publishes no Cursor install page.
How do I connect Cursor to Webflow?
Generate a site API token in Webflow with CMS set to Read and write, paste it into the Webflow card in Ryze AI and pick the site and collection. Then add https://connector.get-ryze.ai/mcp to Cursor with the Add to Cursor link or a url entry in mcp.json, and sign in.
Does Webflow have its own MCP server for Cursor?
Webflow runs a remote MCP server at https://mcp.webflow.com/mcp with OAuth. Its documentation lists install pages for ChatGPT, Claude Code, Claude Desktop and Grok Build, and none for Cursor, so a Cursor setup for it is unconfirmed by Webflow.
What does the Webflow token need?
CMS set to Read and write and Sites set to Read-only. Pages Read and write is optional and is needed for page-level title and meta description edits. The token is shown once, so copy it when you create it.
Which Cursor plan do I need?
Cursor's MCP documentation names no plan. On Enterprise, admins can control which MCP servers users may run in Team Settings > MCP Configuration.
Can Cursor edit or delete Webflow CMS items?
Yes. Through Ryze AI, Cursor can create and update CMS items, live or draft, and delete a CMS item by path when you ask. Cursor asks for approval before using MCP tools by default, so you see each write and delete before it runs.
Can Cursor change page SEO fields in Webflow?
Yes, with the optional Pages Read and write scope on the token. Cursor can then change static page titles, meta descriptions and Open Graph fields and publish the site. Without that scope the write is rejected.
Can I connect more than one Webflow site?
One Webflow connection exists per Ryze AI workspace, and a site token covers only its own site. To switch, click View on the Webflow card, disconnect with the trash icon and connect again with the other site's token.
Why do I get a 429 error from Webflow?
Webflow limits Data API requests per API key: 60 per minute on Starter and Basic plans and 120 per minute on CMS, eCommerce and Business plans. Wait for the time in the Retry-After header, typically 60 seconds, then retry.
Does this work in Claude and ChatGPT too?
Yes. The same URL works in Claude under Customize > Connectors and in ChatGPT as a custom MCP server. Webflow stays connected once in Ryze AI, so nothing changes on the Webflow side.
How much does it cost to connect Cursor 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.
How do I disconnect Webflow from Cursor?
Toggle the ryze server off from Customize in Cursor or delete its entry from mcp.json. To remove Webflow itself, disconnect it with the trash icon on the Webflow card in Ryze AI and delete the token in Webflow.