How to connect Microsoft Copilot to Webflow

Paste a Webflow site token into Ryze AI once, add one MCP URL as a tool on a Copilot Studio agent or a Microsoft 365 Copilot declarative agent, then ask about CMS collections, items and page SEO.

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

Paste it as the Server URL of a Model Context Protocol tool on a Copilot Studio agent. See the steps

See pricing

By Ira Bodnar, Ryze AI · Updated · Test record: what was and was not run

Quick answer

The main way to connect Microsoft Copilot to Webflow is the Ryze AI connector. Microsoft's pages show no Copilot chat window with a field for an MCP address, so the connector goes onto an agent: paste a Webflow site token into Ryze AI, then on a Copilot Studio agent add https://connector.get-ryze.ai/mcp as a Model Context Protocol tool with OAuth 2.0 and Dynamic discovery. The agent then holds 3 Webflow tools, 1 read, 1 write and 1 delete, which cover sites, collections, CMS items and, with an extra token scope, page SEO fields.

  1. In Webflow open Site settings, go to Apps & Integrations and generate an API 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, then pick the site and the CMS collection
  3. In Copilot Studio switch to the classic experience, open your agent, then Tools, Add a tool, New tool, Model Context Protocol
  4. Enter the server details, pick OAuth 2.0 with Dynamic discovery, sign in to Ryze AI, add the tool and ask about your collections in the test chat

Microsoft Copilot to Webflow at a glance

FactDetail
Main way to connectThe Ryze AI connector: a hosted MCP server that a Copilot Studio agent takes as a tool. A Microsoft 365 Copilot declarative agent can take it as an action, a route not yet confirmed for Ryze AI
Server addresshttps://connector.get-ryze.ai/mcp, the same for every user
Where it goes in CopilotOn an agent. Classic experience: Tools > Add a tool > New tool > Model Context Protocol. New experience: Build tab > Tools > Add > Model Context Protocol (MCP). No chat window has a documented field for it
Sign-inCopilot signs in to Ryze AI with OAuth 2.0 and Dynamic discovery. Webflow is joined once inside Ryze AI with a site token, so no Webflow token is typed into Copilot
Webflow tools3: 1 read, 1 write and 1 delete
Can the agent change the siteYes. The write tool creates and updates CMS items (live or draft) and can publish the site, and the delete tool removes items. Page titles and meta descriptions change only if the token has the optional Pages scope
Other data in the same chatOther platforms connected in the same Ryze AI workspace are served by the same URL
Copilot planMicrosoft's MCP pages name none. A Copilot Studio trial cannot publish an agent, and the Copilot Studio for Teams plan lacks generative orchestration and Power Platform connectors
Ryze AI priceSEO Starter is $129 per month with a 3-day free trial. Adding the connector costs nothing; the Webflow tools need an active plan or trial
Webflow's own option for CopilotWebflow MCP at https://mcp.webflow.com/mcp, OAuth, hosted by Webflow. Webflow's pages name Claude, ChatGPT, Codex and Grok Build and no Microsoft product, so a Copilot Studio sign-in to it is untested
Last testedNothing was run through the connector against Webflow and nothing was run inside a Microsoft product. Microsoft pages read November 14, 2026, Webflow pages read November 15, 2026

Before you start

  • A Copilot Studio agent or a Microsoft 365 Copilot declarative agent. Adding a tool is a maker or admin task, normally done in a work or school tenant. Microsoft says Copilot Studio is open to all Microsoft 365 users for creating agents and actions. A Copilot Studio trial can create and test agents, but publishing them needs a paid plan.
  • A Copilot Studio plan that carries MCP. Microsoft documents that MCP access in Copilot Studio relies on Power Platform connectors, and its licensing page marks Power Platform connectors and generative orchestration as not available in the Copilot Studio for Teams plan. No Microsoft sentence says whether MCP tools run on that plan, so test before you promise it.
  • A Webflow site token. Only a site administrator can create one, in Site settings > Apps & Integrations > API access. Set CMS to Read and write and Sites to Read-only. Set Pages to Read and write as well if you want the agent to read pages or edit page SEO fields. Webflow lets a site hold up to 5 tokens.
  • At least one CMS collection on the site. Ryze AI asks you to pick the site and the collection after you paste the token. A token sees only the site it was created on.
  • A Ryze AI workspace on a plan or free trial. SEO Starter is $129 per month with a 3-day free trial and covers Content Plan articles that publish into a Webflow CMS collection, up to 90 per billing cycle. Annual billing takes 30% off the first year. Connecting the connector is free, and the Webflow tools need an active plan or trial.

