How to connect VS Code to Webflow

Give Ryze AI a Webflow site token once, add one MCP URL to VS Code, then ask GitHub Copilot Chat about your sites, CMS collections and items.

Your MCP URL
https://connector.get-ryze.ai/mcp

Paste it into VS Code under Chat: Open Customizations, MCP Servers, Add Server. See the steps

See pricing

By Ira Bodnar, Ryze AI · Updated · No live Webflow call yet, sources checked November 15, 2026

Quick answer

The main way to connect VS Code to Webflow is the Ryze AI connector. Generate a Webflow site token and connect it once in Ryze AI. Then, with Copilot as the session target, run Chat: Open Customizations, select MCP Servers and add an HTTP server with https://connector.get-ryze.ai/mcp and the server ID ryze. Trust it and finish the Ryze AI sign-in in your browser. Copilot Chat then has 3 Webflow tools, one each to read, write and delete, for sites, collections and CMS items. Page title and meta description edits need the optional Pages scope on the token.

  1. In Webflow open Site settings > Apps & Integrations > API access, generate a token with CMS set to Read and write and Sites set to Read-only
  2. In Ryze AI open Integrations, click Connect on the Webflow card, paste the token and pick the site and CMS collection
  3. In VS Code run Chat: Open Customizations, select MCP Servers and add an HTTP server with the connector URL
  4. Trust the server, sign in to Ryze AI and ask Copilot Chat to list the collections on your site

VS Code to Webflow at a glance

FactDetail
Main way to connectThe Ryze AI connector, saved in VS Code as one HTTP MCP server called ryze
Server addresshttps://connector.get-ryze.ai/mcp, the same for every user
Where it goes in VS CodeChat: Open Customizations > MCP Servers > Add Server (+), or the MCP: Add Server command. A personal entry lands in Copilot Global, ~/.copilot/mcp-config.json
Sign-in from VS CodeOAuth in the browser, run by VS Code. No Webflow token is typed into VS Code
Sign-in to WebflowDone once in Ryze AI with a Webflow site API token, then you choose the site and the CMS collection
Webflow tools3: webflow__read, webflow__write and webflow__delete
Can Copilot change the siteYes. The write tool creates and updates CMS items, live or draft, and the delete tool removes one. A new VS Code session starts on Manual permissions, which show a call that is not auto-approved before it runs
Other data in the same chatThis guide covers the Webflow tools only. Tools for other Ryze AI platforms appear when you connect those platforms in the same workspace
Copilot planGitHub lists MCP in every Copilot plan. Business and Enterprise seats also need the MCP servers in Copilot policy, which ships off
Ryze AI priceSEO Starter is $129 per month with a 3-day free trial. Adding the connector is free
Webflow's own option for VS CodeWebflow runs a remote MCP server at https://mcp.webflow.com/mcp. Its install pages do not name VS Code, and its getting-started page says any agent that supports MCP servers can connect by URL
Last checkedSources read November 14 and 15, 2026. No Webflow call was run for this guide and no step inside VS Code was run

Before you start

  • GitHub Copilot in a current VS Code. GitHub's MCP article asks for Copilot access and VS Code 1.99 or later. The steps below save the server to Copilot Global, which arrived in VS Code 1.140, so update an older install first. An eligible GitHub account with no plan is enrolled in Copilot Free when it signs in to VS Code.
  • The MCP policy, when Copilot comes from an organization. On Copilot Business or Copilot Enterprise through an organization or enterprise, the MCP servers in Copilot policy must be on, and GitHub ships it off. Copilot Free, Pro, Pro+ and Max are outside that policy.
  • A local folder, with Copilot as the session target. Microsoft's walkthrough asks for AI features on, a local folder open and Copilot picked in the Session Target dropdown before a server is added.
  • A Webflow site administrator. Webflow says only site administrators can create a site token. The token covers the one site it was made on, so repeat the steps for each site you want in the chat, keeping in mind that Ryze AI holds one Webflow connection per workspace.
  • A blog collection Ryze AI can fill. Required image, file or multi-reference fields cannot be filled automatically. Make them optional or give them a default, or Ryze AI will tell you at setup which field to change.
  • A Ryze AI workspace on a plan or free trial. SEO Starter is $129 per month with a 3-day free trial and publishes Content Plan articles into a Webflow CMS collection. Adding the connector is free, but the Webflow tools need any active Ryze AI plan or trial.

How to connect VS Code to Webflow with the Customizations editor

