Skip to main content
Book a demo

Connect Webflow to Cline CLI

Give Cline CLI governed access to Webflow’s 34 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cline CLI setup guide

Set up

Add Webflow to Cline CLI in four steps

Admins approve the server once. Everyone in Cline CLI then gets it through the same governed connection.

  1. 1

    Approve Webflow in Runlayer

    Add Webflow from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Cline CLI to Runlayer

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Webflow’s 34 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI setup guide
  3. 3

    Sign in to Webflow

    Sign in the way Webflow requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Webflow from Cline CLI

    Webflow’s approved tools appear in Cline CLI. Every call is checked against policy and recorded.

Tools

34 Webflow tools in Cline CLI

Runlayer policy decides which of these Cline CLI users can call. 4 read data only.

  • Ask Webflow AI

    Ask Webflow AI about anything related to Webflow API.

  • Designer asset tool

    Designer Tool - Upload an image from a publicly accessible URL as a Webflow asset.

  • Data agent instructions tool

    Data tool - Manage and generate agent instructions (rules and skills) for a site.

  • Data analyze tool

    Read Webflow Analyze report data for a site, including traffic timeseries, ranked pages, ranked dimensions, ranked engagement events, and aggregate or bucketed time on page.

  • Data apps tool

    Inspect and manage Webflow Cloud apps, GitHub sources, environments, variable metadata, deployments, domains, and logs, including destructive lifecycle changes and deployment triggers.

  • Data assets tool

    Data tool - Manage Webflow site assets and asset folders via the Data API.

  • Data campaigns tool

    Campaign Hub sites, campaigns, page-variation personalization, and campaign analytics.

  • Data cms tool

    Data tool - CMS tool to manage collections, collection fields (static/option/reference), collection field groups, and collection items (list, create, update, publish, unpublish, delete)

See all 34 Webflow tools

Control

What Runlayer can see and stop in Cline CLI

Some controls apply to every client at the gateway. Others depend on what Cline CLI exposes to Runlayer.

  • Gateway policy (available)

    Every Webflow call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cline CLI as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination