Skip to main content
Book a demo

Connect Looker to Cursor

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

Book a demo Cursor setup guide

Set up

Add Looker to Cursor in four steps

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

  1. 1

    Approve Looker in Runlayer

    Add Looker 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, Looker’s 30 tools show up in Cursor’s own tool list.

    Cursor setup guide
  3. 3

    Sign in to Looker

    Each user signs in to Looker with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Looker from Cursor

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

Tools

30 Looker tools in Cursor

Runlayer policy decides which of these Cursor users can call.

  • Dev mode

    Allows toggling the Looker IDE session between Development Mode and Production Mode.

  • Generate embed URL

    Generates a signed, private embed URL for specific Looker content, allowing users to access it directly.

  • Get connection databases

    Retrieves a list of databases available through a specified Looker connection.

  • Get connection schemas

    Retrieves a list of database schemas available through a specified Looker connection.

  • Get connection table columns

    Retrieves a list of columns for one or more specified tables within a given database schema and connection.

  • Get connection tables

    Retrieves a list of tables available within a specified database schema through a Looker connection.

  • Get connections

    Retrieves a list of all database connections configured in the Looker system.

  • Get dashboards

    Searches for saved dashboards in a Looker instance.

See all 30 Looker 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 Looker 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