Webflow Official Remote MCP Server
Webflow's hosted MCP (mcp.webflow.com/mcp) exposes the Webflow Data API โ sites, pages, CMS collections and items โ to agents with scoped OAuth 2.1 authorization.
- Provider
- Webflow โ
- Categories
- ๐จ Design & UI/UX
ไธญๆ็ฎไป
Webflow ๅฎๆน่ฟ็จ MCP ๆๅกๅจใAI ไปฃ็ๅฏ้่ฟ OAuth 2.1 ๅๅบ็ซ็นใ่ฏปๅ้กต้ข็ปๆๅนถ็ฎก็ CMS ้ๅไธๆก็ฎใ
Maintainer of Webflow? Claim or update this listing โ
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"webflow": {
"url": "https://mcp.webflow.com/mcp"
}
}
}claude mcp add --transport http webflow https://mcp.webflow.com/mcp
Or add to .vscode/mcp.json:
{
"servers": {
"webflow": {
"type": "http",
"url": "https://mcp.webflow.com/mcp"
}
}
}- Open Settings โ Connectors (Integrations) โ Add Custom Connector.
- Paste the endpoint URL:
https://mcp.webflow.com/mcp - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"webflow": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.webflow.com/mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"webflow": {
"serverUrl": "https://mcp.webflow.com/mcp"
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"webflow": {
"url": "https://mcp.webflow.com/mcp"
}
}
}Add to ~/.codex/config.toml โ Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.webflow] url = "https://mcp.webflow.com/mcp"
Add to cline_mcp_settings.json (Cline โ MCP Servers โ Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"webflow": {
"type": "streamableHttp",
"url": "https://mcp.webflow.com/mcp"
}
}
}Add to ~/.gemini/settings.json under mcpServers โ httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"webflow": {
"httpUrl": "https://mcp.webflow.com/mcp"
}
}
}๐งฐ Webflow MCP Tools & Schema (6)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| list_sites ~37 tok | ๐ข Read | List Webflow sites accessible to your account. | โ |
| get_site ~49 tok | ๐ข Read | Get details of a single Webflow site. | siteId*: string |
| list_pages ~51 tok | ๐ข Read | List pages and their SEO metadata on a site. | siteId*: string |
| list_cms_collections ~50 tok | ๐ข Read | List CMS collections on a site. | siteId*: string |
| list_cms_items ~66 tok | ๐ข Read | List items in a CMS collection. | collectionId*: stringlimit: number |
| create_cms_item ~73 tok | ๐ Write | Create a draft item in a CMS collection. | collectionId*: stringfieldData*: object |
๐ก๏ธ Security, Quality & Context Token Audit
Every tool definition (name + description + input schema) is injected into your LLMโs context on every request โ Estimate per-call LLM token cost โ
- No prompt-injection or hidden-character anomalies detected in tool descriptions
- Streamable HTTP primary endpoint (current 2025-03-26 transport)
- OAuth 2.1 with PKCE S256 enforced
- Official first-party endpoint operated by the vendor
- Manually verified by RemoteMCP.net
๐ OAuth 2.1 & Security
- Auth type
- OAuth 2.1
- Dynamic Client Registration
- โ Supported
- PKCE S256
- โ Supported
- Scopes
sites:readcms:readcms:write- Protected resource metadata
- https://mcp.webflow.com/.well-known/oauth-protected-resource (expected location)
๐งฉ Recommended Agent Skills
๐ Webflow MCP Endpoint Overview & Security Guide
Webflow MCP โ Remote MCP Server
Webflow's remote MCP connects agents to your site data layer โ inventory sites and pages, pull CMS collection schemas, and create or update collection items for content workflows โ authorized per user with granular OAuth scopes.
Official Webflow MCP Endpoint & Transport Architecture
- Endpoint URL:
https://mcp.webflow.com/mcp - Transport: Streamable HTTP
Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. Webflow MCP does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
Webflow MCP uses OAuth 2.1 โ the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow โ PKCE and Dynamic Client Registration, so no manual client setup is needed โ and simply open a browser consent screen.
Of the 6 cataloged tools, 5 are read-only and 1 can write or mutate state (create resources, run SQL, post messages). Grant access only to the accounts and projects you intend agents to act on, and prefer scoped credentials or a dedicated workspace where the provider supports them.
Common Troubleshooting & Connection Tips
- 401 Unauthorized on connect โ that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact
WWW-Authenticatechallenge. - "Session expired" / stale
Mcp-Session-Idโ just re-sendinitialize; stateless clients can ignore session headers entirely. - Designer/canvas editing is not exposed โ scope is sites, pages and CMS data.
- Approve CMS read/write scopes separately in the Webflow consent screen.
๐ How to Connect
- Copy the Webflow MCP endpoint URLThe remote endpoint is https://mcp.webflow.com/mcp.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http webflow https://mcp.webflow.com/mcp. Cursor: add"webflow": { "url": "https://mcp.webflow.com/mcp" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Complete the OAuth consentOn first connection your client opens a Webflow consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
- Verify with the online inspectorPaste https://mcp.webflow.com/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm Webflow MCP's 6 tools respond.
โ FAQ
What is the Webflow MCP remote MCP endpoint?
The primary endpoint is https://mcp.webflow.com/mcp. It is an official first-party server operated by Webflow, speaking the Streamable HTTP transport.
How do I authenticate with Webflow MCP?
Webflow MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.
I'm getting a 401 Unauthorized from Webflow MCP โ what's wrong?
A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.
Which MCP clients work with Webflow MCP?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http webflow https://mcp.webflow.com/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, Kiro (`~/.kiro/settings/mcp.json`), and Claude Desktop via the `mcp-remote` bridge.
What tools does Webflow MCP expose?
6 tools are cataloged in this directory โ including `list_sites`, `get_site`, `list_pages` and more. Use our online inspector to fetch the live tool list straight from the endpoint.
๐ Connect Guides
๐ Embed Status Badge in README
Related Servers
Figma's official remote MCP server. Agents can pull design context, variables, Code Connect mappings and screenshots from your Figma files.
Canva's official remote MCP server. Agents can search your designs, generate new designs from templates, autofil brand content and export to image or PDF โ with interactive MCP Apps rendering.
CastHTML's hosted remote MCP server. CastHTML's MCP lets Claude, Cursor and other AI agents publish generated HTML dashboards or Markdown research reports as sandboxed, shareable online links (cast_live_... API key as bearer). It authenticates with a bearer token or API key sent via the Authorization header.
The official drawio (diagrams.net) remote MCP server โ public and authless. Agents can generate diagrams as drawio XML and open them directly in the editor via interactive MCP Apps.