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.
- Connects over OAuth
- Free 14-day trial
- No credit card
List the blog posts published this month on our marketing site
Working in Webflow with Elaichi
-
Get asset preview
-
Get more tools
-
Data agent instructions tool
How to connect Webflow to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
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. 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.
Webflow MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Webflow through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Webflow is logged.
-
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?”
What connecting Webflow gets you
6 screens from Elaichi, each doing one job for your Webflow account.
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, Cursor or Microsoft Copilot
The agent
Ask about your Webflow site in plain language.
Pages, CMS items and form submissions answered from live records, no dashboard to open.
Copy the endpoint
AI apps
One endpoint brings Webflow to every MCP client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth through one org endpoint, no SDK, no shared key.
Tool catalog
34 Webflow tools, no code to write.
Sites, pages, CMS collections, assets, forms, components and styles covered out of the box.
Toolboxes
Every team gets its own Webflow toolbox.
Content edits CMS items, Design shapes components, Marketing reads form submissions, each in its own scope.
Shared connections
Share one Webflow connection, never a password.
One person connects Webflow, teams work through it, and nobody else ever sees a credential.
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.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
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 Jake Morgan
Approve Deny -
Post the digest
Webflow
Queued
Workflows
A schedule starts the work, a person approves.
New Webflow form submissions are fetched, grouped, drafted into a digest, approved, then posted back.
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%
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.
Why connect Webflow's MCP server through Elaichi
Webflow builds and runs this MCP server. Elaichi sits in front of it, so Webflow's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Webflow's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Webflow's tools at the same Elaichi address as every other connected app. Nobody adds Webflow's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Webflow sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Webflow's server. By default, a tool Webflow does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Webflow
Webflow builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Webflow team.
For IT and engineering
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 | Free for one person; $15 per user per month on Gold. | 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.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting publishing, deleting items or changing styles. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot