Connect your AI Agents to Webflow in minutes

What is a Webflow MCP?

It's an MCP server that gives your agents access to Webflow via tools. Your agents can invoke these tools to create and publish CMS collection items, manage e-commerce orders, handle form submissions, update site content, and more.

Webflow offers an official MCP server, but you can also use one from a third-party platform, like Merge Agent Handler.

How can I use the Webflow MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

• Content publishing pipeline: When a new blog post is approved in a content tool like Notion, an agent calls <code class="blog_inline-code">create_collection_item</code> to add it to the appropriate Webflow CMS collection and then calls <code class="blog_inline-code">publish_collection_items</code> to make it live without any manual steps in the Webflow editor

• Form-to-CRM sync: When a visitor submits a contact form on a Webflow site, an agent calls <code class="blog_inline-code">get_form_submission</code> to retrieve the data and creates a corresponding contact record in HubSpot, keeping sales pipeline data current without manual imports

• E-commerce order fulfillment: When a payment is confirmed in Stripe, an agent calls <code class="blog_inline-code">fulfill_order</code> to mark the Webflow order as shipped and calls update_inventory to decrement available stock, keeping storefront data accurate in real time

• Post-deploy site publish: When a CI pipeline finishes a build, an agent calls <code class="blog_inline-code">publish_site</code> to push all pending content changes live alongside the code release, ensuring copy and functionality ship together

What are popular tools for Webflow's MCP server?

Here are some of the most commonly used tools:

• <code class="blog_inline-code">create_collection_item</code> adds a new item to a specified Webflow CMS collection with the provided field values. Use this when an agent needs to push content from an external source into a Webflow site without opening the editor

• <code class="blog_inline-code">publish_collection_items</code> moves one or more staged collection items to the live site. Call this after creating or updating items when an agent needs the changes to be immediately visible to site visitors

• <code class="blog_inline-code">list_collection_items</code> retrieves all items in a CMS collection, including their field values and publish status. Good for agents that need to audit existing content before creating duplicates or generating a content inventory report

• <code class="blog_inline-code">list_form_submissions</code> returns all submissions for a given Webflow form, including field data and timestamps. Helpful when an agent needs to process leads, route inquiries, or sync form data to a downstream system on a schedule

• <code class="blog_inline-code">fulfill_order</code> marks a Webflow e-commerce order as fulfilled and optionally records tracking information. Use this when an agent is automating order processing in response to a fulfillment event in a logistics or payment system

• <code class="blog_inline-code">publish_site</code> pushes all staged changes for a Webflow site to production. Call this when an agent needs to coordinate a content release with an external trigger, like a campaign launch date or a completed approval workflow

What makes Merge Agent Handler's Webflow MCP server better than alternative Webflow MCP servers?

Here is what sets Merge Agent Handler's Webflow MCP server apart from building your own or using a standalone alternative:

• Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Webflow, this means you can prevent form submission data containing PII, e-commerce order details, and unpublished CMS content from being exposed even when the agent has broad read access

• Managed authentication and credentials: Merge stores and refreshes Webflow credentials on your behalf. You never hand OAuth tokens to an agent directly or deal with re-authentication when Webflow credentials expire

• Real-time observability and audit trail: Every tool call made against Webflow is logged with timestamp, tool name, input parameters, and response metadata. You can see exactly what content an agent published, what orders it fulfilled, or what form data it read without adding any custom logging

• Tool Packs and controlled access: Tool Packs let you bundle specific Webflow tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's Webflow MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account and navigate to Tool Packs (collections of connector tools scoped to a specific use case).

2. Create a new Tool Pack, then find and enable the Webflow connector. Choose which tools to include: enable read tools like <code class="blog_inline-code">list_collection_items</code> for content auditing use cases, or add write tools like <code class="blog_inline-code">create_collection_item</code> and <code class="blog_inline-code">publish_site</code> if your agent needs to create or publish content.

3. Add a Registered User inside the Tool Pack. This is the identity context under which your agent operates. Merge generates a unique MCP URL scoped to this user once it's created.

4. From the Registered User detail page, authenticate Webflow by completing the OAuth flow. Merge stores and manages the credentials going forward.

5. Copy the MCP URL from the Tool Pack detail page and generate an API key from Settings. You'll need both to connect your agent.

6. Add the MCP server to your agent or IDE using the MCP URL and API key. Your Webflow tools are now accessible through that endpoint.