Webflow

Webflow

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.

7 日間無料 · クレゞットカヌド䞍芁 · EU ホスト

Webflow に䜕でも聞ける

AnythingMCP 経由で Webflow に実際のプロンプトを詊そう — Claude がツヌルを呌び出し、回答したす。あなたのメッセヌゞで Enter を抌すず Cloud にむンストヌルしたす。

Webflow を Cloud にむンストヌル
Webflow · MCP 経由でラむブ
共有
Opus 4.7

Claude は AI のため誀るこずがありたす。回答をご確認ください。

2 分でセットアップ

  1. 1cloud.anythingmcp.com で無料トラむアル開始。
  2. 2コネクタヌストアで Webflow をクリック。資栌情報を貌り付け。
  3. 3MCP API キヌを発行し、AI クラむアントを MCP URL に向ける。
Webflow を今すぐむンストヌル

Webflow のガむド

䞻芁 AI クラむアント向けのステップバむステップセットアップ。

Webflow のセットアップ

コネクタ定矩そのものから認蚌情報の入手先、必芁な暩限、このアダプタが呌び出す API。 コネクタ䜜者により英語で提䟛されおいたす。

Webflow

This connector works with one Webflow site through the Data API v2 (https://api.webflow.com/v2), signed in with a site API token: the site, its custom domains and publishing, pages with their SEO and Open Graph settings, CMS collections and items (staged and live), forms and form submissions, assets, and e-commerce products and orders.

Setup (about 3 minutes; you need to be a site administrator)

  1. Sign in at https://webflow.com/dashboard, hover the site and click its gear icon to open Site settings.
  2. In the left sidebar choose Apps & integrations, scroll to API access at the bottom of the page and click Generate API token.
  3. Name the token (for example "AnythingMCP"), choose the scopes below and click Generate token.
  4. Copy the token right away and paste it into WEBFLOW_API_TOKEN, without the word "Bearer".
  5. Run webflow_get_token_info to see the scopes and the site id the token grants, then webflow_list_sites for the site's details.

Scopes: sites:read (and sites:write to publish the site), pages:read (and pages:write for page settings), cms:read (and cms:write to create, change, publish, unpublish or delete items), forms:read, assets:read, and ecommerce:read on an e-commerce site. Scopes cannot be added to a token later: generate a new one.

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. webflow_delete_item and webflow_unpublish_live_item are installed switched off.

One site per token: a site token only reaches the site it was generated on, so webflow_list_sites returns that one site; its id is the site_id the other tools take. 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 and a free workspace included. The CMS needs a site plan that has it: Starter includes a small one (20 collections, 50 items), Basic none, the paid CMS plans more. Webflow lists publishing and unpublishing single CMS items as a feature of the paid CMS plans, so on Starter webflow_publish_items, webflow_create_live_item, webflow_update_live_item and webflow_unpublish_live_item may be refused: 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, webflow_update_item and webflow_delete_item work on staged content and change nothing on the public site. New items are drafts unless is_draft is false, which queues them for the next site publish.
  • webflow_publish_items puts chosen staged items live; 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. webflow_unpublish_live_item takes an item off the site and turns it back into a draft without deleting it.
  • Setting is_draft to true on a published item does not unpublish it: its changes wait as "changes in draft". Setting is_archived to true removes it from the site 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 webflow_publish_site, webflow_publish_items, webflow_create_live_item, webflow_update_live_item or webflow_update_page_settings, tell the user exactly what will change on the website and wait for a yes. Webflow accepts one successful site publish per minute.

Field data: an item's content is fieldData, keyed by each field's slug from webflow_get_collection (not its display name). name and slug are required when creating. Values: plain text as a string, rich text as an HTML string, numbers, true/false for a Switch, ISO 8601 date-times, an option id for an Option field, an item id for a Reference and an array of item ids for a MultiReference, {"url": "https://..."} for a new image (a public URL, at most 4 MB) and an array of those for a MultiImage. Changing a slug breaks links to the old URL.

Locales: on a localized site webflow_get_site lists the locales. CMS tools take a locale's cmsLocaleId, page and asset tools its id as locale_id. Without one, the primary locale is used.

Pagination: list tools take offset and limit (at most 100) and answer with pagination (limit, offset, total). Sites, collections and custom domains come back in one call.

Rate limits: per token, 60 requests a minute on Starter and Basic site plans, 120 on CMS, e-commerce and Business plans, custom on Enterprise. Over the limit Webflow answers 429 with a Retry-After header (usually 60 seconds).

Errors (JSON with code, message and details)

  • 400 bad_request or a validation error: an unknown field slug, a value in the wrong format, or a missing name or slug; details names the field.
  • 401 not_authorized: the token is wrong, revoked or expired.
  • 403 missing_scopes or forbidden: the token lacks the scope (generate a new token with it), or the site plan does not include the feature.
  • 404 resource_not_found: a wrong id, or an id from another site.
  • 409 conflict: the request clashes with the site's state, for example e-commerce calls on a site without e-commerce.
  • 429 too_many_requests: wait for Retry-After.

Out of scope here: creating or changing collections and fields, page content and components, custom code, uploading or deleting assets, changing or deleting form submissions, editing products, SKUs or orders (fulfilment, refunds), webhooks, comments, analytics, the Content Delivery API, and workspace and Enterprise endpoints.

あなたの AI は Webflow から 2 クリック先。

コネクタヌをむンストヌル、資栌情報を貌り付け、AI に質問。7 日間無料、クレゞットカヌド䞍芁。