The first two steps happen in Webflow and Ryze AI, the other four in VS Code. The connector URL is the same for every user.

  1. Generate the Webflow site token

    In Webflow open Site settings > Apps & Integrations, scroll to API access and click Generate API token. Name it, set CMS to Read and write and Sites to Read-only, and set Pages to Read and write only if you want page title and meta description edits. Webflow's own button reads Generate token. Copy the token, because Webflow shows it once.

  2. Connect the site in Ryze AI

    Create a Ryze AI account or sign in, open Integrations and click Connect on the Webflow card. Paste the token, then pick the site that hosts the blog and the CMS collection that articles publish to.

  3. Open the MCP Servers list in VS Code

    Open a local project folder and pick Copilot in the Session Target dropdown, because the editor lists the servers of the selected harness. Run Chat: Open Customizations from the Command Palette, select MCP Servers and choose Add Server (+) in the User group.

  4. Add the HTTP server

    Choose HTTP (HTTP or Server-Sent Events) and enter https://connector.get-ryze.ai/mcp. Type ryze as the server ID. For a personal setup select Global, then Copilot Global. There is no client ID or secret to enter.

  5. Trust the server and sign in

    Read the trust prompt before you accept it, then finish the Ryze AI sign-in in the browser. If no sign-in page opens, use the ellipsis (...) beside ryze in MCP Servers and choose Authenticate. On the Ryze AI page pick the workspace that holds your Webflow connection and click Allow connection.

  6. Ask your first question in Copilot Chat

    Open Copilot Chat and ask: List the CMS collections on my Webflow site and the fields in each one. Expand the tool call in the conversation to confirm the ryze server answered. Microsoft's docs point out that a reply with no tool call proves nothing about the connection.

To switch the Webflow site later, click View on the Webflow card in Ryze AI, disconnect it with the trash icon and connect again with the other site's token. Ryze AI also refuses a Webflow connection link while a Webflow connection already exists in the workspace.

The Ryze AI help center page for Webflow covers the Webflow side of the connection, and the VS Code MCP servers documentation covers the editor side.

Sources: VS Code MCP servers, GitHub: extend Copilot Chat with MCP, GitHub Copilot plans, Webflow site tokens, Ryze AI help center page for Webflow. Checked November 14 and 15, 2026.

Command Palette and config files

The Customizations editor, the guided command and the config files all end in the same server entry. Pick by how you manage VS Code. Webflow needs nothing different for any of them, because the site token was given to Ryze AI before VS Code was involved.

Guided flow

Run MCP: Add Server from the Command Palette and answer the prompts with the same URL and the server ID ryze. It skips the Customizations editor.

Portable config file

To write the entry by hand, use the portable format that the Copilot harness reads. It lives in ~/.copilot/mcp-config.json for you alone ($COPILOT_HOME/mcp-config.json when that variable is set) or in .mcp.json at the workspace root. Both start with mcpServers. Every portable HTTP example in Microsoft's reference carries a tools field, so this one does too:

{ "mcpServers": { "ryze": { "type": "http", "url": "https://connector.get-ryze.ai/mcp", "tools": ["*"] } } }

Older VS Code format

The earlier format uses the key servers in .vscode/mcp.json or the profile mcp.json. It belongs to the Local harness, which VS Code 1.146 deprecated on November 11, 2026, with removal announced for February 2027. Copilot harness sessions do not read these files directly. Older tutorials still show this shape, and some vendors' one-line install commands still write it:

{ "servers": { "ryze": { "type": "http", "url": "https://connector.get-ryze.ai/mcp" } } }

In the portable entry, ["*"] makes every tool of the server available and leaves approvals in place. Portable files do not support VS Code input variables, envFile or SecretStorage. A workspace .mcp.json is meant to be committed for a team, and with this connector it holds only the address. The Webflow site token stays in Ryze AI and never lands in a file you commit.

Limits of VS Code to know

  • The type field sets the transport: http for Streamable HTTP, stdio for a local command and sse for older endpoints that Microsoft labels legacy. The ryze entry uses http.
  • Trusting a server lets it start, signing in gives it access, and approving covers single tool calls. VS Code treats these as three steps.
  • Copilot Global does not sync to your other machines, and a remote host or Dev Container does not read the local file. Add the server on the machine where the session runs.
  • Settings Sync carries the profile mcp.json only, so it leaves both the Copilot user file and .mcp.json files behind.
  • Microsoft's MCP developer guide says VS Code signs in to providers other than GitHub and Microsoft Entra through Dynamic Client Registration or a pre-registered OAuth client. Ryze AI was not tried inside VS Code for this guide. If the sign-in does not start, email Ryze AI support with the link at the end of the page.

VS Code, Copilot and MCP in one table

