Skip to main content
GetWhys connects to Gemini Enterprise as a custom MCP server data store. Once connected, Gemini can call GetWhys tools for research interviews, personas, messaging frameworks, brand voice, and content scoring.
Custom MCP connectors are available in Gemini Enterprise (Google Cloud). The consumer Gemini app and Gemini for Workspace do not currently offer the same self-serve custom MCP setup. If you’re on those surfaces, reach out via Teams, Slack, Google Chat, or email [email protected] and we’ll help you pick the right path.

​
Who does what

For OAuth-only setups, you may not need a token. Keep the token handy if your Gemini connector UI supports Bearer / API key auth.

​
Create a Custom MCP Server data store

In Gemini Enterprise (Google Cloud console / Gemini Enterprise admin):
  1. Go to Data stores (or Connected data stores) and create a new data store
  2. Search for Custom MCP Server and select it
  3. Set MCP Server URL to:
  1. Complete the Authentication fields your admin UI requires:
    • If the UI supports a Bearer / API key header: use Authorization: Bearer <Organization MCP API Token> (see Authenticating)
    • If the UI requires OAuth (Authorization URL, Token URL, Client ID / Secret): use GetWhys OAuth. If you need the exact OAuth endpoint values for Gemini Enterprise, reach out via Teams, Slack, Google Chat, or email [email protected] — Gemini Enterprise’s OAuth client registration is org-specific
  2. Name the connector (e.g. GetWhys) and create the data store
  3. Open the data store → Actions (or equivalent) and reload / enable the GetWhys tools you want available

​
Connect the data store to your Gemini Enterprise app

Attach the GetWhys data store to the Gemini Enterprise app your team uses, then in chat:
  1. Open the connector / tools control in the chat input
  2. Toggle GetWhys on
  3. Complete any Authorize / OAuth prompt if shown

​
Verify

With GetWhys toggled on, ask the verify prompt: “Who am I in GetWhys?”

​
Troubleshooting

You only have the consumer Gemini app — custom MCP isn’t self-serve there yet. Use a generic MCP client for developer tools that wrap Gemini, or contact GetWhys about Gemini Enterprise. Data store creates but no actions / tools show — open the data store, reload custom actions, and enable the GetWhys tools. Confirm the MCP URL ends in /mcp. OAuth or auth fields fail — Gemini Enterprise often needs GetWhys OAuth client details registered for your Google tenant. Reach out via Teams, Slack, Google Chat, or email [email protected] with your Gemini Enterprise project context.