Skip to content

How to connect your ad accounts to Gemini Enterprise

Use Get MCP Ads directly in Gemini Enterprise. Your Google Cloud administrator configures the connector once; each person then signs in and reads their own…

guides/setup/gemini-enterprise.md

Connection URL

https://mcp.getmcpads.com/mcp?catalog=compact

Your Google Cloud administrator configures this connector with its dedicated OAuth client and PKCE. Each user then authorizes their own Get MCP Ads access.

Both readings are on this page.

For you

What the answer looks like, and what to type to get it.

Gemini on gemini.google.com with a Workspace account does not currently support this custom MCP connection. For a conversation directly in Gemini, use Gemini Enterprise on Google Cloud. Google Chat is a separate option.

Capabilities and boundaries

  • Reports, campaign management, saved reviews, alerts and Sheets exports use the same authorized Get MCP Ads tools. Availability still depends on plan, account selection, workspace permissions and provider support.
  • Native alerts and export schedules run on Get MCP Ads after the chat closes.
  • Results come back as conversation text; the embedded views shown in Claude and ChatGPT are not part of these routes. Use the dashboard for visual media selection, account setup and uploads.
  • Keep each client workspace explicit. Review the exact account, campaign, budget, settings and revision before approving a change. A timeout is not permission to repeat an uncertain write.

This route is for the Gemini Enterprise application on Google Cloud. A Google Workspace subscription alone does not provide this connector. An administrator must configure the custom MCP connector and enable its actions.

  1. Your Google Cloud administrator requests a dedicated confidential OAuth client for this Enterprise integration from Get MCP Ads.
  2. Configure Streamable HTTP with https://mcp.getmcpads.com/mcp?catalog=compact. Set authorization URL https://mcp.getmcpads.com/oauth/authorize and token URL https://mcp.getmcpads.com/oauth/token.
  3. Register the Google callback https://vertexaisearch.cloud.google.com/oauth-redirect. Enter the issued client ID and secret in Google’s protected connector configuration, never in a conversation. Select client-secret-post authentication (leave HTTP Basic Authentication off), enable PKCE (S256) and request scope mcp.
  4. Refresh the connector’s custom actions after creation, then enable the discovery tools and run_tool. The compact catalogue is capped at 90 tools; search_tools and describe_tool discover other authorized capabilities, then run_tool calls them. Keep Google’s write confirmations enabled.
  5. Each collaborator opens your organization’s Gemini Enterprise app, selects Sources → Get MCP Ads → Authorize and completes their own consent. Enable this source in the conversation. Verify the accounts shown before requesting a report.

Before your administrator starts

A Google Cloud project, Gemini Enterprise access and the required Discovery Engine permissions are needed. Google may require a project-level custom-MCP policy exception and allowed connector domains. Ask an administrator to review these settings; do not disable organization-wide protections. Google licensing and Cloud charges are separate from Get MCP Ads. You do not need the Get MCP Ads Enterprise plan just to use this client; your existing plan limits still apply.

Test the connection

text
Use Get MCP Ads to list my accessible workspaces and ad accounts. Do not change anything.

A successful response names only the accounts you authorized. Next request a read on one of those accounts.

If Gemini keeps looking for tools

Stop repeated discovery calls rather than letting them consume your allowance. Try the guided read below, replacing the placeholders with IDs from your own account list. Gemini may display a review step even for this read. Never approve a different operation.

text
Call describe_tool with name="reddit_get_campaigns". Then call run_tool with that name and the exact schema arguments for adAccountId="YOUR_REDDIT_ACCOUNT_ID" and workspace_id="YOUR_WORKSPACE_ID". Do not call list_workspaces again. Do not modify anything.

If authorization says “contact an administrator”

Close old consent popups, reload the Gemini Enterprise app and start Sources → Get MCP Ads → Authorize once again. A stale PKCE connection state can cause this generic Google error; a fresh page usually resolves it. Other causes are possible. If it persists, contact support with the time and error message, never your tokens or client secret. Keep PKCE enabled.

Before using campaign changes

Keep Google’s confirmation controls enabled. Review the exact account, action and values before approving a change.

For your agent

The tool sequence, the parameters that matter, and what will be refused.

Both readings as Markdown: /guides/setup/gemini-enterprise.md

Do not auto-install. These integrations require administrator setup. Establish this user’s own connection and check the accounts it returns before claiming access. Never paste secrets into chat. Preserve per-user permissions and wait for OAuth consent.

This route is for the Gemini Enterprise application on Google Cloud. A Google Workspace subscription alone does not provide this connector. An administrator must configure the custom MCP connector and enable its actions.

  1. Your Google Cloud administrator requests a dedicated confidential OAuth client for this Enterprise integration from Get MCP Ads.
  2. Configure Streamable HTTP with https://mcp.getmcpads.com/mcp?catalog=compact. Set authorization URL https://mcp.getmcpads.com/oauth/authorize and token URL https://mcp.getmcpads.com/oauth/token.
  3. Register the Google callback https://vertexaisearch.cloud.google.com/oauth-redirect. Enter the issued client ID and secret in Google’s protected connector configuration, never in a conversation. Select client-secret-post authentication (leave HTTP Basic Authentication off), enable PKCE (S256) and request scope mcp.
  4. Refresh the connector’s custom actions after creation, then enable the discovery tools and run_tool. The compact catalogue is capped at 90 tools; search_tools and describe_tool discover other authorized capabilities, then run_tool calls them. Keep Google’s write confirmations enabled.
  5. Each collaborator opens your organization’s Gemini Enterprise app, selects Sources → Get MCP Ads → Authorize and completes their own consent. Enable this source in the conversation. Verify the accounts shown before requesting a report.

Before your administrator starts

A Google Cloud project, Gemini Enterprise access and the required Discovery Engine permissions are needed. Google may require a project-level custom-MCP policy exception and allowed connector domains. Ask an administrator to review these settings; do not disable organization-wide protections. Google licensing and Cloud charges are separate from Get MCP Ads. You do not need the Get MCP Ads Enterprise plan just to use this client; your existing plan limits still apply.

Test the connection

text
Use Get MCP Ads to list my accessible workspaces and ad accounts. Do not change anything.

A successful response names only the accounts you authorized. Next request a read on one of those accounts.

If Gemini keeps looking for tools

Stop repeated discovery calls rather than letting them consume your allowance. Try the guided read below, replacing the placeholders with IDs from your own account list. Gemini may display a review step even for this read. Never approve a different operation.

text
Call describe_tool with name="reddit_get_campaigns". Then call run_tool with that name and the exact schema arguments for adAccountId="YOUR_REDDIT_ACCOUNT_ID" and workspace_id="YOUR_WORKSPACE_ID". Do not call list_workspaces again. Do not modify anything.

If authorization says “contact an administrator”

Close old consent popups, reload the Gemini Enterprise app and start Sources → Get MCP Ads → Authorize once again. A stale PKCE connection state can cause this generic Google error; a fresh page usually resolves it. Other causes are possible. If it persists, contact support with the time and error message, never your tokens or client secret. Keep PKCE enabled.

Before using campaign changes

Keep Google’s confirmation controls enabled. Review the exact account, action and values before approving a change.

Manage your ads from your AI assistant

Start for free

Free with 1 ad account, no card. Pro is free for 7 days.