TopicWhat Microsoft and GitHub document
Screen for adding a serverChat: Open Customizations opens the Agent Customizations editor. Its MCP Servers page has Add Server (+). The Chat title bar and the Agents window sidebar open the same editor
Files the Copilot harness reads~/.copilot/mcp-config.json (Copilot Global) for one person and .mcp.json at the workspace root for a shared setup, each with a top-level mcpServers object
Legacy files.vscode/mcp.json and the profile mcp.json, with a servers object, kept for the deprecated Local harness
Transportsstdio starts a command, http speaks Streamable HTTP, and sse reaches older endpoints that lack Streamable HTTP
Sign-inWhen a server asks for OAuth, the Copilot runtime hands the sign-in to VS Code, which stores the credentials. Redirects go to http://127.0.0.1:33418 or https://vscode.dev/redirect. The portable format has a flat oauthClientId field for a pre-registered client
Keys and headersHTTP entries accept a headers object whose values can read environment variables as ${NAME}. The portable files ignore input prompts, envFile and SecretStorage, so VS Code never asks you for a key there
Tool approvalNew sessions start on Manual permissions and show the tool name and its inputs for any call that is not auto-approved. The chat input dropdown also offers Assisted permissions, where an LLM judges each call, and Allow all. Autopilot approves every tool
PlanGitHub includes MCP on Copilot Free, Student, Pro, Pro+, Max, Business and Enterprise. Business and Enterprise seats also need the MCP servers in Copilot policy, off by default
Admin controlsallowedMcpServers and deniedMcpServers in enterprise-managed settings match a server by URL, command or name, and a local file cannot lift a block. chat.mcp.access set to none turns MCP off
Managing a serverEach entry in MCP Servers has a toggle and an ellipsis menu with Start, Stop, Enable or Disable, Uninstall and Show Output, plus Authenticate when a sign-in is pending. MCP: List Servers offers the same actions
Tool cap128 enabled tools per chat request. Past that, VS Code answers Cannot have more than 128 tools per request.

Sources: VS Code MCP servers, VS Code MCP configuration reference, VS Code: manage MCP servers, VS Code MCP developer guide, VS Code tool approvals, VS Code agent harnesses, VS Code enterprise AI settings, GitHub: extend Copilot Chat with MCP, GitHub Copilot plans. Checked November 14 and 15, 2026.

Other editors and assistants

The same URL works in other MCP clients. The site is connected once in Ryze AI, so nothing changes on the Webflow side.

Cursor

Cursor keeps its servers in its own mcp.json, with mcpServers and a url field. The same Ryze AI connection serves it. How to connect Cursor to Webflow.

Claude and Claude Code

Claude takes the same URL under Customize, Connectors, and Claude Code takes it from the command line. How to connect Claude Code to Webflow.

ChatGPT and Codex

ChatGPT takes the same URL as a custom MCP app, and its plan rules differ from Copilot's. Codex adds it as an MCP server of its own. How to connect ChatGPT to Webflow.

Webflow token, scopes and rules

The Webflow connection is a site token, so the access question is about what that token was allowed to do when you made it. Two sign-ins are involved: the token, handed to Ryze AI once, and the Ryze AI sign-in that VS Code starts. Four things decide what Copilot Chat can reach.

Which site
The one site the token was created on. Webflow site tokens are made per site, and Ryze AI keeps one Webflow connection per workspace.
Which scopes
The ones ticked when the token was generated. Ryze AI asks for CMS Read and write and Sites Read-only, with Pages Read and write as an option. Webflow names them cms:read, cms:write, sites:read, sites:write, pages:read and pages:write.
Which collection
The CMS collection you chose during setup is where Content Plan articles publish. The tools themselves can list and edit other collections on the same site, because the CMS scope covers the CMS.
What VS Code asks
A server saved in Copilot Global can ask for your trust before it starts, and again after its entry changes. Manual permissions then show each Webflow call that is not auto-approved, with its tool name and inputs.

Scopes behind each action

The table maps what you ask Copilot Chat to do to the Webflow scope that the endpoint names in Webflow's reference. The last column says whether the default token, CMS Read and write plus Sites Read-only, covers it.

Action in Ryze AIWebflow scopeOn the default token
List collections and read their itemscms:readYes
Read the site's detailssites:readYes
Create or update CMS items, as draft or livecms:writeYes
Delete CMS itemscms:writeYes
Publish CMS itemscms:writeYes. Not tested
List static pages and read their metadatapages:readNo. Needs the optional Pages scope
Change a page's title, meta description or Open Graph fieldspages:writeNo. Needs the optional Pages Read and write scope
Publish the whole sitesites:write on Webflow's Publish Site endpointNot promised. The default token has Sites Read-only. Not tested

What the token can and cannot reach, in Webflow's words

Webflow documents site tokens, scopes and their limits on separate pages. The table sets out the parts that decide what Ryze AI can do with the token.

ItemWhat Webflow saysWhat it means for the Ryze AI tools
Site API tokenGives an integration access to the Data API for one site, with the scopes picked at creation. Only site administrators can create oneThe credential Ryze AI stores for Webflow. It sees only the site it was created on
Expiry and countA site token expires after 365 consecutive days of inactivity, and a site can have up to 5 tokensAn unused connection can stop working, so generate a new token and reconnect
cms:read and cms:writeList Collections and List Items name cms:read. Create, update, delete and publish items name cms:writeCover reading, creating, updating, deleting and publishing CMS items
sites:read and sites:writeList Sites names sites:read. Publish Site names sites:writeThe default token has Sites Read-only, so a full site publish is not covered by it
pages:read and pages:writeList Pages and Get Page Metadata name pages:read. Update Page Metadata names pages:writeReading pages and editing titles, meta descriptions and Open Graph fields need the optional Pages scope
Endpoints closed to site tokensNo access to authorization, custom code or workspace activity log endpointsCustom code is out of reach for the Ryze AI connection

Webflow's own MCP server works differently. It signs in with OAuth, each authorization covers one workspace and the sites you choose, and only site owners and admins can authorize it. The Ryze AI connection uses one token for one site.

Not included: pages, titles and meta descriptions without the Pages scope. A site publish on the minimum token. Required image, file or multi-reference fields, which Ryze AI cannot fill. Other sites, because a site token only sees its own. Assets, forms, components, ecommerce, comments and custom code, none of which the 3 Webflow tools list.

Sources: Webflow site tokens, Webflow scopes, Webflow: list pages, Webflow: update page metadata, Webflow: publish site, Webflow: publish items, Ryze AI help center page for Webflow. Checked November 14 and 15, 2026.

Removing access

To stop access from VS Code, open Chat: Open Customizations, select MCP Servers and disable or uninstall the ryze server from its ellipsis menu. Stop is weaker: it ends the current run and a later request can start the server again. To end Webflow access itself, disconnect Webflow in Ryze AI and revoke the token in Webflow under Site settings > Apps & Integrations > API access.

What Copilot Chat can do in Webflow

The Ryze AI connector exposes 3 Webflow tools: 1 read, 1 write and 1 delete. Each acts through the Webflow Data API on the connected site. Reads, writes and deletes are separate tools, so VS Code can ask about each one on its own. The tool names come from the Ryze AI product facts and were not seen in a live connector.

ToolTypeWhat it does
webflow__readReadReads from the connected Webflow site through the Webflow Data API (GET), such as sites, pages, collections and collection items. Pages need the Pages scope on the token.
webflow__writeWriteCreates or updates resources on the connected site, such as CMS items (live or draft) and static page SEO and Open Graph fields, and can publish the site.
webflow__deleteDeleteDeletes a resource on the connected site by path, such as a CMS item.

A few limits hold in every client. The token sees one site. Publishing fails with a token that has no CMS write access. Static page SEO edits need the Pages scope, and a full site publish is not promised on the default token. Required image, file and multi-reference fields in a collection must be optional or carry a default.

A new VS Code session uses Manual permissions unless a setting or an organization default says otherwise, so a Webflow call that is not auto-approved shows its tool name and inputs before it runs. Watch Chat: Manage Tool Approval, because the top-level checkbox for ryze trusts every tool on the server, webflow__delete included. Setting a tool to false in chat.tools.eligibleForAutoApproval keeps it on manual approval, while Allow all and Autopilot approve everything. The Ryze AI chat itself starts on Skip all approvals and can switch to Approve write & delete or Manual approve. Article publishing from a Content Plan follows Publishing mode in SEO > Preferences > Publishing, which is Automatic by default or Manual.

Limits in numbers

Webflow sets most of these numbers, in its own units. The Data API limits apply to the site token that Ryze AI holds, and Webflow tracks them per API key. The pages opened for this guide give no data delay or retention figure for CMS, pages or sites data.

LimitFigureSource
Requests per minuteStarter and Basic plans 60. CMS, eCommerce and Business plans 120. Enterprise custom. Counted per API keyWebflow rate limits
Over the limitHTTP 429 Too Many Requests with a Retry-After header, typically 60 seconds, and the error code too_many_requests. Every response carries X-RateLimit-Remaining and X-RateLimit-LimitWebflow rate limits
Site publishOne successful publish queue per minuteWebflow publish site
Items per list requestlimit up to 100 records, paged with offset. Up to 10 custom filter terms, 2 text-search terms and 3 sort fieldsWebflow list items
Bulk writesCreate Items takes up to 100 items per request, counting every locale variant. Update Items is limited to 100Webflow create items
Fields per collectionA collection's schema can have up to 60 fieldsWebflow collections and items
Site tokensUp to 5 per site. Expire after 365 consecutive days of inactivityWebflow site tokens
Cached content deliveryCached requests have effectively no rate limit. Uncached ones count against the plan's limitWebflow rate limits
VS Code128 enabled tools per chat requestVS Code tools

Sources: Webflow rate limits, Webflow: list items, Webflow: create items, Webflow: manage collections and items, Webflow: update items, VS Code tools, Ryze AI help center page for Webflow. Checked November 14 and 15, 2026.

First 3 prompts to run

These prompts use only what the 3 tools document. What comes back is your own site content, so no sample output is shown, and none of these calls was run for this guide.

1. Map the CMS

List the CMS collections on my Webflow site and the fields in each one.

Tools used: webflow__read

What comes back: The collections and their fields, as the Webflow Data API returns them. Nothing is changed.

