Skip to main content
Book a demo

Connect Google Sheets to Cursor

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

Book a demo Cursor setup guide

Set up

Add Google Sheets to Cursor in four steps

Admins approve the server once. Everyone in Cursor 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 Cursor to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Google Sheets’s 21 tools show up in Cursor’s own tool list.

    Cursor 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 Cursor

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

Tools

21 Google Sheets tools in Cursor

Runlayer policy decides which of these Cursor 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 Cursor

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

  • Gateway policy (available)

    Every Google Sheets call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cursor 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 Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

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

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination