---
ref: tool:webflow/update-cms-items
name: Update CMS items
company: company:webflow
workflows: []
access: [mcp, cli, api]
tags: [capability:publish-content, category:cms, has:api, has:cli, has:mcp]
docs: https://developers.webflow.com/data/reference/cms/collection-items/staged-items/update-items
updated: 2026-09-27
---

# Update CMS items

Updates the fields of one or more items in a CMS collection, holding changes to published items in draft until they are published.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "webflow": { "url": "https://mcp.webflow.com/mcp" } } }
```

Call the MCP tool `data_cms_tool` with `PATCH /collections/{collection_id}/items`.

Server URL: https://mcp.webflow.com/mcp

### CLI (official)

Install the command and sign in with it, then confirm it runs.

```sh
npm install -g @webflow/webflow-cli
webflow --version
```

Run `webflow cms items update`.

### API (official)

- Base URL: https://api.webflow.com/v2
- Endpoint: `PATCH /collections/{collection_id}/items`
- Auth: send the header `Authorization: Bearer $WEBFLOW_API_TOKEN`
- Docs: https://developers.webflow.com/data/reference/rest-introduction

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.