Webflow MCP v2 needs no Designer session: pair it with Sume MCP

What shipped

Webflow's changelog lists MCP v2.0: most element, component, style and variable operations no longer need a Designer session, and it adds Analyze, forms, custom fonts, sitemap indexing and agent instructions. v2.0.1 reorganised the tools, and v2.1 added Interactions (GSAP only), Webflow Cloud, Campaigns and branch lifecycle. Changelog entries carry no dates, so treat the order as the only timing.

For video, the interesting part is that one agent can now edit a Webflow page and generate the clip for it, with each server doing its own job.

Webflow MCP facts

Read from the MCP overview.

Two servers, one agent

Sume's hosted MCP endpoint is https://mcp.sume.com/mcp. It signs in with OAuth and is read-only by default (mcp:read); write tools need mcp:write granted at consent. Tools include generate_image, timeline_create and jobs_wait.

Add both servers to the client, ask the agent to generate the hero clip, and let it wait with jobs_wait. That call holds at most 55 seconds (50 by default), so a long render needs repeated waits on the same ids, never a second paid create. See the MCP quickstart.

claude mcp add --transport http webflow https://developers.webflow.com/_mcp/server
claude mcp add --transport http sume https://mcp.sume.com/mcp

Caveats

Keep the order explicit in your prompt: generate and finish the asset first, then update the page with its media.sume.com URL.

• Webflow is one workspace per authorization, so a multi-site agency authorizes once per workspace.
• If a tool still needs the Designer, the agent will stall until the Bridge App is connected.
• Grant Sume write scope only when you want it to create paid jobs.