Skip to main content
Book a demo

Connect Clay to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

Add Clay 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 Clay in Runlayer

    Add Clay 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 Clay’s 21 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI setup guide
  3. 3

    Sign in to Clay

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

  4. 4

    Use Clay from Cline CLI

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

Tools

21 Clay tools in Cline CLI

Runlayer policy decides which of these Cline CLI users can call. 12 read data only and 3 can change or delete data.

  • Add company data points

    Add data points to companies in an existing search.

  • Add contact data points

    Add data points to contacts in an existing search.

  • Ask question about accounts

    Ask a natural language question about one or more accounts available in Clay Audiences.

  • Find and enrich company

    Find and enrich a single company by domain or LinkedIn URL.

  • Find and enrich contacts at company

    Search for contacts at a company by role, title, name, or department.

  • Find and enrich list of contacts

    Find and enrich specific named contacts at their companies.

  • Get credits available

    Check if credits are available for the workspace.

  • Get current workspace

    Report which Clay workspace this connection is pinned to.

See all 21 Clay 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 Clay 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