2. Audit the blog collection

List the items in my blog collection with name, slug and publish status, and flag any item whose summary or featured image field is empty.

Tools used: webflow__read

What comes back: A list of items with the fields you named, up to 100 per request, and the empty fields picked out of the returned data. Nothing is changed.

3. Draft one item

Create a draft CMS item in the blog collection with the title, slug and body I give you, then read it back so I can check it is still a draft.

Tools used: webflow__write, webflow__read

What comes back: A write call that creates the item once you approve it in VS Code, then a read of the saved item so you can compare it with your request.

Replace the collection and the field names with your own. Read each write and delete call before you approve it in VS Code.

10 jobs to hand to Copilot Chat

Ten jobs to type into Copilot Chat once the ryze server is running, each with the tool behind it and whether the default token covers it. The default token has CMS Read and write and Sites Read-only, without the Pages scope. No job was run for this guide, because no Webflow site was connected.

JobAsk CopilotToolOn the default token
Collection mapList my CMS collections and the fields each one has.webflow__readYes
Blog inventoryList the items in the blog collection with name, slug and publish status.webflow__readYes
Gap checkFind blog items where the summary or the featured image is empty.webflow__readYes. The check runs on the returned field data
Site detailsShow my site's name, custom domains and locales.webflow__readYes
Create a draftCreate a draft item from this title, slug and body.webflow__writeYes, after you approve the call
Edit an itemUpdate the excerpt and the body of this item.webflow__writeYes, after you approve the call
Go liveCreate or update this item directly on the live site.webflow__writeYes, after you approve the call. This skips the draft stage
Delete an itemDelete this CMS item.webflow__deleteYes. Keep this tool on manual approval
Pages without metaList static pages whose title or meta description is empty.webflow__readNo. Needs the optional Pages scope
Rewrite page SEORewrite this page's title, meta description and Open Graph fields.webflow__writeNo. Needs Pages Read and write

7 ways to connect VS Code to Webflow

Seven ways can bring a Webflow site into Copilot Chat in VS Code. They differ in where they run, what they sign in with and how much of Webflow the assistant can touch. This guide treats the Ryze AI connector as the main way, because the site is connected once in Ryze AI, VS Code holds one hosted address and reads, writes and deletes stay separate tools. The other six were read on their own pages on November 15, 2026, and none was set up for this guide.