How to connect Microsoft Copilot to Webflow

Two steps happen in Webflow and Ryze AI, three in Copilot Studio, and the last is your first question. The connector URL is the same for every user.

  1. Generate a Webflow site token

    In Webflow open Site settings, then Apps & Integrations, and scroll to API access. Select Generate API token and give it a name. Set CMS to Read and write and Sites to Read-only. Optionally set Pages to Read and write for page-level SEO edits. Generate the token and copy it, because Webflow shows it once.

  2. Connect Webflow in Ryze AI

    In Ryze AI open Integrations, click Connect on the Webflow card and paste the site token. Pick the site that hosts your blog and the CMS collection that articles publish to. Do this before you add the connector to Copilot.

  3. Open the agent and start a new MCP tool

    These steps are for the classic experience (the standard harness). New agents from the Copilot Studio home page run on the Microsoft Copilot harness, so switch first: select the three dots at the bottom of the home page side bar, then Open classic experience, which lasts for the session. Open your agent and go to its Tools page. Select Add a tool, then New tool, then Model Context Protocol in the Create new section. The MCP onboarding wizard opens.

  4. Fill in the server details and choose the sign-in

    Server name: Ryze AI. Server description: a plain note on what the tools do, for example Reads and edits Webflow CMS items and page SEO fields. Microsoft says the agent orchestrator uses this description to decide when to call the server. Server URL: https://connector.get-ryze.ai/mcp. Set the authentication type to OAuth 2.0 and the OAuth type to Dynamic discovery, which is meant for servers that support dynamic client registration, so no client ID, secret or callback URL is typed. Select Create, then Next.

    https://connector.get-ryze.ai/mcp
  5. Create the connection and add the tool

    On Add tool, select Create a new connection and complete the Ryze AI sign-in, or pick an existing connection. Microsoft's page stops at that button and does not show the sign-in window, and this step was not run for this guide. Then select Add to agent.

  6. Ask about your collections in the test chat

    Open the agent's test chat and try: List the CMS collections on my Webflow site and show the fields of the blog collection. Copilot Studio turns on all of the server's tools by default, so decide before you publish the agent whether webflow__write and webflow__delete should stay on.

The Ryze AI help center page for Webflow covers the Webflow side of the connection. There is no Ryze AI help center page for Microsoft Copilot.

Sources: Microsoft, connect an existing MCP server to an agent, Microsoft, switch between experiences, Ryze AI Webflow guide, Webflow, site tokens. Microsoft pages checked November 14, 2026.

Microsoft 365 agents and other routes

Microsoft 365 Copilot declarative agent

If your team works in Microsoft 365 Copilot and not in Copilot Studio, the same URL can sit in a declarative agent as an MCP action. Microsoft documents this route in its Agents Toolkit walkthrough. It was not run for Ryze AI.

  1. In Visual Studio Code open Microsoft 365 Agents Toolkit, version 6.12.0 or later, and select Create a New Agent/App, then Declarative Agent.
  2. Select Add an Action, then Start with an MCP Server, and enter https://connector.get-ryze.ai/mcp.
  3. Choose OAuth with dynamic registration, then pick a project location and an agent name.
  4. In the Accounts pane sign in to Microsoft 365 and confirm that Custom App Upload Enabled and Copilot Access Enabled show, then select Provision in the Lifecycle pane.
  5. At m365.cloud.microsoft/chat open the agent, whose name ends in dev, ask a question and select the sign-in button when Copilot asks.

Microsoft says Agents Toolkit sets a new MCP plugin to dynamic tool discovery, so Copilot reads the server's tool list at run time and you add no tools by hand. Sideloading needs Upload custom apps switched on by an admin in the Teams admin center. For dynamic registration Microsoft also requires that the authorization server issues a client secret, which was not checked for Ryze AI. The first time the agent uses the plugin, Copilot asks the person to allow or cancel. After that, tools that only read do not ask again, and tools that change data do.

Other places Microsoft accepts an MCP address

Microsoft documents more places that accept an MCP address than the two above. Each changes who does the setup and how sign-in works.

