Skip to main content
Book a demo

Connect Google Sheets to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

Add Google Sheets 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 Google Sheets in Runlayer

    Add Google Sheets 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 Google Sheets’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 Google Sheets

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

  4. 4

    Use Google Sheets from Cline CLI

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

Tools

21 Google Sheets tools in Cline CLI

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

  • Add sheet

    Add a new sheet (tab) to an existing spreadsheet.

  • Append

    Append data to a spreadsheet.

  • Autofill

    Extend a formula or detected series from a source range into a larger destination range (like dragging the fill handle).

  • Clear

    Clear the values in a range while leaving the rows, columns, and formatting in place.

  • Clear filter

    Remove a sheet's filter, restoring any rows it was hiding.

  • Create

    Create a new spreadsheet.

  • Create filter

    Turn on filtering over a range of a sheet (the funnel button in the Sheets UI), so rows can be sorted and filtered by column.

  • Delete rows

    Delete rows from a sheet, shifting the rows below them up.

See all 21 Google Sheets 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 Google Sheets 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