How is this different from connecting Webflow MCP directly?

Connected directly, an agent sees every tool the server exposes and holds the credential itself. Through TrustGate you choose which tools each agent gets, and every call is logged against the agent that made it.

What if the Webflow MCP API changes?

We track the Webflow MCP schema, so the tool catalogue stays current. Tools you have already allowed keep working, and anything new stays denied until you enable it.

Can I give different agents different Webflow tools?

Yes. Access is set per agent: one can get a handful of read tools, another the full set. You grant the whole MCP or single tools within it.

Where can I see what my agents did in Webflow?

Every call is logged against the agent that made it, with the tool it used. Activity can be sent on to your own monitoring.

Do I need to run the Webflow MCP server myself?

No. TrustGate connects to the Webflow MCP server and sits in front of it. Your agent only talks to your TrustGate URL, never to Webflow directly.

Connect Webflow MCP to your AI agents, securely.

Q: Is Webflow MCP secure?

The server itself exposes 37 tools, and some of them can write to your Webflow account. Behind TrustGate an agent only sees the tools you allow, requests and responses are inspected, and every call is logged. Anything outside the allowlist is denied before it reaches Webflow.

One secured endpoint for every Webflow call your AI agents make, scoped per user, inspected, and logged.

Get started for free

Get a demo

Try Webflow MCP now

What your agents can ask once Webflow MCP is connected.

“List my Webflow sites and their published status”
“What collections and fields does this site's CMS have?”
“Create a hero section on this landing page”

“Which form submissions came in this week?”
“Show the components used across this site”
“Update the SEO settings on this page”

Select the tools your AI agents can call

37 tools from the Webflow MCP schema.

Showing 37 tools

data_sites_toolhigh riskLists sites, gets site details and publishes sites. Publishing pushes changes to the live domain.
data_pages_toolwriteLists pages, gets page metadata, creates pages, updates page settings, and reads or updates static content.
data_sitemap_toolreadInspects and manages the site's sitemap and indexing configuration.
data_localization_toolwriteManages the site's locales and localized content.
data_scripts_toolwriteRegisters and applies custom scripts on a site or page.
data_cms_toolhigh riskManages a site's CMS: collections, their static, option and reference fields, field groups, and the items within them. Items are created and updated as drafts; publishing them live is a separate action.
data_element_toolhigh riskQueries, adds, repositions and deletes elements on a page. Requires siteId and pageId.
data_element_settings_toolwriteReads and updates the settings of an element on a page.
data_element_builderwriteCreates one element, with optional nested children, from an element schema at a given position.
data_whtml_builderwriteBuilds page structure from Webflow-flavoured HTML in a single call.
data_component_toolwriteLists and queries components, gets component metadata and content, and updates component content.
data_component_props_toolwriteReads and updates the properties defined on a component.
data_component_variants_toolwriteManages component variants and their per-variant style overrides.
data_component_builderwriteCreates components from a schema, including their nested structure.
data_style_toolwriteCreates and updates styles on elements. Requires siteId and pageId.
data_variable_toolwriteManages design variables and the collections that hold them.
data_fonts_toolreadLists the fonts available on a site.
data_interactions_toolwriteManages the interactions and animations configured on a page.
data_assets_toolwriteLists, uploads and manages the assets and asset folders in a site's library.
data_forms_toolreadLists the forms on a site and the submissions they have received.
data_comments_toolwriteReads and replies to comment threads, the user feedback attached to an element or page inside the Designer.
data_apps_toolreadInspects and manages Webflow Cloud apps: their GitHub sources, environments, environment variable metadata, deployments, custom domains and logs.
data_webhook_toolhigh riskLists, creates and removes the webhooks that deliver site events to external endpoints.
data_enterprise_toolreadReads enterprise-level workspace and site settings.
data_campaigns_toolreadReads the campaigns configured on a site.
data_analyze_toolreadReads site analytics. Requires the Webflow Analyze add-on.
data_agent_instructions_toolreadSearches a site's agent instructions by name, description or markdown substring, returning metadata and a resource URI per result.
data_aeo_toolreadReads AEO (answer engine optimization) analytics for a site.
data_optimize_toolreadReads Webflow Optimize results for a site.
data_members_toolhigh riskWorks with site and workspace access for members.
designer_toolwriteReads and acts on what is open in the Designer: the current mode, the active page, element selection and switching pages.
asset_toolwriteBrings a remotely hosted image into a site's assets by URL. In 2.0 this is the only asset action that still runs through the Designer session.
element_snapshot_toolreadCaptures a visual snapshot of a Designer element by its composite ID, for debugging and visual feedback.
ask_webflow_aireadAsks Webflow AI a free-form question about the Webflow API and gets an answer back.
get_asset_previewreadGets an image preview of a site asset by its ID. Image content only, up to 2 MB.
get_more_toolsreadRequests a specialized tool for a capability the currently loaded tools do not cover.
webflow_guide_toolreadReturns the recommended workflows and best practices for using the Webflow tools.

What Webflow MCP exposes

Webflow MCP groups its 37 tools into 9 categories, each with a suggested starting policy.

Category	Covers	Access	Suggested policy
Sites & Pages	Site listing and publishing, page metadata and settings, static content, sitemap, localization and custom scripts	Read / Write	Publishing a site pushes changes live; require approval
CMS	Collections, their fields and field groups, and the items inside them. Items are created as drafts; publishing is a separate action	Read / Write	Approve item publishing and deletion; drafts are safe to create
Elements	Reading, creating, repositioning and deleting page elements, their settings, and building from HTML	Read / Write	Every action needs a siteId and pageId; approve deletions
Components	Components, their properties, variants and the component builder	Read / Write	Component changes propagate to every instance across the site
Styling	Styles, variables, fonts and interactions on a page	Read / Write	Use only style properties Webflow Designer supports
Content & Feedback	Assets, form submissions and Designer comment threads	Read / Write	Form submissions can hold personal data; restrict access
Platform	Webflow Cloud apps, webhooks, enterprise settings, campaigns, Analyze data and agent instructions	Read / Write	Webhooks route site data elsewhere; approve changes
Designer Session	Live canvas actions: the current mode and page, element selection, page switching, image upload by URL and element snapshots	Read / Write	Requires the MCP Bridge app and an open Designer; actions act on what the user is looking at
Utility	Webflow AI questions, asset previews, tool discovery and workflow guidelines	Read	Read-only and headless; safe to allow broadly