RouteWhat Microsoft documents
Copilot Studio, new experience (Microsoft Copilot harness)Open the agent, go to the Build tab, select Tools, then Add next to the search bar, then Model Context Protocol (MCP). The Add MCP server page asks for a name, a description, the server URL and an authentication choice. Microsoft's page for this flow carries a preview label and does not list its sign-in choices, so this guide does not say that it offers Dynamic discovery.
Microsoft 365 admin center, custom federated connectorAn admin goes to Copilot > Connectors > Gallery, creates a new connector and enters a base URL. The sign-in choices are Microsoft Entra SSO, OAuth 2.0 with a client registered by hand, or no authentication. Dynamic client registration is not among them, and the Ryze AI facts name no fixed client ID and secret, so this route is not confirmed for Ryze AI.
Plugin package or Agent 365 CLIA developer can name a remote MCP server in a plugin package manifest, or register it with the Agent 365 CLI for admin approval. Both are developer routes that were not checked against the Ryze AI connector.
Copilot chat window and personal CopilotNo Microsoft page shows a field in a Copilot chat window for typing an MCP address. Personal Copilot at copilot.com lists four fixed connector services and documents no way to add your own.

Copilot and MCP: the facts in one table

TopicWhat Microsoft's documentation says
Where servers are addedOn an agent: the Tools page in Copilot Studio, Add an Action in Agents Toolkit, or the Connectors gallery for admins
TransportsCopilot Studio supports Streamable only. SSE support ended after August 2025
Sign-in choices in Copilot StudioNone, API key (header or query parameter) or OAuth 2.0 with Dynamic discovery, Dynamic or Manual
Who signs inEach person signs in to the server with their own account. A Copilot Studio tool uses end user credentials by default, and maker-provided credentials is the other choice
Tool approvalCopilot Studio turns on all tools of a new MCP server. Microsoft 365 declarative agents ask on first use and before tools that change data
Tools per agentWith generative orchestration the standard harness takes up to 128 tools per agent, and Microsoft suggests 25 to 30. Each MCP server counts as one tool
Admin controlsA Power Platform data policy on connectors also governs the MCP server. In the Microsoft 365 admin center, Agents > Tools > Registry can block a server
Local serversNo field for a command that starts a server on your computer. Every route takes an HTTPS address that Microsoft's service can reach

Sources: Microsoft, build MCP plugins, Microsoft 365 Copilot extensibility prerequisites, Microsoft, custom federated connectors, Microsoft, plugins overview, Microsoft, add tools to an agent, Copilot Studio licensing. Checked November 14, 2026.

Claude and ChatGPT

The same connector URL works in other MCP clients, and your Webflow site stays connected once in Ryze AI. Guides for Webflow:

Claude

Add https://connector.get-ryze.ai/mcp as a custom connector under Customize > Connectors, pick the workspaces and start a new chat. How to connect Claude to Webflow.

ChatGPT

Add the same URL as an app under Settings > Apps, pick the workspaces and start a new chat. How to connect ChatGPT to Webflow.

Webflow access and scope

Two sign-ins are involved, and each limits what the agent can reach.

Which Webflow site
The site the token was created on. Webflow site tokens are made per site, and a Ryze AI workspace holds one Webflow connection. A connection link is refused while one already exists.
Which Webflow scopes apply
The scopes chosen when the token was generated. Webflow names them in read and write pairs, such as cms:read and cms:write. The Ryze AI settings use CMS Read and write and Sites Read-only, with Pages Read and write as an option.
What Copilot does first
Copilot Studio turns on every tool of a new MCP server. Nothing waits for your click unless you switch the tools off or build a declarative agent, where Copilot asks before tools that change data.

Access behind each action

The table sets each kind of action against the Webflow scope its API reference names. The Ryze AI settings come from the Ryze AI Webflow facts.

Action in Ryze AIWebflow scope and tool
List collections, their fields and itemswebflow__read, with CMS Read (cms:read) in Webflow's reference
Read the site's detailswebflow__read, with Sites Read (sites:read)
List pages or read page metadatawebflow__read, with Pages Read (pages:read). This is the optional Pages scope, which the minimum token lacks
Create or update CMS items, live or draftwebflow__write, with CMS Write (cms:write)
Change a page's title, meta description or Open Graph fieldswebflow__write, with Pages Write (pages:write). Needs the optional Pages Read and write setting
Publish CMS itemswebflow__write. Webflow lists cms:write for publishing items
Publish the whole sitewebflow__write can publish the site, but Webflow's Publish Site reference names sites:write while the Ryze AI token has Sites Read-only. This was not tested, so check it on a test site before relying on it
Delete a CMS itemwebflow__delete, with CMS Write (cms:write)

The Webflow site token behind the connection

The connection is a Webflow site token. Webflow describes site tokens this way, and the table sets that against how Ryze AI uses one.

ItemWhat Webflow saysWith Ryze AI
Key typeSite API token, made in Site settings > Apps & Integrations > API accessPasted once into the Webflow card in Ryze AI. No OAuth app is installed on the Webflow side
Who can create itOnly site administratorsA designer or editor without that role cannot generate the token
SiteCreated per site, reaches that site onlyOne Webflow connection per Ryze AI workspace
Life of the tokenExpires after 365 consecutive days of inactivity. Up to 5 tokens per siteGenerate a new token and reconnect if it lapses
What a site token cannot reachAuthorization, custom code and workspace activity log endpointsNot available to the agent
ScopesChosen when the token is generated, in read and write pairsCMS Read and write and Sites Read-only are required. Pages Read and write is optional

Not covered by the Ryze AI tools or the minimum token: page reads and page SEO edits without the Pages scope, assets, forms, components, ecommerce, comments and custom code. The Ryze AI Webflow tools return site, page and CMS content, and they do not return analytics or other metrics.

Sources: Webflow, site tokens, Webflow, scopes, Webflow, publish site, Webflow, update page settings, Ryze AI Webflow guide. Checked November 15, 2026.

Removing access

To take Webflow away from a Copilot Studio agent, open its Tools page in the classic experience, hover over Ryze AI, select the three dots and Delete. To cut Webflow off from Ryze AI, open the Webflow card, click View, and disconnect with the trash icon. To kill the token itself, open Site settings > Apps & integrations > API access in Webflow, find the token and select revoke.

What Copilot can do in Webflow

The Ryze AI connector exposes 3 Webflow tools: 1 read, 1 write and 1 delete. Writes and deletes are separate tools, so a Copilot agent can be set up to treat them differently.

ToolTypeWhat it does
webflow__readReadReads from the connected Webflow site through the Webflow Data API (GET), such as sites, pages, collections and collection items.
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.

Some limits apply in every client. A site token sees only its own site. Page edits need the Pages scope, and the required image, file or multi-reference fields of a collection cannot be filled automatically, so they must be made optional or given a default. Publishing fails with a token that has no CMS write access.

In Copilot Studio, a new MCP server arrives with every tool turned on (Allow all), and Microsoft does not describe a confirmation prompt for MCP tools there. To keep a person in the loop, turn Allow all off and switch off webflow__write and webflow__delete in the server's tool list on the Tools page, or use a declarative agent, where Copilot asks on first use and before tools that change data. Separately, the Ryze AI chat has a Tool approvals picker that starts on Skip all approvals; you can switch it to Approve write & delete or Manual approve in the message box, and article publishing follows Publishing mode under SEO > Preferences > Publishing, which is Automatic by default.

Limits in numbers

LimitFigure or ruleSource
Data API rate limit, per API keyStarter and Basic site plans 60 requests per minute. CMS, eCommerce and Business 120. Enterprise custom. Each key is tracked on its own.Webflow rate limits
Over the limitHTTP 429 Too Many Requests with a Retry-After header, typically 60 seconds. The error code is too_many_requests.Webflow rate limits
Site publishOne successful publish queue per minute.Webflow, publish site
Items per list requestUp to 100 records per request, paged with an offset.Webflow, list items
Bulk item writesCreate Items and Update Items take up to 100 items per request. Create Items counts every locale variant.Webflow, create items
Fields per collectionA collection schema can have up to 60 fields.Webflow, manage collections and items
Site tokensUp to 5 per site. A token expires after 365 consecutive days of inactivity.Webflow, site tokens
Ryze AI Content PlanUp to 90 articles per billing cycle and up to 3 a weekday on SEO Starter.Ryze AI plan facts
Tools per Copilot Studio agentUp to 128 with generative orchestration in the standard harness. Each MCP server is added as one tool.Microsoft, add tools to an agent
Transport in Copilot StudioStreamable only.Microsoft, connect an existing MCP server

The Webflow figures are for Webflow's own Data API, which the Ryze AI token uses, so the limit of the site's plan applies to the connection. Webflow's pricing page shows newer plan names, and its developer docs still use the older ones above.

