Looker MCP connector
The Looker connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- App credentials
- Free 14-day trial
- No credit card
List Looker users who have no role assigned.
Working in Looker with Elaichi
-
List all Looker users
-
Get single Looker user by ID
-
List all Looker user roles
How to connect Looker to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Looker MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Looker MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Looker MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Looker MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Looker MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Looker to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
What teams do with Looker through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Looker is logged.
-
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.”
What connecting Looker gets you
6 screens from Elaichi, each doing one job for your Looker account.
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, Cursor or Microsoft Copilot
The agent
Ask about Looker users and roles in plain language.
Starter prompts return answers from live Looker users, roles and alerts.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Looker through one endpoint.
Connect any MCP client over OAuth, with no SDK and no shared API key.
Tool catalog
294 Looker tools are ready without custom code.
Browse tool names, resources and methods across Looker users, roles, alerts and dashboards.
Toolboxes
Every team gets its own Looker toolbox.
Curate one toolbox per team and scope it to the Looker work they do.
Shared connections
Teammates query Looker without seeing a credential.
The connections table shows who connected each Looker account and which teams share it.
Audit log
Every Looker call is answerable after the fact.
The append-only log records when, who, what happened, type and Looker resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Looker digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Looker
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Looker
Queued
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 health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
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%
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.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Looker
All three can connect Looker to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Looker tools | Allow or restrict single Looker tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Looker call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
No tools match your search.
Showing 274 of 294 Looker tools here. Connect Looker and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
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, Microsoft Copilot, 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 restricting role changes or user deletion for a role, but it can never widen what Looker already allows.
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 restricting user deletion, role edits, or alert changes. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot, and every other client at the same time.
Does the Looker MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Looker is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Looker?
Yes. Both let Claude, ChatGPT or Cursor use Looker. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Looker call.
How is Elaichi different from Composio for Looker?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Looker: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Looker in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot