Skip to main content
Book a demo

Connect Google Docs to Cline CLI

Give Cline CLI governed access to Google Docs’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 Docs 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 Docs in Runlayer

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

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

  4. 4

    Use Google Docs from Cline CLI

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

Tools

21 Google Docs tools in Cline CLI

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

  • Add comment

    Add a comment to a specific text range in a Google Docs document.

  • Apply doc updates

    Apply an ordered batch of raw Google Docs API Request objects to a document via documents.batchUpdate.

  • Create file

    Markdown (recommended, default path): uploaded as text/markdown and converted by Google Drive's native markdown importer (headers, bold, italic, lists, tables, blockquotes, fenced code blocks, links,…

  • Delete between text

    Delete a whole block of a document — a heading and everything beneath it, tables included — by naming the text at each end instead of computing character indices.

  • Delete text

    Delete all occurrences of specific text from a Google Docs document.

  • Edit table

    Structurally edit an existing table in a Google Doc: insert/delete rows and columns, set a column width, style a cell (background color, vertical alignment, padding), replace a cell's text, or…

  • Fetch

    Fetch the content of a Google Docs document using its document ID.

  • Fetch all tabs

    Fetch content from all tabs in a Google Docs document.

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