The Webflow connector.
Sites and CMS collections. Connect once with your own key. Every agent your team runs reads the same 6 tools under one permission model.
How access is governed
6
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
Webflow exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
Webflow defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every Webflow tool
6 tools, named as the agent sees them.
- list_sitesread
List the Webflow sites this token can reach. Start here — the site `id` is what get_site and list_collections take.
- get_siteread
Get one site with its domains, locales and publish timestamps. Takes `site_id` from list_sites. Use it to answer "when was this last published?".
- list_collectionsread
List the CMS collections on a site (blog posts, team members, products...). Takes `site_id` from list_sites. The collection `id` returned here feeds get_collection and list_collection_items.
- get_collectionread
Get a collection's field schema — the slug and type of every field its items carry. Call this before list_collection_items when you need to know what is inside `fieldData`, or which slug to filter/sort on.
- list_collection_itemsread
List the items in a CMS collection. Takes `collection_id` from list_collections. Item content is under `fieldData`, keyed by field slug — run get_collection first if you do not know the slugs. Filter with `name`/`slug`, or sort with `sort_by` + `sort_order`.
- get_collection_itemread
Get one CMS item in full, exactly as Webflow returns it. Takes `collection_id` from list_collections and `item_id` from list_collection_items. Use this when you already have an item id and want every field without paging a list.
Use it from any agent
The same Webflow tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a Webflow Site Token in your Webflow account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect Webflow once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.