Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Everyday tasks

Webflow's MCP server inside Microsoft Copilot

Written November 13, 2026

Webflow put its MCP server inside Microsoft Copilot. What a site owner can now ask an assistant to do with their Webflow site.

What changed

On November 12, 2026, Webflow announced an MCP connector for Microsoft Copilot. Webflow is available as a plugin in the Microsoft plugin registry, so a person working in Copilot can manage a Webflow site without leaving the tool they already use. Webflow says the connector brings the same core capabilities already offered through Claude, ChatGPT, Codex and Slack into Copilot, and that it also supports Copilot Skills: reusable instructions that guide an agent through common workflows and Webflow best practices.

For a site owner, the practical change is where the conversation happens. Work that used to start in Webflow, or in a different assistant, can now start inside the Copilot environment an organization has already approved. Ben Haefele, Webflow's Chief Product Officer, puts it as a direct way to act on what a team learns about its content: get insights on performance, make updates, or launch a new page without leaving that environment.

What an assistant can do with the site

Webflow's announcement groups the connector's work into six areas:

Webflow's MCP server overview describes the same server behind the other assistants: an assistant can create and edit pages, manage styles and components, work with CMS Collections and items, publish a site or individual pages, deploy Webflow Cloud apps and read their logs, and summarize Analyze traffic across date ranges. Performance questions about Optimize tests and answer-engine visibility sit behind the Analyze and Optimize add-ons.

Who can connect, and what governs the work

The MCP server is available on all Webflow Site plans, including the free Starter plan. Users with any site role except Reviewer can connect, and the server respects each user's existing role permissions. When you connect, you choose which sites or Workspaces the assistant can reach; Webflow's own guidance is to authorize only the sites you are actively working on. The Copilot connector itself is free to install and does not consume Webflow AI credits, though access to individual capabilities depends on your Webflow plan and permissions. Work done through the connector follows the same Webflow roles and permissions that already govern the team, and agent activity is recorded in Webflow's activity logs with AI attribution.

Limits

Related playbooks

Sources

Back to: Everyday tasks playbooks hub · Also: Iterable's hosted MCP server reaches your AI tools · Microsoft 365 Copilot connectors can now write