WayRuns whereSetup in VS CodeWhat it reaches in WebflowPrice
Ryze AI connector (the main way)Hosted by Ryze AI at one addressChat: Open Customizations > MCP Servers > Add Server (+), HTTP, ID ryze, saved to Copilot Global, or an mcpServers entry in a portable file. Sign in to Ryze AI in the browser. The Webflow token is given to Ryze AI onceSites, CMS collections and items to read, create, update and delete, live or draft. With the Pages scope also page titles, meta descriptions and Open Graph fields. One site per tokenSEO Starter is $129 per month with a 3-day free trial
Webflow MCP server (Webflow's own)Hosted by Webflow at https://mcp.webflow.com/mcpWebflow's install pages cover ChatGPT, Claude Code, Claude Desktop, Grok Build, Postman and Slack, not VS Code. Its getting-started page says any agent that supports MCP servers can connect manually with the URL. Sign-in is OAuth, where you choose the sites and Workspaces and click Authorize AppMuch wider: design and build tools for pages, elements, styles and components, CMS, SEO metadata, assets, forms, custom code and Webflow's Analyze, Optimize and AEO data. The tool reference lists 37 names, while Anthropic's directory says 34. Only site owners and admins can authorize it, and each authorization covers one workspaceNo price is stated for the server. Webflow's pricing page lists it among plan features
Webflow beta MCP serverHosted by Webflow at https://mcp.webflow.com/beta/mcpManual URL only. Webflow's connector and plugin point at the production server. At its launch on December 9, 2025 it was limited to Official Webflow MCP Testing partners, and the beta page no longer says soExperimental tools and early-access API featuresNot stated
webflow-mcp-server on npmOn your computer, started with npxA command entry with WEBFLOW_TOKEN in env. The README shows Cursor and Claude Desktop configs, so a VS Code entry would be your own translation. Needs Node.js 22.3.0 or higher. Designer features need your own registered MCP Bridge AppThe Data API with your own token. Version 1.0.0 was published on September 17, 2025. The README still shows the retired /sse remote addressFree, MIT licence. 142 GitHub stars, last push November 13, 2026
ComposioHostedA hosted MCP address, https://connect.composio.dev/mcp, added to VS Code as an HTTP server. Composio's per-client pages for VS Code were not opened. Webflow connections must go through your own OAuth app, registered once with Webflow60 tools on the Webflow toolkit page, read and write, including bulk create of up to 100 items, delete, orders, webhooks and assetsFree plan: 10,000 tool calls a month on the pricing page. Standard is $18 per seat per month
Zapier MCPHostedZapier lists VS Code among its supported MCP clients. Add Zapier as a connector and sign in, and Zapier turns on actions for apps already linked to your Zapier account8 actions shown before Load More, among them Create Item, Update Item, Create Live Item, Fulfill Order and API Request (Beta). The page states no totalOne tool call uses 2 tasks from your Zapier plan
Kvalifik/mcp-routerA desktop app on your computer (macOS, Windows x64)Add a Webflow connection in the app, enable projects and set per-project permissions, then connect an AI app from its Apps screen. The README names VS Code among the appsWebflow projects across several workspaces through one connection, with access levels per project. No tool count is givenFree, under a source-available licence that is not OSI-approved. Not affiliated with Webflow, per its README

Webflow options that do not fit this job

  • The Webflow connector in Claude and the Webflow app in ChatGPT. Both are listings of Webflow's own server inside those two assistants. They are not VS Code routes, and neither page offers a setup for it.
  • The Webflow plugin in Cursor's marketplace. Webflow calls the client Grok Build (formerly Cursor), and the steps use Cursor's marketplace and .cursor/mcp.json.
  • Webflow Skills. These are workflows for agents that support skills, and Webflow names Claude Desktop, Claude Code and Grok Build. They need the Webflow MCP server and are not a connection.
  • kapilduraphe/webflow-mcp-server. A small open-source server with 2 read-only tools, get_sites and get_site, and no CMS access. Its README covers Claude Desktop.
  • The Webflow documentation MCP server. It gives an agent Webflow's developer docs and API references and no site data.
  • The old /sse address. Webflow replaced https://mcp.webflow.com/sse with https://mcp.webflow.com/mcp on November 24, 2025, and its January 17, 2026 changelog says SSE is fully deprecated.
  • Webflow in Slack and in Postman. Webflow documents both as separate surfaces, and neither brings a site into VS Code.

Which one to pick

Ryze AI is the best way to connect VS Code to Webflow for managing CMS items and publishing blog content through one hosted address and a site-scoped token, with one caveat: it has 3 tools, so it does not build pages or styles, and page SEO edits need the optional Pages scope. Webflow's own server is the better pick when you design and build in Webflow, because it reaches the Designer, components, assets and forms, and it uses OAuth instead of a token. Zapier and Composio fit teams that already route other apps through them, and the npm package suits someone who wants to run the server locally with their own token. VS Code caps a chat request at 128 tools, and Webflow's server alone lists 37 names, so switch off servers you do not need.

Sources: Webflow MCP server overview, Webflow MCP getting started, Webflow MCP how it works, Webflow MCP FAQ, Webflow MCP data tools, Webflow beta MCP server, Webflow documentation MCP server, webflow/mcp-server on GitHub, webflow-mcp-server on npm, Webflow pricing, Composio Webflow toolkit, Composio pricing, Zapier MCP for Webflow, Zapier MCP quickstart, Kvalifik/mcp-router, kapilduraphe/webflow-mcp-server, Webflow Skills, Webflow in Claude's directory, Webflow MCP in ChatGPT, Webflow MCP in Slack, Ryze AI help center page for Webflow. Checked November 14 and 15, 2026.

Webflow, Copilot and MCP: dates that matter

DateWhat happened
April 4, 2025VS Code 1.99, the March 2025 release, came out with MCP server support in agent mode.
April 8, 2025Webflow announced its official MCP server and LLMS.txt support in its changelog.
September 4, 2025Webflow's MCP server gained Designer API support, with a companion app that installs during authorization.
September 17, 2025webflow-mcp-server 1.0.0 was published on npm and as a GitHub release.
November 24, 2025Webflow moved its MCP server from SSE to HTTP, replacing https://mcp.webflow.com/sse with https://mcp.webflow.com/mcp.
December 9, 2025Webflow launched a beta MCP server at https://mcp.webflow.com/beta/mcp, then for testing partners only.
January 17, 2026Webflow MCP v1.0.1 consolidated 46 or more data tools into 19 and fully deprecated the /sse endpoint.
April 1, 2026Webflow MCP v1.2 added element tools, variables and a webhook tool.
September 21, 2026Webflow MCP v2.1 added Interactions with GSAP, Webflow Cloud and Campaigns tools and CMS field groups.
September 30, 2026VS Code 1.140 added Copilot Global and the workspace .mcp.json as destinations in MCP: Add Server.
October 22, 2026VS Code 1.143 made the Copilot harness the default for new sessions.
November 11, 2026VS Code 1.146 deprecated the Local harness that reads .vscode/mcp.json, with removal announced for February 2027.

Webflow's skill migration guide also names MCP v2.0 and v2.2 without a release date, so no date is given for them here.

Sources: Webflow changelog, April 8, 2025, Webflow changelog, September 4, 2025, VS Code 1.99, Webflow changelog, November 24, 2025, Webflow changelog, December 9, 2025, Webflow changelog, January 17, 2026, Webflow changelog, April 1, 2026, Webflow changelog, September 21, 2026, VS Code 1.140, VS Code 1.143, VS Code 1.146, webflow-mcp-server on npm. Checked November 14 and 15, 2026.

How this guide was tested

The record for this guide is short, because no Webflow site was connected and nothing was run inside VS Code. What exists is a reading of vendor pages, listed below.

CheckResult
Calls to WebflowNone. No Webflow test account was connected, so no Webflow call was run and nothing on this page comes from a site.
The Webflow tool listNot seen in a live connector. The three names in the tools table come from the Ryze AI product facts.
Webflow's developer docsThe MCP pages, Data API reference, changelog, npm and GitHub records were read on November 15, 2026.
VS Code and GitHub docsMicrosoft's VS Code pages and GitHub's Copilot docs were read on November 14, 2026.
Other ways in the comparisonRead from their own pages on November 15, 2026. None was installed.

Not run for this guide: anything inside VS Code. The ryze server was not added to Copilot Global, no trust prompt or sign-in was seen, and Copilot Chat sent no tool call. No Webflow token was generated. The VS Code steps follow Microsoft's documentation pages dated November 11, 2026 and GitHub's Copilot docs. Whether VS Code can sign in to the Ryze AI connector without a pre-registered client was not tried. Webflow's own server and the other ways in the comparison were not set up.

Errors and fixes

The MCP server does not start in VS Code
On Copilot Business or Enterprise, ask an administrator to enable the MCP servers in Copilot policy, which ships off. Admins can also block a server with deniedMcpServers or turn MCP off with chat.mcp.access set to none, and a local file cannot override either. Check the version too: MCP needs VS Code 1.99 or later and Copilot Global needs 1.140.
The sign-in never opens
Trust and sign-in are separate steps, so trust the server first. Then choose Authenticate from the ellipsis menu of ryze in MCP Servers, or run MCP: List Servers to see its state. Show Output in the same menu opens the log. Email Ryze AI support if it stays stuck.
An older tutorial does nothing
Tutorials built on .vscode/mcp.json target the Local harness. New sessions have used the Copilot harness since VS Code 1.143, which reads ~/.copilot/mcp-config.json and the workspace .mcp.json. Add the server again through Chat: Open Customizations.
No Webflow tools appear
If Webflow was connected in Ryze AI after the server was added, remove the ryze server, add it again and start a new chat so the tool list refreshes. The Webflow tools also need an active Ryze AI plan or trial.
Publishing fails
Ryze AI's facts say publishing fails with a token that has no CMS write access. Generate a new token with CMS set to Read and write and connect it again.
Ryze AI says a collection field blocks publishing
Required image, file and multi-reference fields cannot be filled automatically. Make the field optional in Webflow or give it a default.
Page titles and meta descriptions cannot be read or changed
The default token has no Pages scope. Generate a token with Pages set to Read and write and connect it again.
Webflow answers HTTP 429
The site plan's rate limit was hit. Webflow's response carries a Retry-After header, typically 60 seconds, and the code too_many_requests. Wait, then ask for smaller batches.
The connection stops working after a long gap
Webflow expires a site token after 365 consecutive days of inactivity. Generate a new token and reconnect.
Ryze AI refuses a Webflow connection link
A connection link is refused while a Webflow connection already exists in the workspace. Disconnect the old one with the trash icon first.
Copilot sees a different site than expected
A site token only sees the site it was created on. Disconnect Webflow in Ryze AI and connect again with the token of the site you mean.
Cannot have more than 128 tools per request.
VS Code allows 128 enabled tools in one chat request. Deselect tools or whole MCP servers in the tools picker of the Chat view until the count drops.

Terms on this page

Agent Customizations editor
The VS Code screen opened by Chat: Open Customizations. Its MCP Servers page adds, lists and manages servers.
Copilot Global
The personal MCP destination in VS Code, ~/.copilot/mcp-config.json, read in every workspace.
Site API token
A key created in a Webflow site's settings that lets an integration use the Data API on that one site with the scopes chosen at creation. Only site administrators can create one.
Scope
A permission on a token that decides which Webflow data it can reach. Scopes come in read and write pairs, such as cms:read and cms:write.
CMS collection and item
A collection is a group of CMS items that share a template, such as blog posts. An item is one record in it, such as a single post.
Draft and Changes in draft
An item created as a draft stays in Draft status. Updating a published item as a draft sets Changes in draft, and the live item stays as it was until the changes are published.
MCP Bridge App
The companion app that installs when you authorize Webflow's own MCP server. It links a live Designer session to that server and is not part of the Ryze AI connection.

Sources: VS Code MCP servers, VS Code MCP configuration reference, Webflow site tokens, Webflow scopes, Webflow rate limits, Webflow MCP how it works, Webflow: manage collections and items. Checked November 14 and 15, 2026.

Frequently asked questions

How do I connect VS Code to Webflow?

Generate a site token in Webflow under Site settings > Apps & Integrations > API access and connect it in Ryze AI under Integrations. In VS Code, with Copilot as the session target, run Chat: Open Customizations, select MCP Servers, choose Add Server, pick HTTP, enter https://connector.get-ryze.ai/mcp and the server ID ryze, trust the server and finish the Ryze AI sign-in.

Is there a Webflow MCP server for VS Code?

Yes, several. The Ryze AI connector at https://connector.get-ryze.ai/mcp has 3 Webflow tools for your connected site. Webflow runs its own server at https://mcp.webflow.com/mcp, which does not name VS Code on its install pages but accepts any MCP client by URL. Composio, Zapier, an npm package and a desktop router are further options.

What is the Webflow MCP server URL?

For the Ryze AI connector the address is https://connector.get-ryze.ai/mcp, the same for every user. Webflow's own server is at https://mcp.webflow.com/mcp, and its beta server at https://mcp.webflow.com/beta/mcp. The older https://mcp.webflow.com/sse address is deprecated.

Which Webflow server should I use in VS Code?

For CMS items and blog publishing through one address and a site-scoped token, use the Ryze AI connector, which needs a Ryze AI plan. For building pages, styles, components and assets, use Webflow's own server, which signs in with OAuth. The two can run side by side, within VS Code's cap of 128 tools per request.

Is VS Code a supported client for the Webflow MCP server?

Webflow's install pages do not name VS Code. They cover ChatGPT, Claude Code, Claude Desktop, Grok Build, Postman and Slack, and the getting-started page says any agent that supports MCP servers can connect manually. Whether a given client works is up to that client's OAuth support, which was not tested here.

Do I need a Webflow API token for the Ryze AI connection?

Yes. Ryze AI connects to Webflow with a site API token generated by a site administrator, with CMS set to Read and write and Sites set to Read-only. Pages Read and write is optional and only needed for page title and meta description edits. There is no OAuth app to install on Webflow's side.

Which Copilot plan do I need?

Any plan. GitHub's plans tables include MCP on Copilot Free, Student, Pro, Pro+, Max, Business and Enterprise, and GitHub's MCP article asks for VS Code 1.99 or later. Copilot Free, Pro, Pro+ and Max are outside the MCP policy. On Business or Enterprise through an organization, an administrator must enable the MCP servers in Copilot policy, which is off by default.

Can Copilot Chat edit my Webflow CMS items?

Yes. Through Ryze AI, Copilot Chat can create and update CMS items, as drafts or live, with the write tool. New VS Code sessions start on Manual permissions, so a call that is not auto-approved shows its tool name and inputs first.

Can Copilot Chat delete Webflow content?

Only through the separate webflow__delete tool, which deletes a resource by path, such as a CMS item. Allow all, Autopilot or a server-wide approval in Chat: Manage Tool Approval skips the check, so keep the ryze server on manual approval if you want to review deletes.

Can Copilot change page titles and meta descriptions in Webflow?

Only with the optional Pages Read and write scope on the token. With it, the write tool can change static page titles, meta descriptions and Open Graph fields and then publish the site. Without it, Copilot cannot change a page's title or meta description.

How do AI tools publish articles to Webflow?

Ryze AI publishes Content Plan articles into the CMS collection you choose and fills title, slug, body, excerpt, date and featured image automatically. SEO Starter allows up to 90 articles per billing cycle and up to 3 a weekday. Publishing mode in SEO > Preferences > Publishing is Automatic by default or Manual.

Can I connect more than one Webflow site?

Not at once. Ryze AI keeps one Webflow connection per 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 the Webflow tools not show up in VS Code?

If you connected Webflow in Ryze AI after adding the server, remove the ryze server, add it again and start a new chat. Also confirm that you trusted the server and finished the Ryze AI sign-in, which are separate steps, and expand a tool call to see which server answered.

Which config file should I use?

For new setups use the portable format: ~/.copilot/mcp-config.json or .mcp.json at the workspace root, with the key mcpServers. The .vscode/mcp.json file with the key servers belongs to the Local harness, which VS Code 1.146 deprecated, with removal announced for February 2027.

How much does it cost to connect VS Code 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, Paid Ads is $89 per month with a 7-day free trial and Agency is $279 per month. Annual billing takes 30% off the first year.

How do I disconnect Webflow from VS Code?

In Chat: Open Customizations, select MCP Servers and disable or uninstall the ryze server from its ellipsis menu. To end Webflow access itself, disconnect Webflow in Ryze AI and revoke the token in Webflow under Site settings > Apps & Integrations > API access.

Connect Webflow to VS Code with Ryze AI

One Ryze AI connector URL carries the 3 Webflow tools to GitHub Copilot Chat in VS Code. SEO Starter is $129 per month with a 3-day free trial; annual billing takes 30% off the first year.

Webflow MCP server

Need help? Read the Ryze AI help center page for Webflow or email Ryze AI support.