Webflow MCP server
Webflow is a no-code website builder and CMS, used by marketing and design teams that publish and update sites without a developer for every change. Connect through Arc0 to use the actions your identity is allowed to call.
Agent workflows for Webflow.
List sites
Use when discovering the site selected for this connection. Returns only that site, even if a broader token was supplied.
Get site
Use when inspecting the connected site, its custom domain IDs and CMS locale IDs before editing or publishing.
List collections
Use when finding CMS collection IDs in the connected site before reading or drafting content.
10 Webflow actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
6Look things up, subject to your permissions.
- webflow.list_sitesList sites
Use when discovering the site selected for this connection. Returns only that site, even if a broader token was supplied.
- webflow.get_siteGet site
Use when inspecting the connected site, its custom domain IDs and CMS locale IDs before editing or publishing.
- webflow.list_collectionsList collections
Use when finding CMS collection IDs in the connected site before reading or drafting content.
- webflow.get_collectionGet collection
Use when inspecting field slugs, types and required flags before preparing CMS item data. The collection must belong to the connected site.
- webflow.list_itemsList items
Use when browsing staged CMS content or reading back a write by exact slug or item ID. Continue with offset plus limit while below pagination.total; live content may differ.
- webflow.get_itemGet item
Use when inspecting one staged CMS item by ID or verifying a write before retrying an uncertain outcome. This does not return the live version.
write
2Create and change things. Allow, or ask the user first.
- webflow.create_itemCreate item
Use when creating a staged CMS item. Defaults to draft, excluded from site publish; set isDraft=false to queue it for publication. Supply field slugs including name and slug. Read back by slug before retrying uncertain writes; duplicates are possible
- webflow.update_itemUpdate item
Use when editing staged CMS content. Omitted isDraft reads and preserves current state; false queues publication, true excludes edits from site publish. Existing live content stays live. Slug changes can break links. Read back uncertain writes before retrying
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- webflow.delete_itemDelete item
Use when intentionally deleting a CMS item, including cleanup of a disposable draft. Destructive: do not use to pause publication. Check whether the item still exists before retrying an uncertain outcome.
- webflow.publish_sitePublish site
Use when explicitly publishing all queued site changes, including collaborators’ Designer and CMS changes, to public visitors. Draft items are excluded. Do not use for preview or one item. A 202 accepts the queue request; inspect the site before retrying uncertain results
Control access to Webflow.
Connect the intended Webflow account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
- webflow.create_item: require approval
- webflow.delete_item: deny
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How Webflow connects.
Connect Webflow using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Webflow with your AI client.
Sign in to Arc0 and connect Webflow in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
Webflow with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingWebflow with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingWebflow with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingWebflow with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingWebflow with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingWebflow with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
Webflow and Arc0, answered.
Does Webflow work with Claude Desktop and Claude Code?
Yes, after connecting the account and authorizing the client. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.
Can I use Webflow with OpenAI Codex, ChatGPT and Cursor?
Yes, after connecting the account and authorizing the client. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.
Is this the official Webflow MCP server?
This is Arc0’s integration page, not a claim of an official Webflow server. Arc0 adds a shared connection, policy and audit experience across apps. Consult Webflow for its own current MCP offerings.
Which Webflow actions are supported?
10 registry-defined actions: 6 read, 2 write and 2 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.
Which permissions does Webflow need?
Connect Webflow using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
Can I restrict writes in Webflow?
You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.
What does Webflow through Arc0 cost?
See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.
Plug Webflow into your agent.
Webflow MCP server: 10 actions including list sites, get site, list collections. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
Webflow and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Webflow.