Skip to main content
Book a demo

Connect Granola to Gemini CLI

Give Gemini CLI governed access to Granola’s 7 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Gemini CLI setup guide

Set up

Add Granola to Gemini CLI in four steps

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

  1. 1

    Approve Granola in Runlayer

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

  2. 2

    Connect Gemini CLI to Runlayer

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

    Gemini CLI setup guide
  3. 3

    Sign in to Granola

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

  4. 4

    Use Granola from Gemini CLI

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

Tools

7 Granola tools in Gemini CLI

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

  • Get account info

    Get the email, active workspace, joined workspaces (names and IDs), and effective note-access scopes for the Granola account currently connected to this MCP session.

  • Get meeting transcript

    Get the full transcript for a specific Granola meeting by ID.

  • Get meetings

    Get detailed meeting information for one or more Granola meetings by ID.

  • List meeting folders

    List the user's Granola meeting folders.

  • List meetings

    List the user's Granola meeting notes within a time range.

  • Query Granola meetings

    Query Granola about the user's meetings using natural language.

  • Switch workspace

    Change your saved active Granola workspace.

Control

What Runlayer can see and stop in Gemini CLI

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Gemini 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 Gemini CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Gemini CLI’s model sees it.

  • Redact output in place (not available)

    Gemini CLI can only add text to a tool result, not replace it, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.

In Gemini CLI

  • Enforcement needs Gemini CLI 0.26.0 or newer.
  • When Runlayer blocks a call or its output, Gemini CLI shows the model the block reason instead.

Frequently asked questions

Connect more

Find another combination