Provider REST API

Marketing

Connect Claude to Webflow

Read a Webflow site's CMS collections and pages, stage item changes, and publish when you mean to. Toolspoke puts 11 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connection
Provider REST API
Authentication
API token
Actions exposed
11
Cost per call (typical)
1 credit
Adapter
Maintained by Toolspoke

Connected in three steps

  1. 1

    Install Webflow

    Open the marketplace in your workspace, add Webflow to the project your agents work in, and it appears on the gateway immediately.

  2. 2

    Connect the credential

    Authenticate with api token. Where to get one, and what it has to be able to reach, is the next section.

  3. 3

    Point your agent at the gateway

    Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json
{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Webflow shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code

Run it in your project, then /mcp to sign in

claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop

Settings, then Connectors, then Add custom connector

https://toolspoke.com/mcp
Cursor

~/.cursor/mcp.json, or .cursor/mcp.json for one project

{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex

~/.codex/config.toml

[mcp_servers.toolspoke]
url = "https://toolspoke.com/mcp"
VS Code

.vscode/mcp.json, or the MCP: Add Server command

{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Webflow asks for

API token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

API tokenRequired
webflow.com → your site → Settings → Apps & integrations → API access → Generate API token. Grant it cms:read, cms:write, pages:read, sites:read and - only if this connection should be able to publish - sites:write. A site token reaches exactly one site, which is the narrowest thing to hand over.
a1b2c3…

What Claude can do in Webflow

11 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads
8Reads
Writes
2Writes
Destructive
1Destructive

Reads

8

Fetches data and changes nothing.

  • list_sites

    List the sites this token can reach, with each site's id, display name, short name, custom domains, timezone and when it was last published. Free, like every read here - Webflow bills nothing per call and only rate-limits, at 60 requests a minute on Starter and Basic plans and 120 on CMS and above. The `id` values are what every other operation in this connector takes. This is the connection test: it needs no arguments, creates nothing, and a token scoped to the wrong site shows up here as an empty or unexpected list rather than as a puzzling 404 later.

  • get_site

    Read one site: its name, workspace, timezone, custom domains with their ids, and `lastPublished`. Free. Two things here are worth the call - `customDomains[].id`, which is what publish_site takes (it wants domain ids, not domain names), and `lastPublished`, which tells you whether staged CMS edits are already waiting to go out. A site with a `lastPublished` older than its `lastUpdated` has unpublished changes, and publishing will release all of them, not only yours.

  • list_collections

    List the CMS collections on a site - blog posts, team members, case studies, whatever this site models - with each collection's id, display name, singular name and slug. Free. Collection ids are what the item operations take. This returns the collections themselves and not their fields; get_collection is where the field definitions are.

  • get_collection

    Read one collection's schema: every field with its `slug`, `type`, `displayName`, whether it `isRequired`, and any validations. Free. Call this before create_item or update_item, always. `fieldData` is keyed by these field slugs and Webflow rejects a key it does not recognise, so a body built by guessing from a field's label rather than its slug fails as a validation error rather than being ignored. `name` and `slug` are required on every collection. Reference fields take another item's id; asset fields take {"fileId":"…","url":"…"}. Structure, not content, which is why this one is logged like any other read.

  • list_collection_items

    List the items in a CMS collection - the staged copy, which is what the Designer shows and what a future publish would release. Free. Paging is offset and limit, and the response carries `pagination` with the total. Narrow with `name` or `slug` rather than fetching everything: a collection of a thousand blog posts is a very large answer, and each item carries its whole `fieldData`, including rich-text bodies. `isDraft: true` on an item means it will not be published even when the site is; `isArchived: true` means it has been taken out of the collection without being deleted. The payload is somebody's site content, so it is kept out of the audit log.

  • get_collection_item

    Read one CMS item by id - its whole `fieldData`, plus `isDraft`, `isArchived`, `lastPublished` and `lastUpdated`. Free. This is the call to make before update_item: a PATCH replaces the fields it names and leaves the rest alone, so reading first is how you know what you are about to change. An item whose `lastUpdated` is newer than its `lastPublished` has staged edits that publish_site would release. The payload is somebody's site content, so it is kept out of the audit log.

  • list_pages

    List the static pages of a site with their ids, titles, slugs, parent ids, SEO title and description, Open Graph fields and whether each is a draft or archived. Free. Page ids are what get_page_content takes, and also what publish_site's `pageId` takes when only one page should go out. This returns page settings rather than page copy - the copy is in get_page_content - so it is logged like any other read.

  • get_page_content

    Read the text content of one page as a list of DOM nodes - every heading, paragraph and rich-text block the Designer put there, each with its own node id. Free. This is how to audit what a page actually says without opening Webflow, and it is the only read here that returns page copy rather than settings. It reads the staged version, so a page edited but not published shows the new text. Paging is limit and offset over the node list; a long marketing page can be hundreds of nodes. The payload is the site's own prose, so it is kept out of the audit log.

Writes

2

Creates or updates something on the other side.

  • create_collection_item

    Add an item to a CMS collection, staged. Nobody outside the workspace sees it until publish_site runs, which is exactly why this is a write and publish_site is destructive - Webflow also offers an /items/live route that skips staging and goes straight to the public site, and this connector deliberately does not declare it. `fieldData` must use the field slugs get_collection returns, and must include `name` and `slug`; an unknown key is rejected rather than ignored. `isDraft` defaults to true on this route, so an item created without it stays a draft even after the site is published - pass false when the item is meant to go out with the next publish. Free to call. The item body is the caller's own prose, so it is kept out of the audit log in both directions.

  • update_collection_item

    Change fields on an existing CMS item, staged. Only the fields named in `fieldData` are replaced; anything omitted keeps its current value, so read the item with get_collection_item first if you need to know what that is. Nothing reaches the public site until publish_site runs - the /items/live route that would skip staging is deliberately not declared here. Free to call. This overwrites the previous value of every field it names and Webflow keeps no version history through the API, so the old text is gone: treat it as an edit that cannot be undone from here even though it is not yet public. Setting `isArchived: true` takes the item out of the collection without deleting it, and setting `isDraft: true` holds it back from the next publish.

Destructive

1

Deletes or permanently alters something. Worth granting on purpose.

  • publish_site

    Put the site live. This is the operation that makes changes public, and it cannot be quietly undone: Webflow has no unpublish that restores the previous build, and everyone who visits the domain sees the new one from the moment it finishes. It is destructive for a second reason too - it releases every staged change on the site, not only the ones this agent made. Somebody else's half-finished edit in the Designer goes out with yours. Call get_site first and compare `lastUpdated` against `lastPublished` to see whether there is other work waiting. `customDomains` takes domain *ids*, from get_site's `customDomains[].id`, not domain names; `publishToWebflowSubdomain` publishes to the free .webflow.io address and defaults to false. Passing neither publishes nothing, so name at least one target. Needs a token with sites:write; a read-and-write grant that stops short of destructive cannot reach this, which is the point.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else
The 11 actions above are the whole of it. A call to any other name is refused before it reaches Webflow rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It reaches no further than your credential
Toolspoke holds no access to Webflow of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Webflow
Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Webflow. An agent has to ask.
It does not smooth over provider limits
Toolspoke does not retry, queue or back off around Webflow's own rate limits. A call that Webflow refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Webflow?

11 named actions: 8 that only read, 2 that write and 1 that delete or permanently alter something. They include list_sites, get_site and list_collections. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Webflow connector need?

API token. The connector asks for api token. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Webflow connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 11 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Webflow connector not do?

The 11 actions above are the whole of it. A call to any other name is refused before it reaches Webflow rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Toolspoke holds no access to Webflow of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Webflow. An agent has to ask. Toolspoke does not retry, queue or back off around Webflow's own rate limits. A call that Webflow refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Webflow's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Webflow?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and the credits spent. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.