Sources: Webflow rate limits, Webflow, list items, Webflow, create items, Webflow, manage collections and items, Webflow, site tokens, Microsoft, add tools to an agent. Checked November 15, 2026 and November 14, 2026.

First 3 prompts to run

Nothing was run through the connector against Webflow for this guide, so no prompt below has a real result. Each one lists the tool it uses and what the tool is documented to return.

1. List collections and learn the field names

List the CMS collections on my Webflow site, then show the fields of the blog collection so I can use the right field names later.

Tools used: webflow__read

What comes back: The collections of the site and the fields of the one you named. Nothing is changed.

2. Find items with a missing field

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

Tools used: webflow__read

What comes back: The items with their slugs and status, with the empty fields marked. The check runs on the field data that comes back, so the field names depend on your collection. Nothing is changed.

3. Update one item as a draft

Read the item with the slug my-post-slug, rewrite its excerpt from the text I give you, and save it as a draft. Show me the field before and after.

Tools used: webflow__read, webflow__write

What comes back: A read of the item, then an update. Webflow marks an updated item that was already published as having changes in draft, and the live item stays as it was until the changes are published.

The second and third prompts need your own collection and slugs. Replace the names with yours, and check the item in Webflow before you ask for anything live.

10 jobs to hand to a Copilot agent

Ten jobs to hand to a Copilot agent with the Ryze AI tool, each matched to its tool. None was run from Copilot or against a Webflow site for this guide. The last two need the optional Pages scope on the token.

JobAsk the agentToolWorks on the default connection
List collectionsList the CMS collections on the site and the fields each one has.webflow__readYes
List itemsList the items in the blog collection with name, slug and publish status.webflow__readYes
Find gapsFind blog items where the summary or the featured image is empty.webflow__readYes
Read the siteRead the site's name, custom domains and locales.webflow__readYes
Create a draftCreate a draft CMS item from a title, slug and body that I give you.webflow__writeYes
Update an itemUpdate the excerpt or body of an existing CMS item.webflow__writeYes
Write to the live siteCreate or update an item directly on the live site.webflow__writeYes. Use with care, nothing waits for a publish
Delete an itemDelete a CMS item that is no longer needed.webflow__deleteYes
Audit page SEOList the static pages whose title or meta description is empty.webflow__readNo. Needs the Pages scope
Rewrite page SEORewrite a static page's title, meta description and Open Graph fields.webflow__writeNo. Needs Pages Read and write

4 ways to connect Microsoft Copilot to Webflow

Four ways can bring a Webflow site to a Copilot agent. This guide uses the first, the Ryze AI connector, as the main way: one hosted address that a Copilot Studio agent takes as a tool, with Webflow joined by a site token you paste into Ryze AI once. The others were checked on the dates in the Sources line. None of the four was run from a Microsoft product.

