Skip to main content
Book a demo

Connect Gmail to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

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

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

    Cline CLI setup guide
  3. 3

    Sign in to Gmail

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

  4. 4

    Use Gmail from Cline CLI

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

Tools

16 Gmail tools in Cline CLI

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

  • Add labels

    Add one or more labels to a message or multiple messages

  • Archive messages

    Archive one or more messages (remove from inbox)

  • Create draft

    Create a draft email that can be edited later or sent

  • Create label

    Create a new label in the user's Gmail account

  • Fetch attachment

    Fetch a Gmail message attachment.

  • Fetch message

    Fetch the full content of a Gmail message using its message ID (don't use external tools to read messages)

  • List drafts

    List all draft messages with pagination support

  • List labels

    List all available labels in the Gmail account

See all 16 Gmail 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 Gmail 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