# Webflow MCP connector

The Webflow connector brings sites, pages, CMS items, assets and form submissions to Claude, ChatGPT and Cursor through one governed endpoint, so each person works inside their own Webflow access with every action logged.

Source: https://elaichi.ai/connectors/webflow/

## Facts

| | |
| --- | --- |
| Application | Webflow |
| Category | Design |
| AI tools | 34 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Webflow builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | support.webflow.com |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Webflow is connected

- List the blog posts published this month on our marketing site
- Show form submissions from the contact page this week
- Which pages are missing a meta description?

## Connect Webflow in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Webflow.
2. Optionally set Share with, then press Connect.
3. Approve it in Webflow. Webflow's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Webflow tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Webflow MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Webflow MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## Webflow MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Webflow to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Webflow tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Webflow through Elaichi

### Turn a brief into a published blog post

Content. Ask for a draft, have it added as a CMS item in the right collection with the right fields, and publish it once someone has read it over.

### Summarize this week's form submissions

Marketing. Pull every contact and demo request that came through your Webflow forms and get them grouped by campaign, with the ones that need a reply called out.

### See where a component or style is used

Design. Before changing a button or a color, find out which pages use that component or class so nothing breaks on a page you forgot about.

### Get a site ready for launch day

Web. Check which pages are still drafts, which assets are missing, and whether the sitemap and scripts are in place, then fix what is wrong in one pass.

### Find CMS items missing a translation

Localization. List the pages and CMS items that have not been localized for a given locale and get the gaps filled before a regional launch.

### Audit page titles and meta descriptions

SEO. Find pages with missing or duplicate titles and descriptions across the whole site and update them without opening each page in the Designer.

## Elaichi vs Zapier MCP vs Composio for Webflow

All three can connect Webflow to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Webflow tools | Allow or restrict single Webflow tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Webflow call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Webflow to Claude?

Open Elaichi, choose Webflow, and sign in with your Webflow account, which asks you to approve access and pick the sites you want to work with. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi once and Webflow is available from then on.

### Does Webflow work with ChatGPT and Cursor as well as Claude?

Yes. Once Webflow is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Webflow once and every client you use picks it up.

### What can an AI agent actually do with my Webflow data?

It can read and update your Webflow sites, pages, CMS collections and items, assets, forms and form submissions, components, styles, scripts, sitemaps and localization settings. In practice that means asking for a list of unpublished pages, having a blog post added to a collection, or getting this week's contact form submissions summarized. Short, concrete asks such as "list draft pages on the marketing site" work better than long paragraphs.

### Does connecting Webflow give the AI access to every site in my workspace?

No. Access follows the person who signed in, so the AI sees only the Webflow sites and content that person approved during sign-in and already has permission to touch. Elaichi can narrow that further, for example to a single site or to read-only work, but it can never grant more than the person already has in Webflow.

### Can my team share one Webflow connection?

Yes. One person connects Webflow in Elaichi and shares it with a team, and nobody else ever handles a Webflow credential. Each teammate still signs in to Elaichi as themselves, so every page edit or CMS change in the audit log is tied to the person who made it, not to whoever set up the connection.

### Can I stop an agent from deleting or changing things in Webflow?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Webflow pages and CMS items while blocking publishing, deleting items or changing styles. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however it is worded, can reach it.

### What happens to a Webflow connection when someone leaves?

Offboarding that person in Elaichi ends their access to Webflow through every client at once. If they connected a shared Webflow account, the connection keeps working for everyone it was shared with. Disconnecting Webflow once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

### Does the Webflow MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Webflow is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Webflow?

Yes. Both let Claude, ChatGPT or Cursor use Webflow. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Webflow call.

### How is Elaichi different from Composio for Webflow?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Webflow: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 34 Webflow tools

