Webflow MCP server for Claude, Codex and Cursor

What your AI apps can do with Webflow

Read and update CMS collections
Manage pages and publishing

Webflow MCP tools

30 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Tool	What it does
`webflow_guide_tool`	Recommended workflows and best practices, meant to be called first
`ask_webflow_ai`	Ask Webflow AI about the Webflow API
`get_asset_preview`	Image preview of a site asset
`get_more_tools`	Request a specialized tool for a capability not already loaded
`data_sites_tool`	List sites, get site details and publish_site
`data_pages_tool`	List and create pages, update page settings and SEO, schema markup, page branches (branches need Enterprise)
`data_cms_tool`	Collections, fields and items: list, create, update, publish, unpublish and delete
`data_element_tool`	Inspect and edit page elements: text, links, styles, attributes, move or remove
`data_element_builder`	Build elements from a schema or insert HTML/CSS
`data_whtml_builder`	Build elements from a schema or insert HTML/CSS
`data_style_tool`	Classes, combo classes and style variable modes
`data_component_tool`	Component definitions and instances
`data_variable_tool`	Design-token variables, collections and modes
`data_assets_tool`	Assets, folders, uploads and compression, including delete_asset
`data_forms_tool`	Read forms and submissions; update or delete submissions
`data_scripts_tool`	Site and page custom code in head and footer
`data_webhook_tool`	Create, list and delete site webhooks
`data_sitemap_tool`	Sitemap inclusion for pages and CMS items
`data_localization_tool`	Read and update content in secondary locales
`data_comments_tool`	Designer comment threads and replies
`data_agent_instructions_tool`	Site-level rules and skills that guide agents
`data_apps_tool`	Webflow Cloud apps, environments, deployments, logs
`data_members_tool`	Workspace and site membership and roles (Enterprise)
`data_enterprise_tool`	301 redirects, robots.txt, well-known files, activity logs (Enterprise)
`data_analyze_tool`	Read-only analytics for the Analyze, Optimize and AEO add-ons
`data_optimize_tool`	Read-only analytics for the Analyze, Optimize and AEO add-ons
`data_aeo_tool`	Read-only analytics for the Analyze, Optimize and AEO add-ons
`designer_tool`	Live Designer canvas: current page, selection, breakpoints, snapshots, image upload by URL (needs the Bridge App)
`element_snapshot_tool`	Live Designer canvas: current page, selection, breakpoints, snapshots, image upload by URL (needs the Bridge App)
`asset_tool`	Live Designer canvas: current page, selection, breakpoints, snapshots, image upload by URL (needs the Bridge App)

Suggested access for each AI app

The documentation this list comes from doesn't mark Webflow's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Webflow connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

Connect once. Add Webflow to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
Choose access per app. Give Claude Code every Webflow tool, give Cursor only the read tools, or keep Webflow away from an app entirely.
Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Webflow MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell

claude mcp add --transport http toolstile 'https://toolstile.com/mcp'

Then connect Webflow in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Webflow endpoint to each app separately. In Claude Code:

Shell

claude mcp add --transport http webflow 'https://mcp.webflow.com/mcp'

In Cursor's mcp.json:

JSON

{
  "mcpServers": {
    "webflow": {
      "url": "https://mcp.webflow.com/mcp"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Webflow MCP documentation for what your client needs.

Before you connect

A Webflow account. Sign-in uses your Webflow permissions.

Server details

Detail	Value
Publisher	Webflow
Endpoint	`https://mcp.webflow.com/mcp`
Authentication	Browser sign-in
Categories	Development, Marketing & research
Tool list	30 tools, observed 29 October 2026 (docs)

Webflow MCP documentation