Skip to main content
Connect GetWhys to Gemini Enterprise as a custom MCP server data store. This setup gives your Gemini Enterprise app organization-level access to GetWhys.

​
Before you start

This setup requires a GetWhys admin to generate OAuth credentials and a Google Cloud administrator to configure Gemini Enterprise. One person can complete both parts if they have both roles. Ask your Google Cloud administrator to complete these prerequisites:
  • Override the organization policy that disables Custom MCP server connectors. This feature is off by default.
  • Grant the person creating the data store the Discovery Engine Editor role (roles/discoveryengine.editor).
  • If egress restrictions are enforced, allow api.getwhys.io.
  • If the project uses VPC Service Controls or enforced data-source restrictions, add custom_mcp to the allowed data sources.
See Google’s Custom MCP prerequisites for the policy details.

​
Connect GetWhys

1

Generate GetWhys OAuth credentials

Generate an OAuth MCP Connector in GetWhys with a label such as gemini. Copy the OAuth Client ID and OAuth Client Secret. GetWhys shows the secret only once.On the connector, click Edit URIs and add this redirect URI:
2

Create a custom MCP server data store

In the Google Cloud console, open Gemini Enterprise → Data stores and click Create data store. Search for Custom MCP Server, then click Add MCP server.
3

Configure OAuth

Select OAuth 2.0 and enter these values:Click Verify Auth, then click Continue.
4

Create the data store

Choose the data connector’s location, enter GetWhys as the name, and click Create. Wait for the data store’s state to change from Creating to Active.
5

Enable GetWhys actions

Open the GetWhys data store and select Actions → Reload custom actions. Select the actions you want to make available, then click Enable actions.Gemini Enterprise calls MCP tools “actions.” They are disabled by default.
6

Connect the data store to your app

In Gemini Enterprise, open Apps and select your app. Go to Connected data sources, click Add existing data stores, select GetWhys, and click Connect.
7

Authorize GetWhys

Open the app’s web URL and select Manage your data. Find GetWhys, click Enable actions, and complete the authorization flow.

​
Verify the connection

In your Gemini Enterprise app, ask: “Who am I in GetWhys?” If Gemini returns your GetWhys organization, you’re connected.

​
Troubleshooting

Custom MCP Server isn’t available — ask an Organization Policy Administrator to turn off the Disable custom MCP server connector for Gemini Enterprise constraint. Verify Auth fails — confirm the OAuth URLs, client credentials, mcp:tools scope, and GetWhys redirect URI. If your project restricts egress, confirm that api.getwhys.io is allowed. No actions appear — wait until the data store is Active, then select Actions → Reload custom actions and enable the actions you need. GetWhys isn’t available in your app — confirm that the data store is connected under Connected data sources and authorized under Manage your data.