Looker
Looker serves its managed MCP server from the Looker instance, at https://{instance}/mcp. A Looker admin registers Willow as an OAuth client. The client ID is a GUID you choose. There is no client secret. Each person then signs in with their own Looker user, and the agent inherits that user's roles. It is the Looker card with the Official badge. Willow also has a built-in Looker connector.
The instance must be Looker-hosted (Looker (Google Cloud core) or Looker (original)).
Set up Looker
A Looker admin does this once.
- In the Admin panel, go to Authentication → Manage OAuth clients → Custom Clients → Add New.
- Set Client ID to a unique string that does not start with
com.looker.(that prefix is reserved). - Set Redirect URIs to the URI from Willow's setup step. You can add more than one.
- Optionally set Restrict to Group ID so only members of that Looker group can authorize.
- Save, and copy the Client ID. There is no secret.
You can do the same with the Register OAuth App API, POST /api/4.0/oauth_client_apps/{client_guid}, with enabled set to true.
Set up Willow
- Go to MCP Servers → + Add MCP server, open the Looker card with the Official badge, and click + Use.
- Enter the Looker instance host.
- Keep OAuth sign-in. Paste the Client ID. Leave the client secret empty.
- Click Check connection and sign in to Looker. Assign groups and Publish.
Troubleshooting
Looker rejects the client as a forgery
Cause: The client ID or redirect URI in the sign-in request does not match the registered client.
Solution: Use the same client ID you registered, and paste Willow's redirect URI into the custom client without retyping it.