# Webflow MCP server > Manage Webflow sites, CMS collections, pages and Designer elements from your AI assistant. - Listing: https://mcp.tc/i/webflow - Connect: use the server's own URL `https://mcp.webflow.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Design, Websites & CMS](https://mcp.tc/c/design) - Vendor: Webflow - Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe. - Homepage: - Repository: - Package: npm `webflow-mcp-server` ## About Connects an AI assistant to Webflow through the Webflow Data API and the Designer. You can work with sites, CMS collections and items, pages, and elements on the live Designer canvas, for example to draft blog content, add internal links or build page sections. Runs as a hosted streamable HTTP endpoint at mcp.webflow.com with OAuth sign-in to authorize your Webflow sites. Designer features need the Webflow MCP Bridge App opened in the Designer. A local npm package (webflow-mcp-server) is also available and uses a WEBFLOW\_TOKEN API token. Node.js 22.3.0 or higher is required for the documented setups. ## What it can do - Read and manage Webflow sites through the Data API - Work with CMS collections and items such as blog posts - Inspect and edit pages - Create and change elements in the Webflow Designer - Get a link to open a site in the Designer ## Example prompts - "Analyze my last 5 blog posts and suggest 3 new topic ideas with SEO keywords" - "Find older blog posts on similar topics and add internal links to my latest post" - "Create a hero section card on my home page with a CTA button" - "Give me a link to open in the Webflow Designer" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http webflow https://mcp.webflow.com/mcp ``` 2. Start Claude Code, type `/mcp`, pick **webflow** and choose **Authenticate**. A browser window opens for the Webflow sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Settings → Connectors** and click **Add custom connector**. 2. Name it **Webflow** and paste this URL: ```url https://mcp.webflow.com/mcp ``` 3. Click **Add**, then **Connect**, and sign in when Webflow asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://mcp.webflow.com/mcp` and click **Add**. 3. Click **Connect** and sign in when Webflow asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://mcp.webflow.com/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Webflow to sign in. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "webflow": { "url": "https://mcp.webflow.com/mcp" } } } ``` Cursor shows **Needs login** next to the server. Click it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"webflow","type":"http","url":"https://mcp.webflow.com/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "webflow": { "type": "http", "url": "https://mcp.webflow.com/mcp" } } } ``` VS Code asks you to sign in the first time the server starts. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "webflow": { "serverUrl": "https://mcp.webflow.com/mcp" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add webflow --url https://mcp.webflow.com/mcp codex mcp login webflow ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.webflow] url = "https://mcp.webflow.com/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http webflow https://mcp.webflow.com/mcp ``` Then, inside Gemini CLI, run `/mcp auth webflow` to sign in. This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "webflow": { "type": "http", "url": "https://mcp.webflow.com/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.webflow.com/mcp`. ## Details - Server version: 2.0.0 - Last checked: 2026-10-03 (reachable, asks for credentials) - Listed: 2026-10-03 - Updated: 2026-10-03 --- Source: https://mcp.tc/i/webflow (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report