Skip to content

Analytics

Looker MCP connector

The Looker connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent manage Looker users, roles, alerts, and boards on your behalf, with every action running as the signed-in person and recorded in an audit log.

  • How it connects. App credentials. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Looker to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Looker once

  1. Open Connections, choose Add connection, and pick Looker.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste your Looker app credentials. Looker authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

looker
Looker
Allium
Amplitude
Artie
Botify
DoiT
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Looker to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Looker to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Looker to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Looker to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Looker through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Data

    Set up a new analyst in Looker

    Create the Looker user, assign the right roles, and confirm the setup in one ask instead of clicking through the admin pages.

  • IT

    Review who holds which Looker role

    List every Looker user and role, spot people with more access than their job needs, and tighten a role without opening Looker.

  • Analytics

    Find out why an alert fired

    Search Looker alerts, read the notifications behind a threshold breach, and follow the ones that matter to your dashboards.

  • Operations

    Keep alert thresholds current

    Update a Looker alert when a target changes, or trigger it right away to check the new threshold behaves as expected.

  • Finance

    Follow revenue alerts without a Looker login

    Follow or unfollow Looker alerts on the numbers you care about, and catch the notification the moment a figure crosses a line.

  • IT

    Offboard a leaver from Looker

    Remove the departing person's Looker roles and delete the user, with the change recorded against whoever asked for it.

Try asking

  • “List Looker users who have no role assigned.”
  • “Which Looker alerts fired more than once this week?”
  • “Show roles added to Looker in the last 30 days.”

See all 294 Looker tools below

AI tools

Looker tools for your AI agents

294 tools are ready to call through Elaichi's MCP endpoint the moment you connect Looker, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Looker gets you

6 screens from the product, each doing one job for your Looker account.

The agent

Ask about Looker users and roles in plain language.

Starter prompts return answers from live Looker users, roles and alerts.

  • users
  • roles
  • alerts
  • dashboards

Ask Elaichi to work across your apps.

List Looker users who have no role assigned.

Which Looker alerts fired more than once this week?

Show roles added to Looker in the last 30 days.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Looker through one endpoint.

Connect any MCP client over OAuth, with no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

294 Looker tools are ready without custom code.

Browse tool names, resources and methods across Looker users, roles, alerts and dashboards.

  • List all Looker users
  • Get single Looker user by ID
  • Delete a Looker user by ID
  • Create a Looker user
ElaichiTools
Tool Action Description
List all Looker users List Get information about all users in Looker. Returns user details including id, display_name, email, first_name, last_name, is_disabled, and credentials information.
Get single Looker user by ID Get Get information about the user with a specific id in Looker. Returns full user information if the caller is an admin or the user themselves; otherwise returns minimal public info including user name and avatar URL.
Delete a Looker user by ID Delete Delete the user with id in Looker. This operation deletes the user and all looks and other information owned by the user.
Create a Looker user Create Create a user with the specified information in Looker. Returns the created user's id, display_name, email, first_name, last_name, is_disabled status, locale, role_ids, group_ids, and credentials details.
Update a Looker user by ID Update Update information about the user with a specific id in Looker. Returns the updated user object including id, first_name, last_name, email, display_name, is_disabled, locale, role_ids, group_ids, and credentials details.

Toolboxes

Every team gets its own Looker toolbox.

Curate one toolbox per team and scope it to the Looker work they do.

  • Data platform
  • Analytics engineering
  • Revenue operations
  • Finance
ElaichiToolboxes
Name Source template Tools Created

Data platform toolbox

Looker · roles and permission sets

Looker starter 18 Mar 4, 2026

Analytics engineering toolbox

Looker · looks and dashboards

9 Mar 2, 2026

Revenue operations toolbox

Looker · sales dashboards and alerts

24 Feb 27, 2026

Finance toolbox

Looker · scheduled reports and queries

Looker starter 6 Feb 19, 2026

IT administration toolbox

Looker · users and group membership

31 Jan 30, 2026

Customer support toolbox

Looker · read-only looks and alerts

12 Jan 22, 2026

Shared connections

Teammates query Looker without seeing a credential.

The connections table shows who connected each Looker account and which teams share it.

  • Data platform
  • Analytics EMEA
  • Revenue operations
  • Finance reporting
ElaichiConnections
Connection Scope Status Access
LO

Looker (Data platform)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
LO

Looker (Analytics EMEA)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
LO

Looker (Revenue operations)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
LO

Looker (Finance reporting)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
LO

Looker (IT administration)

Connected by Clara Nowak

Personal • Active Not shared
LO

Looker (Support read-only)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Looker call is answerable after the fact.

The append-only log records when, who, what happened, type and Looker resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Looker Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Looker Users Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Looker Users List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires and the Looker digest ships.

Six steps fetch Looker alerts, group them, draft a digest, await approval, then post back.

Looker digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch users

    Looker

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Looker

    Queued

Collections and dashboards

Looker health arrives before anyone asks for it.

Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.

Looker health

Refreshed 4 minutes ago · every 15 minutes · from the users collection

Live

Users

1,284 ↓ 12%

Roles

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Users created

Last 14 days

By team

Share of activity

Data platform 34%

Analytics EMEA 27%

Revenue operations 21%

Finance reporting 18%

FAQ

Frequently asked questions

How do I connect Looker to Claude?

Connecting Looker takes two steps. First, connect Looker in Elaichi by entering its app credentials once; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste in https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Looker is ready in Claude.

Does Looker work with ChatGPT and Cursor as well as Claude?

Yes. Once Looker is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Looker once and every client picks it up.

What can an AI agent actually do with my Looker data?

With Looker connected, an agent can list and look up Looker users, create or update them, and assign or change roles. It can search Looker alerts, follow or unfollow them, read the notifications behind them, update their thresholds, trigger one on demand, and list your Looker boards. Short, concrete asks such as "show me every Looker user with the Admin role" work better than long paragraphs, because Looker has hundreds of actions and the agent searches for the right one.

Does connecting Looker give the AI access to every user, role, and alert?

No. Every call to Looker runs inside the access of the person who signed in, so an agent sees the Looker users, roles, alerts, and boards that person could already see. Elaichi can narrow that further, for example by hiding role changes or user deletion from a team, but it can never widen what Looker already allows.

Can my team share one Looker connection?

Yes. One person connects Looker in Elaichi and shares the connection with a team, and nobody else ever handles the Looker credentials. Each teammate still signs in to Elaichi as themselves, so every change to a Looker user, role, or alert is logged under the name of the person who made it.

Can I stop an agent from deleting or changing things in Looker?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Looker users and alerts while blocking user deletion, role edits, or alert changes. A blocked action is never advertised to Claude, ChatGPT, or Cursor at all, so no prompt, however worded, can reach it.

What happens to a Looker connection when someone leaves?

When you offboard a person in Elaichi, their access to Looker through Elaichi ends at once, and every client they used stops working for them. A shared Looker connection keeps working for everyone else on the team. If you want Looker gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

Put Looker in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.