WayRuns whereSetup in CopilotWhat it reaches in WebflowPrice
Ryze AI connector (the main way)Hosted. One address for every userA Model Context Protocol tool on a Copilot Studio agent with OAuth 2.0 and Dynamic discovery, or an action in a declarative agentSites, collections and CMS items to read, create, update and delete, plus page SEO fields with the Pages scope. 3 toolsSEO Starter is $129 per month with a 3-day free trial
Webflow MCP (Webflow's own)Hosted by Webflow at https://mcp.webflow.com/mcp, with OAuth to a Webflow accountThe same Server URL field on an agent. Webflow's pages name Claude, ChatGPT, Codex and Grok Build, and no Microsoft product, so whether Copilot Studio finishes the sign-in is untestedPages, elements, styles, components, the CMS, SEO metadata, assets, forms, custom code and more, inside the signed-in user's Webflow roles. Webflow's tool reference lists 37 tool names, while Anthropic's directory listing says 34No price stated for the server. Webflow's pricing page lists it among the features of its free Starter site plan
Composio, Webflow toolkitHostedA custom MCP server at https://connect.composio.dev/mcp. Composio's pages show setup for Claude, ChatGPT and Cursor, and none for Microsoft Copilot60 Webflow tools listed, including bulk item creation, live items, orders, webhooks and assets. Composio says Webflow connections go through your own OAuth appFree plan: 10,000 tool calls a month. Standard: $18 per seat per month
Zapier MCP, Webflow actionsHosted by ZapierZapier lists Microsoft Copilot Studio among the clients that can connect. Zapier creates a server and turns on actions for apps already connected to your Zapier accountThe Webflow page shows 8 actions before Load More, such as Create Item, Update Item, Find Item and an API Request in beta. No total is printedAvailable to all Zapier accounts. One MCP tool call uses 2 tasks from your plan quota, and failed calls do not count

With a hosted way your Webflow content passes through that vendor, and Microsoft says a Power Platform data policy applies to any MCP server added to Copilot Studio. Webflow MCP signs in as a person, so it reaches far more of the site than a site token with CMS access does, within that person's roles. Webflow also says only site owners and admins can authorize its MCP server.

Options that do not fit this job

  • The webflow-mcp-server npm package. An open-source Node server that runs on your own computer with a Webflow API token. Microsoft's pages show no field for a command that starts a server locally, so it does not fit a Copilot agent. The README still names the deprecated /sse address for its remote option.
  • Kvalifik mcp-router. A source-available desktop app for macOS and Windows that joins several Webflow workspaces into one connection. It names Codex, Claude Desktop, Claude Code, Cursor, VS Code and Gemini CLI, runs on your machine and is not endorsed by Webflow, so it does not reach a Copilot agent.
  • kapilduraphe/webflow-mcp-server. A local Node server with 2 read-only tools, get_sites and get_site, and no CMS access. It names Claude Desktop only.
  • Webflow Beta MCP at https://mcp.webflow.com/beta/mcp. Experimental tools that Webflow lists for manual setup. It has the same untested Copilot Studio sign-in as the main Webflow server, plus unfinished tools.

Which one to pick

Ryze AI is the best way to connect Microsoft Copilot to Webflow for CMS content work that an agent maker sets up, with one caveat: it has 3 tools on one site token, so design work, components, assets and custom code need another route. Webflow MCP is the better fit when an agent must build or restyle pages, and the first thing to test if your Copilot Studio tenant accepts its sign-in, because Webflow documents that server for other assistants and not for Copilot. Zapier MCP makes sense when your team already runs Webflow automations in Zapier. Composio suits teams that have registered their own Webflow OAuth app.

Sources: Webflow MCP overview, Webflow MCP, getting started, Webflow MCP FAQs, Webflow Beta MCP, Webflow pricing, Composio Webflow toolkit, Composio pricing, Zapier MCP for Webflow, Zapier MCP quickstart, webflow/mcp-server, Kvalifik/mcp-router, kapilduraphe/webflow-mcp-server, Ryze AI Webflow guide. Checked November 15, 2026 and November 14, 2026.

Webflow, Copilot and MCP: dates that matter

DateWhat happened
April 8, 2025Webflow introduced its official MCP server in its developer changelog.
May 29, 2025Microsoft announced general availability of MCP in Copilot Studio, with a streamable transport. SSE stayed in public preview at that point.
August 2025Copilot Studio stopped supporting SSE for MCP. Streamable is the only supported transport.
November 24, 2025Webflow moved its MCP server from SSE to HTTP, replacing https://mcp.webflow.com/sse with https://mcp.webflow.com/mcp.
December 15, 2025Microsoft announced general availability of MCP support in declarative agents for Microsoft 365 Copilot.
January 17, 2026Webflow's changelog called the /sse endpoint fully deprecated and said its data tools were consolidated from 46 or more to 19.
July 2026Copilot Studio news listed adding an MCP server as a tool for agents on the Microsoft Copilot harness, as a preview.
September 2, 2026Microsoft's blog said workflows and MCP servers can be added as tools on the harness now called the Microsoft Copilot harness. Microsoft's how-to page for that flow still carried a preview label on November 14, 2026.
September 21, 2026Webflow released MCP v2.1 with Interactions, Webflow Cloud and Campaigns tools, and CMS field groups.
October 27, 2026Microsoft 365 Copilot release notes said admins can create custom MCP connectors in the Microsoft 365 admin center.

Sources: Microsoft Copilot blog, May 29, 2025, Microsoft, connect an existing MCP server, Microsoft 365 Developer Blog, December 15, 2025, Copilot Studio what's new, Microsoft Copilot blog, September 2, 2026, Microsoft 365 Copilot release notes, Webflow changelog, April 8, 2025, November 24, 2025, January 17, 2026, September 21, 2026. Checked November 14, 2026 and November 15, 2026.

How this guide was tested

This guide is built from Microsoft's and Webflow's own pages and from the Ryze AI facts for the Webflow integration. No call was made to Webflow through the connector, so there are no tested reads or sample results here.

What was doneWhat it gave
Microsoft's documentationCopilot Studio, Microsoft 365 Copilot, Agents Toolkit and admin pages were read on November 14, 2026. The steps above follow them.
Webflow's documentationThe Webflow MCP pages, the Data API rate limit, scope and site token pages, and the pricing page were read on November 15, 2026.
The connector address and sign-in detailsThe connector's two OAuth discovery files were requested once each on November 14, 2026 and answered. No client was registered and no sign-in was started.
The Webflow toolsThe names webflow__read, webflow__write and webflow__delete come from the Ryze AI facts, which took them from the app source. No workspace had Webflow connected, so the tool list was not seen live.
Search demandA Search Console read for Webflow connection queries on November 15, 2026 returned no matching rows, so the FAQ uses the wording of the target searches.

Not run for this guide: every step inside Copilot Studio, Microsoft 365 Copilot, the Microsoft 365 admin center and Agents Toolkit. No agent was created, no server was added, no sign-in was done and no tool was called from a Microsoft product. No Webflow test site was connected, so no read, write, publish or delete was run and no error message was captured. For that reason this guide has no table of tested reads and no table of exact error messages.

Copilot and Webflow errors and fixes

No error message was captured for this guide, so the entries below are problems the documentation and the Ryze AI facts lead to, not messages seen in a test.

Ryze AI does not appear when I look for the tool
Ryze AI was not found on Microsoft's public MCP server lists, and the in-product lists were not opened. Use New tool, Model Context Protocol and type the address yourself instead of searching the MCP tab.
I cannot find New tool or the Model Context Protocol option
New agents open in the new experience, where the path is Build > Tools > Add > Model Context Protocol (MCP). The steps in this guide are for the classic experience. Switch with the three dots at the bottom of the home page side bar.
The Webflow tools do not appear after I add the server
Connect Webflow in Ryze AI first, then add the server again or start a new test chat. Microsoft says tool changes on a server show up dynamically, and says that after a republished custom connector new or renamed tools can take about 12 to 24 hours.
Dynamic discovery fails at sign-in
Microsoft documents Dynamic discovery for servers that support dynamic client registration, and the Ryze AI server does, but the sign-in was not run from Copilot. Try the Dynamic or Manual OAuth type, or ask Ryze AI support.
Webflow reports HTTP 429
The site plan's Data API limit was reached, 60 or 120 requests per minute for the plans Webflow lists. Webflow sends a Retry-After header, typically 60 seconds. Ask for smaller batches and retry after the wait.
The agent cannot read pages or change a page title
The token lacks the Pages scope. Generate a new token with Pages set to Read and write, then reconnect Webflow in Ryze AI.
Publishing fails
Publishing needs a token with CMS write access, and Webflow allows one successful site publish per minute. Webflow lists sites:write for a full site publish while the Ryze AI token has Sites Read-only, so check that on a test site.
Creating an item fails on a required field
Required image, file or multi-reference fields cannot be filled automatically. Make the field optional or give it a default value in the collection settings.
Webflow is already connected elsewhere
A Ryze AI workspace holds one Webflow connection, and a connection link is refused while one exists. Open the Webflow card, click View, disconnect with the trash icon and connect again.
The tools reply that a subscription is required
The Webflow tools need an active Ryze AI plan or free trial. Start the trial, then retry.
Nobody else can use the agent
A Copilot Studio trial can create and test agents but not publish them. Publishing needs a standalone license, and an admin may need to allow the connection under a Power Platform data policy.

Terms on this page

MCP
The Model Context Protocol, an open standard for connecting AI applications to outside systems. Copilot Studio, Claude and ChatGPT support it.
MCP server
A program that offers tools over MCP. The Ryze AI connector is an MCP server that runs on Ryze AI's side, so there is nothing to install.
Declarative agent
An agent for Microsoft 365 Copilot that you build with Agents Toolkit and give actions. An MCP server can be one of its actions.
Harness
The engine a Copilot Studio agent runs on. The standard harness is shown as the classic experience, and the Microsoft Copilot harness is the new experience.
Webflow CMS collection
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 item
Updating an item as a draft leaves a never-published item in Draft status. On an item that is already published it sets Changes in draft, and the live item stays published until the changes are published.
Site token
A key created in a Webflow site's settings that lets an integration use the Webflow Data API on that one site, with the scopes chosen when it was made.

Sources: modelcontextprotocol.io, Webflow, site tokens, Webflow, update items. Checked November 15, 2026.

Frequently asked questions

How do I connect Copilot to Webflow?

Generate a Webflow site token with CMS Read and write and Sites Read-only, connect Webflow in Ryze AI with it, then add https://connector.get-ryze.ai/mcp as a Model Context Protocol tool on a Copilot Studio agent with OAuth 2.0 and Dynamic discovery. Sign in to Ryze AI and add the tool to the agent.

Is there a Webflow connector for Copilot?

Microsoft's and Webflow's pages list no ready-made Webflow connector for Microsoft Copilot, so the route is an MCP tool you add to an agent. The Ryze AI connector at https://connector.get-ryze.ai/mcp has 3 Webflow tools. Webflow's own server, Zapier and Composio are other options, untested in Copilot.

Is there a Webflow MCP server for Copilot?

Yes, two kinds. Webflow runs its own at https://mcp.webflow.com/mcp with OAuth, but Webflow's pages name no Microsoft product for it. The Ryze AI connector gives a Copilot Studio agent 3 Webflow tools. You add either with the Server URL field of an MCP tool.

What is the Webflow MCP server URL?

Webflow's own server is at https://mcp.webflow.com/mcp. The older /sse address was replaced on November 24, 2025. The Ryze AI connector uses https://connector.get-ryze.ai/mcp, the same for every user, and you connect Webflow inside Ryze AI with a site token.

Which should I use, Ryze AI or Webflow MCP?

Use the Ryze AI connector for CMS content jobs that an agent maker sets up, and Webflow MCP when the agent must work on pages, styles and components. Webflow MCP signs in as a person, so it reaches more, and its sign-in with Copilot Studio is untested. Both can sit on one agent.

Can Microsoft Copilot edit my Webflow pages?

Only page SEO fields through the Ryze AI tools: with the optional Pages Read and write scope the write tool can change a static page's title, meta description and Open Graph fields. Page layout, elements and styles belong to Webflow's own MCP server, which names no Microsoft product.

Can Copilot create or update Webflow CMS items?

Yes, through webflow__write, which creates and updates CMS items as live or draft. Copilot Studio turns on all tools by default, so switch the write tool off if you want read-only access. A token with CMS Read and write is needed for this.

Can Copilot delete Webflow items?

Only through the separate webflow__delete tool, which deletes a resource by path, such as a CMS item. In Copilot Studio you can switch that tool off in the server's tool list, and a declarative agent asks before tools that change data.

Can I type the MCP URL into the Copilot chat window?

No Microsoft page shows such a field. An MCP address goes on an agent in Copilot Studio, in a declarative agent built with Agents Toolkit, or in a custom connector made by an admin. Personal Copilot at copilot.com lists four fixed connector services.

Which Copilot plan do I need?

Microsoft's MCP pages name no plan. Copilot Studio is open to all Microsoft 365 users, a trial cannot publish agents, and the Copilot Studio for Teams plan lists Power Platform connectors and generative orchestration as not available. Declarative agents need an admin to allow custom app upload.

Do I need a Webflow plan or a site token?

You need a site token from Site settings, under Apps & Integrations and API access, and only a site administrator can create one. Webflow's pricing page lists its MCP server among the features of the free Starter site plan. The Data API limit follows the site plan.

Can I connect more than one Webflow site?

Not in one Ryze AI workspace. A site token sees only its own site, and a workspace holds one Webflow connection. To switch sites, click View on the Webflow card, disconnect with the trash icon and connect with the other site's token.

Why do the Webflow tools not show up in Copilot Studio?

Connect Webflow in Ryze AI before you add the server, then start a new test chat. If the tools still do not show, check that the connection was created and the tool was added to the agent. Microsoft says tool changes can take about 12 to 24 hours after a republished custom connector.

How much does it cost to connect Copilot 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, Agency is $279 per month and Shopify CRO is $1,499 per month. Annual billing takes 30% off the first year. Microsoft bills Copilot Studio use separately.

How do I disconnect Webflow from Copilot?

Delete the Ryze AI tool from the agent's Tools page in Copilot Studio, or disconnect Webflow from its card in Ryze AI with the trash icon. To end the token, revoke it in Site settings > Apps & integrations > API access in Webflow.

Connect Webflow to Microsoft Copilot

Your Webflow site connects once in Ryze AI with a site token, then a Copilot agent can read, create, update and delete CMS items on it. 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.