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.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Webflow to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Webflow once
-
Open Connections, choose Add connection, and pick Webflow.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Webflow. Webflow's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Webflow MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Webflow to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Webflow through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Content
Turn a brief into a published blog post
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.
-
Marketing
Summarize this week's form submissions
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.
-
Design
See where a component or style is used
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.
-
Web
Get a site ready for launch day
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.
-
Localization
Find CMS items missing a translation
List the pages and CMS items that have not been localized for a given locale and get the gaps filled before a regional launch.
-
SEO
Audit page titles and meta descriptions
Find pages with missing or duplicate titles and descriptions across the whole site and update them without opening each page in the Designer.
Try asking
- “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?”
Compare
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Webflow tools for your AI agents
34 tools are ready to call through Elaichi's MCP endpoint the moment you connect Webflow, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Webflow builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Webflow gets you
6 screens from the product, each doing one job for your Webflow account.
The agent
Ask about your Webflow site in plain language.
Pages, CMS items and form submissions answered from live records, no dashboard to open.
- sites
- pages
- assets
- forms
Ask Elaichi to work across your apps.
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?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Webflow to every MCP client.
Claude, ChatGPT and Cursor connect over OAuth through one org endpoint, no SDK, no shared key.
Copy the endpoint
Tool catalog
34 Webflow tools, no code to write.
Sites, pages, CMS collections, assets, forms, components and styles covered out of the box.
- Data agent instructions tool
- Data analyze tool
- Data apps tool
- Data assets tool
Toolboxes
Every team gets its own Webflow toolbox.
Content edits CMS items, Design shapes components, Marketing reads form submissions, each in its own scope.
- Marketing
- Content
- Design
- Web
Shared connections
Share one Webflow connection, never a password.
One person connects Webflow, teams work through it, and nobody else ever sees a credential.
- Marketing site
- Blog
- Design system
- Localization
Audit log
Every Webflow change is written down, by name.
Who published a page, edited a CMS item or changed a style, and exactly when.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts the work, a person approves.
New Webflow form submissions are fetched, grouped, drafted into a digest, approved, then posted back.
Webflow digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch sites
Webflow
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Webflow
Queued
Collections and dashboards
Webflow health, computed on a schedule, no asking.
Four metrics, 14 days of CMS items created and a team breakdown, with no model involved.
Webflow health
Refreshed 4 minutes ago · every 15 minutes · from the sites collection
Sites
1,284 ↓ 12%
Pages
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Sites created
Last 14 days
By team
Share of activity
Marketing site 34%
Blog 27%
Design system 21%
Localization 18%
Related connectors
More from the catalog
FAQ
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 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.
Put Webflow in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.