Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Looker to Claude Code

Let Claude build and update Looks and dashboards in Looker. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Looker to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Looker, you add a Looker MCP server: a small hosted service that exposes Looker's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Looker account. No API keys pasted into config files.

claude mcp add --transport http looker https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Looker once connected?

Full read-write Looker access lets Claude create and update Looks and dashboards, run and save explore queries, manage schedules and content folders, and adjust dashboard filters, then save once you approve. The reporting work that used to mean clicking through the UI happens where your model already lives.

  • Create a new Look from an explore query and save it to a folder
  • Update tiles and filters on an existing dashboard
  • Run a saved explore query and write the results back as a refreshed Look
  • Schedule a dashboard or Look delivery on a cadence you set
  • Organize content by creating folders and moving Looks between them
  • Adjust a dashboard's default filters after you approve the change

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Looker access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Looker API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Looker changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Looker connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Looker connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Looker account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Looker's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Looker?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Looker account it signs in with. Revoking access is one click in Looker.

More on the Looker connector

Looker connector for claude.aiAmazon Redshift + Claude CodeMetabase + Claude CodeRedis + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us