Webflow MCP Server for Claude
Manage Webflow sites, pages, CMS collections, collection items, assets, and forms from Claude — with the official Webflow MCP server that connects AI agents to the Webflow Data API via OAuth.
Open the source and read safety notes before installing.
Safety notes
- CMS collection item create, update, and delete operations write directly to your Webflow project — confirm before applying changes to live sites.
- Publishing operations make content publicly visible immediately; review changes before asking Claude to publish.
- The remote server requires OAuth authorization — you control which sites Claude can access during the OAuth flow.
Privacy notes
- Site structure, page content, CMS collection schemas, collection items, form submissions, and asset metadata from your Webflow workspace are surfaced in Claude's context.
- OAuth authentication scopes access to specific sites you authorize — no credentials are stored in your MCP config when using the remote server.
Prerequisites
- A Webflow account — authenticate via OAuth on first use when using the remote server.
- For the local server: Node.js 22.3.0+ and a Webflow API token from Account Settings → Integrations → API Access.
- An MCP client such as Claude Code or Claude Desktop.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Scope
- Source repo
- Estimated setup
- 5 minutes
- Difficulty
- beginner
- Website
- https://webflow.com
Full copyable content
{
"mcpServers": {
"webflow": {
"url": "https://mcp.webflow.com/sse",
"type": "http"
}
}
}About this resource
Overview
The Webflow MCP Server is the official Model Context Protocol server from Webflow. It gives
Claude access to the Webflow Data API — sites, pages, CMS collections, collection items, assets,
forms, and more. Authenticate via OAuth (no API tokens required) using the hosted remote server at
https://mcp.webflow.com/sse, or run locally with a Webflow API token. Licensed under MIT.
The remote server includes a Webflow Designer companion app that syncs changes to your live canvas in real time.
Key capabilities
- Sites — list all Webflow sites and retrieve site details.
- Pages — list, inspect, and update static page content.
- CMS collections — create, update, and delete CMS collection schemas.
- Collection items — full CRUD plus publish operations for CMS content items.
- Assets — list, get, and upload assets to your Webflow site.
- Forms — list forms and retrieve submission data.
- Custom domains — list configured custom domains.
- Webhooks — manage Webflow webhook subscriptions.
How it compares
| Server | CMS collections | Page management | Asset management | Designer sync | Auth |
|---|---|---|---|---|---|
| Webflow MCP | Full CRUD | Yes | Yes | Yes | OAuth |
| Contentful MCP | Full CRUD | No | Yes | No | API key |
| Sanity MCP | Full CRUD | No | Limited | No | OAuth |
| Builder.io MCP | Limited | Yes | Limited | No | API key |
Webflow's MCP is the only web-building platform to offer a live Designer sync — changes made by Claude appear in the Webflow canvas in real time.
Installation
Claude Code (remote, OAuth)
claude mcp add --transport http webflow https://mcp.webflow.com/sse
On first use, Claude Code will open a browser window for Webflow OAuth — select which sites to authorize.
Claude Desktop (remote)
{
"mcpServers": {
"webflow": {
"url": "https://mcp.webflow.com/sse",
"type": "http"
}
}
}
Claude Desktop (local, API key)
{
"mcpServers": {
"webflow": {
"command": "npx",
"args": ["webflow-mcp-server"],
"env": {
"WEBFLOW_TOKEN": "your-webflow-api-token"
}
}
}
}
Get your API token from Account Settings → Integrations → API Access in Webflow.
Requirements
- A Webflow account and at least one site.
- For local server: Node.js 22.3.0+ (npm is included).
- An MCP client (Claude Code or Claude Desktop).
Security
- Remote server uses OAuth — access is limited to sites you authorize during sign-in.
- Publishing operations immediately affect live content; review before confirming.
- For local server, store your API token in MCP config rather than shell history.
Source Verification Notes
Verified on 2026-06-18:
- Official GitHub repository
webflow/mcp-server(MIT, 132+ stars) documents thewebflow-mcp-servernpm package, hosted endpoint athttps://mcp.webflow.com/sse, OAuth flow, local API-token config, and Webflow Designer integration. - MCP server listing at
feluda.ai/mcp-servers/webflowindependently confirms the remote OAuth endpoint and CMS/page management capabilities. - Claude Code MCP documentation at
code.claude.com/docs/en/mcpdescribes the--transport httpconnection pattern used above.
Source citations
Add this badge to your README
How it compares
Webflow MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Webflow MCP Server for Claude Manage Webflow sites, pages, CMS collections, collection items, assets, and forms from Claude — with the official Webflow MCP server that connects AI agents to the Webflow Data API via OAuth. Open dossier | Contentful MCP Server for Claude Create, update, publish, and manage content in Contentful from Claude — entries, assets, content types, locales, spaces, environments, and AI actions — with the official Contentful Management API MCP server supporting semantic search and vector-based content discovery. Open dossier | Sanity MCP Server for Claude Manage Sanity content from Claude — query documents with GROQ, create and publish content, deploy schemas and studios, manage releases, search documentation, and generate images — with the official Sanity remote MCP server hosted at mcp.sanity.io. Open dossier | ConfigCat MCP Server for Claude Manage ConfigCat feature flags from Claude — create, update, and delete flags and targeting rules, manage environments, find and clean up stale flags, and audit change history — with the official ConfigCat MCP server and its 52 tools for the full ConfigCat Management API. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | Webflow | Contentful | Sanity | ConfigCat |
| Added | 2026-06-18 | 2026-06-18 | 2026-06-18 | 2026-06-18 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓CMS collection item create, update, and delete operations write directly to your Webflow project — confirm before applying changes to live sites. Publishing operations make content publicly visible immediately; review changes before asking Claude to publish. The remote server requires OAuth authorization — you control which sites Claude can access during the OAuth flow. | ✓This server uses the Contentful Management API — it can create, update, publish, unpublish, and delete entries, assets, content types, and environments. Use `PROTECTED_ENVIRONMENTS` (comma-separated list) to block write/delete operations on specific environments like `master` or `staging`. Creating or deleting Contentful environments is irreversible for the deleted environment; confirm before executing destructive operations. | ✓Content creation, publishing, schema deployment, and studio operations are live — changes affect your Sanity project immediately. The `deploy_schema` and `deploy_studio` tools push changes to production; review carefully before executing. | ✓Tools can create, update, and delete feature flags, targeting rules, environments, and segments — changes affect live feature flag configuration. Use `list-staleflags` before deleting flags to identify zombie flags and avoid breaking active SDKs. |
| Privacy notes | ✓Site structure, page content, CMS collection schemas, collection items, form submissions, and asset metadata from your Webflow workspace are surfaced in Claude's context. OAuth authentication scopes access to specific sites you authorize — no credentials are stored in your MCP config when using the remote server. | ✓Content entries, asset metadata, content type schemas, locale settings, and AI action configurations from your Contentful space are surfaced in Claude's context. Your `CONTENTFUL_MANAGEMENT_ACCESS_TOKEN` grants full read/write access to the space — treat it as a secret and do not commit it to version control. | ✓Document content, schema definitions, dataset configurations, release metadata, and embedding index data from your Sanity project are surfaced in Claude's context. Authentication uses your Sanity account via OAuth — no API tokens are stored in the MCP configuration. | ✓Feature flag configurations, targeting rules, audience segments, SDK keys, and audit log entries from your ConfigCat account are surfaced in Claude's context. `CONFIGCAT_API_USER` and `CONFIGCAT_API_PASS` are Management API credentials — keep them in the MCP config env and never commit them to version control. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.