How to Connect Webflow to Gemini via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Webflow, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Webflow + Gemini

Let your AI work on a Webflow site: read the site, its pages and SEO settings, CMS collections and items, forms and submissions, assets, and e-commerce products and orders; draft and update CMS items, and publish items or the whole site once you agree. Uses a site API token.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

WEBFLOW_API_TOKEN

Step 1 — Get credentials

1. Sign in at https://webflow.com/dashboard, hover the site and click its gear icon to open Site settings. You need to be a site administrator.
2. In the left sidebar choose Apps & integrations, scroll down to API access at the bottom of the page and click Generate API token.
3. Name the token (for example "AnythingMCP") and choose these scopes:
   • sites:read, sites:write (to publish the site)
   • pages:read, pages:write (for page settings)
   • cms:read, cms:write (to create, change, publish, unpublish or delete items)
   • forms:read, assets:read
   • ecommerce:read (only on an e-commerce site)
4. Click Generate token, copy the token right away and paste it into WEBFLOW_API_TOKEN without the word Bearer, then install the connector.
5. Start with webflow_get_token_info: it shows the scopes and the site id the token grants. Then webflow_list_sites returns the site's details; its id is the site_id the other tools take.

Scopes: scopes cannot be added to a token later. If a tool answers 403 missing_scopes, generate a new token with the missing scope and paste it into WEBFLOW_API_TOKEN.

Read-only setup: tick only the :read scopes and switch off webflow_publish_site, webflow_update_page_settings, webflow_create_item, webflow_update_item, webflow_publish_items, webflow_create_live_item and webflow_update_live_item.

Switched off at install: webflow_delete_item, which deletes a CMS item for good, and webflow_unpublish_live_item, which takes a published item off the website (it stays in the CMS as a draft). Turn them on only if the AI should delete or unpublish items.

One site per token: a site token only reaches the site it was generated on. A site can have up to 5 tokens, and a token expires after 365 days without use. For several sites, install the connector once per site.

Plans: the API works on every site plan, the free Starter plan included. The CMS tools need a plan with the CMS: Starter includes a small one (20 collections, 50 items), Basic none. On Starter, Webflow may refuse publishing single items (webflow_publish_items, webflow_create_live_item, webflow_update_live_item, webflow_unpublish_live_item), as it lists this as a feature of the paid CMS plans: publish the whole site instead. Products and orders need an e-commerce site plan; other sites answer 409.

Staged and live content: every CMS item has a staged version (what editors see) and, once published, a live version on the website. webflow_create_item and webflow_update_item change only the staged content, so nothing changes on the public site; new items are drafts. webflow_publish_items puts chosen items live, and webflow_publish_site publishes every staged change of the site, pages and items. webflow_create_live_item and webflow_update_live_item write straight to the public site. Marking a published item as a draft does not take it off the site; archiving it does, at the next site publish. webflow_list_items shows the staged items, webflow_list_live_items what visitors see.

Publishing is public: confirm first. Before the AI publishes the site or items, writes live items or changes page settings (titles, slugs, SEO and Open Graph texts with webflow_update_page_settings), it tells you exactly what will change on the website and waits for your yes. Webflow accepts one successful site publish per minute.

Field data: an item's content is keyed by each field's slug from webflow_get_collection, not by its display name; name and slug are required for a new item. Rich text is HTML, a reference takes an item id, and a new image is a public URL (at most 4 MB) given as {"url": "https://..."}. Changing an item's slug breaks links to the old URL.

Locales: on a localized site webflow_get_site lists the locales. Without one, the tools use the primary locale.

Rate limits: per token, 60 requests a minute on the Starter and Basic site plans, 120 on the CMS, e-commerce and Business plans. Over the limit Webflow answers 429 with a Retry-After header, usually 60 seconds: wait and try again. List tools return at most 100 entries per page.

Common errors: 400 names the field at fault: an unknown field slug, a value in the wrong format, or a missing name or slug. 401 means the token is wrong, revoked or expired: generate a new one under Site settings → Apps & integrations → API access. 403 (missing_scopes or forbidden) means the token lacks a scope (generate a new token with it) or the site plan does not include the feature. 404 is a wrong id, or an id from another site. 409 means the request clashes with the site's state, for example e-commerce calls on a site without e-commerce. 429 is the rate limit: wait for the Retry-After time.

The connector does not create or change collections and fields, does not edit page content, components or custom code, does not upload or delete assets, does not change form submissions or edit products and orders, and does not handle webhooks, comments or analytics.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Gemini

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Gemini CLI reads MCP servers from ~/.gemini/settings.json (on Windows %USERPROFILE%\.gemini\settings.json). Add:

{
  "mcpServers": {
    "anythingmcp": {
      "httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}

1. Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of YOUR_MCP_API_KEY.
2. Save the file and restart gemini.
3. Run /mcp inside Gemini CLI (or gemini mcp list in your shell): anythingmcp should show as connected.
4. Start prompting: Gemini CLI can now call the Webflow tools.

Available tools

Example prompts

• "List the pages of our Webflow site that have no SEO title or meta description."
• "Which blog posts in the CMS are still drafts, and when were they last updated?"
• "Show me this week's contact form submissions with name, company and message."
• "Create a new post in the Blog collection titled "Spring product update" with a short summary, as a draft only. Do not publish it."

FAQ

Where does Gemini CLI look for MCP servers? In ~/.gemini/settings.json for your user, or in .gemini/settings.json inside a project. gemini mcp list shows each server and whether it connects.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT