Can I use Webflow as a CLI?

Yes. KosmoKrator exposes a Webflow CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Webflow through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Webflow tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Webflow credentials stored?

Webflow credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Webflow MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

cms

Webflow CLI for Headless Automation

Use the Webflow CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write Manual OAuth token auth

Submit Webflow feedback View package source

Webflow CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Webflow CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Webflow CLI for Headless Automation
kosmokrator integrations:configure webflow --set access_token="$WEBFLOW_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call webflow.webflow_list_sites '{}' --json

Discovery Before Execution

Agents and scripts can inspect Webflow docs and schemas before choosing a function.

kosmo integrations:docs webflow --json
kosmo integrations:docs webflow.webflow_list_sites --json
kosmo integrations:schema webflow.webflow_list_sites --json
kosmo integrations:search "Webflow" --json
kosmo integrations:list --json

Useful Webflow CLI Functions

Function	Type	Parameters	Description
`webflow.webflow_list_sites`	Read	none	List all Webflow sites the authenticated user has access to. Returns site IDs, names, and domains needed for further CMS operations.
`webflow.webflow_get_site`	Read	id	Get details for a specific Webflow site by its ID. Returns site name, domain, publishing status, and other metadata.
`webflow.webflow_list_collections`	Read	site_id, limit, offset	List CMS collections for a Webflow site. Collections are content models (e.g., "Blog Posts", "Team Members") that hold structured items.
`webflow.webflow_list_items`	Read	collection_id, limit, offset	List items in a Webflow CMS collection. Returns paginated results with item IDs, field data, and draft/publish status.
`webflow.webflow_get_item`	Read	collection_id, id	Get a single CMS item from a Webflow collection by its ID. Returns full field data including rich text, images, and references.
`webflow.webflow_create_item`	Write	collection_id, fields, live	Create a new item in a Webflow CMS collection. Pass field data as key-value pairs matching the collection's schema. Set live to true to publish immediately.
`webflow.webflow_get_current_user`	Read	none	Get the currently authenticated Webflow user. Returns user profile including name, email, and account details.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Webflow CLI Pages

CI Webflow CLI for CI. Cron Jobs Webflow CLI for cron jobs. Shell Scripts Webflow CLI for shell scripts. Coding Agents Webflow CLI for coding agents.