Every tool below is callable through https://api.elaichi.ai/mcp once Webflow is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Data agent instructions tool** (Action). Manage a site's agent instructions: the markdown-based rules and skills that give agents custom guidance for working on that site. Instructions can reference Webflow primitives (variables, styles, components, pages, CMS collections and items, locales, and other instructions),…
- **Data analyze tool** (Action). Read-only access to Webflow Analyze report data for a site: traffic over time, ranked pages, ranked dimensions, engagement events, and time on page. It also exposes two guide actions that return static guidance for building queries and interpreting results; these make no API…
- **Data apps tool** (Action). Inspect and manage Webflow Cloud apps: their GitHub sources, environments, environment variable metadata, deployments, custom domains, and logs. Apps created through this tool are built from a GitHub repository. Use the Webflow CLI for local-source apps, local-source…
- **Data assets tool** (Action). Manage a site's assets and asset folders. Uploads are a two-step process: create the asset metadata to get a presigned upload target, then POST the file bytes to it. The tool also lists, updates, organizes, and deletes assets and folders, and compresses images to WebP or AVIF…
- **Data campaigns tool** (Action). Manage Campaign Hub sites, campaigns, page variations, and campaign analytics. A campaign is generated from a markdown brief and produces a landing page. Personalization binds campaign fields to element settings and component props, so a single page can present different…
- **Data cms tool** (Action). Manage a site's CMS: collections, their fields (static, option, and reference), collection field groups, and the items within them. Items are created and updated as drafts; publishing them live is a separate action.
- **Data comments tool** (Action). Read Designer comment threads and their replies (filterable by page, resolution status, and date), look up comment participants by email, and post replies to existing threads.
- **Data component builder** (Action). Insert component instances onto a page as a child of an element or into a slot of an existing component instance, including recursive trees of nested components in a single call.
- **Data component props tool** (Action). Manage a component's prop definitions and the prop values on its instances. Create, update, and remove prop definitions, and set or reset the values on an instance.
- **Data component tool** (Action). Manage component definitions and instances: get and query components, create blank components, transform elements into components, and insert and unlink instances. Prop definitions and values live in `data_component_props_tool`, and variants in `data_component_variants_tool`.…
- **Data component variants tool** (Action). Manage a component's variants and the styles scoped to each one. Create, duplicate, delete, reorder, and rename variants, and read or set per-variant style overrides.
- **Data element builder** (Action). Create elements on a page from an element schema, including nested child elements in a single call.
- **Data element settings tool** (Action). Read and write element-level settings and data bindings. Get and set settings, discover the data sources an element can bind to, and set an element's tag, visibility, and DOM id as static values or bindings.
- **Data element tool** (Action). Inspect and modify the elements on a page: query the element tree, move and remove elements, and edit text, styles, links, images, heading levels, attributes, and display names. Element settings and data bindings live in `data_element_settings_tool`; selecting an element…
- **Data enterprise tool** (Action). Manage enterprise site settings: 301 redirects, `robots.txt`, well-known files, and site activity logs.
- **Data fonts tool** (Action). Manage a site's uploaded custom fonts: list and inspect them, register new fonts and replace their files (a two-step upload), update metadata, and remove fonts individually or in batches.
- **Data forms tool** (Action). Read a site's forms and manage their submissions: list forms and their schemas, list and retrieve submissions site-wide or per form, update user-hidden submission fields, and delete submissions.
- **Data interactions tool** (Action). Create and manage IX3 interactions, the animations and interactive behavior attached to a page. An interaction carries its triggers and its inline timelines in a single call. The tool runs headlessly and needs no Designer session or bridge app.
- **Data localization tool** (Action). Localize page and component content into secondary locales. Reads from the primary or a secondary locale, but writes only to secondary locales. Also lists a site's components.
- **Data pages tool** (Action). List, create, and update a site's pages, manage page branches and their staging previews, and read or write page-level SEO metadata and JSON-LD schema markup.
- **Data scripts tool** (Action). Register, apply, update, and remove custom code scripts at the site or page level, and read or write the freeform head and footer custom-code blocks. Registering a script and applying it are separate steps.
- **Data sitemap tool** (Action). Read and set the sitemap indexing status (`includeInSitemap`) of static pages and CMS collection items, individually or in bulk. Folder, collection-template, and utility pages aren't supported by the page actions.
- **Data sites tool** (Action). List the sites accessible to the authenticated user, get a site's details, and publish a site to its domains.
- **Data style tool** (Action). Create, query, update, rename, and remove styles (classes and combo classes), and manage the variable modes applied to a style.
- **Data variable tool** (Action). Create, update, rename, and delete variables (color, font family, number, percentage, size), create collections and modes, and query and reorder collections.
- **Data webhook tool** (Action). List, create, retrieve, and delete a site's webhooks.
- **Data whtml builder** (Action). Insert elements onto a page from HTML and CSS strings.
- **Asset tool** (Action). Upload an image to a site's asset library from a public URL. In 2.0 this is the only asset action that still runs through the Designer session. All other asset and folder management (listing, updating, organizing, deleting, compressing) moved to `data_assets_tool`.
- **Designer tool** (Action). Interact with the live Designer session: read the current page, mode, branch, selected element, and breakpoints; select elements; navigate the canvas between pages and component views; and create page folders.
- **Element snapshot tool** (Action). Capture a visual snapshot of a Designer element for debugging and visual feedback. This lets an agent see the current state of a site and verify its own changes without publishing.
- **Ask Webflow AI** (Action). Ask Webflow AI a free-form question about the Webflow API and get an answer back.
- **Get asset preview** (Get). Get an image preview of a site asset by its asset ID. Downloads the smallest available variant or the original. Image content only, up to 2 MB.
- **Get more tools** (Get). Request a specialized tool for a capability the currently loaded tools don't cover. Use it to reach functionality that isn't already in the tool set.
- **Webflow guide tool** (Action). Return recommended workflows and best practices for using the Webflow tools. Intended to be called before performing actions.