How to Connect Google Ads to Grok Bot

A Bot can work on Google Ads in two ways.

• Through its browser. Every Bot has a cloud computer with a browser. You sign in to Google Ads there and the Bot clicks through the interface. The two ads Bots in SpaceXAI's own Grok Bot for Marketing guide work this way: their templates put the live interface first and exports second.
• Through a connector. A connector hands the Bot the Google Ads API instead of a screen. Reports come back as data, and a change is a named operation with exact values. Grok Bot's docs say to prefer a connector when one is available, because it is often more reliable than clicking through a website.

AdPlug is that connector for Google Ads. You add it once and every Bot on your account can use it.

• Grok Bot. The desktop app runs on macOS, Windows, and Linux, and there are mobile apps for iPhone, iPad, and Android. You sign in with a Cursor account. Cursor's plans page lists access as included with every paid individual Cursor plan and with Cursor Teams, or through an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ subscription linked to that account. There is also a free trial credit.
• An AdPlug account. The free plan is enough to set this up and test it: view only, 500 requests in the first month and 50 a month after that, on one ad platform. AdPlug's Google Ads MCP is the server your Bot talks to.
• Access to the ad account. A Google identity with at least read access to the Google Ads accounts you want the Bot to work on. A manager account (MCC) login covers every account under it.

Steps 1 and 2 happen in AdPlug. Steps 3 to 5 happen in Grok Bot. Allow about ten minutes the first time.

1. 1

   Create your AdPlug account

   Go to adplug.app/signup, sign in with Google or email, and follow the short onboarding. It ends on your AdPlug dashboard.

   

2. 2

   Connect Google Ads to AdPlug

   On the dashboard, click Connect Google Ads (or open the Connections page). AdPlug takes you through Google's own sign-in; use the Google identity that can see the accounts you want your Bot to work on.

   

   If you manage clients through a manager account (MCC), connect the manager identity. One connection then covers every account under it.

   

3. 3

   Ask your Bot to add AdPlug

   Grok Bot calls its connectors plugins. Most are added from Plugins in the sidebar (the docs also call it the Marketplace). AdPlug is not in that list, so you add it as a custom MCP server. Grok Bot's docs describe two kinds, Remote HTTPS and Command. AdPlug is the Remote HTTPS kind and signs you in through your browser, so there is no key to paste.

   The simplest way is to ask. Open a chat with your Bot and send:

   “Add a custom MCP server called AdPlug - Google Ads at https://api.adplug.app/mcp/google-ads”

   Keep the words custom MCP server in the message so the Bot uses this address rather than searching the Marketplace. It shows the name and address back to you; confirm them.

   https://api.adplug.app/mcp/google-ads

   Copy

   

   

4. 4

   Authorise the connection

   Grok Bot asks you to Authorize the plugin and opens AdPlug's sign-in in your browser. Use the same email as your AdPlug account and click Approve. If Grok Bot shows Waiting for authorization, choose Reopen to bring the browser tab back.

   

   Back in Grok Bot, open Plugins in the sidebar and check that AdPlug - Google Ads appears under Installed. Cursor's plugin help covers the other statuses you might see, such as Needs auth.

   

5. 5

   Test the connection

   In a chat with your Bot, type @, pick AdPlug - Google Ads, and ask:

   “List my Google Ads accounts.”

   The Bot calls the google_ads_list_accounts tool and returns your accounts with their names, currencies, and manager hierarchy. If your accounts are listed, the connection works end to end.

   

Swap in your own account and campaign names. More copy-paste prompts live in the prompt playbooks.

Grok Bot can also run work on a schedule. It calls this a routine: you ask the Bot in chat, say what it should do and when, and it keeps running in the cloud while your laptop is closed. A weekly report is the obvious first one:

Give the routine a time zone, the account it covers, and what to do when data is missing. A new routine waits for its next scheduled time, so open it and use Test to run it once now. Keep scheduled work read only. Cursor's help pages say an approval raised by a routine expires after about ten minutes if nobody answers, so a scheduled job that needs a yes will usually just stop. Every run also uses AdPlug requests, and the free plan drops to 50 a month after the first, so a routine you keep wants a paid plan.

AdPlug gives the Bot two tools for campaign changes: a preview tool that returns the exact change without applying it, and an execute tool that applies it. That covers budgets, bids, keywords and negatives, ads, audiences, and campaign settings. On Google Ads the execute tools only apply a change that was previewed first. The free plan is view only; creating and editing campaigns needs a paid AdPlug plan.

Grok Bot has its own approval prompts for sensitive actions, with Allow once, Always allow, and Deny. Do not rely on those alone for ad changes. Put the boundary in the request: ask for a draft that shows the current value, the proposed value, and the expected impact, and tell the Bot to wait. Answer with Allow once rather than Always allow, and add an Ask first rule under Auto-review for anything that edits campaigns. SpaceXAI's marketing guide draws the same line: its analyst Bot pulls Google Ads data and recommends, and does not change a live ad, bid, or budget.

Plugins are shared across your account. Grok Bot's docs note that installed connectors are not isolated to one Bot, and that all your Bots use the same cloud computer and app logins. Any Bot you create can reach the ad accounts this connection can see.

Teams are different. On a Team Bot, the Team Bots docs say a custom MCP server that signs in with OAuth uses the account of whoever is talking to the Bot. AdPlug signs in that way, so each teammate authorises once with their own AdPlug account. A Team Bot also asks for approval only in its owner's own chat; in a teammate's chat it works within what the owner set up without stopping to ask. So set the limit in AdPlug: on the Max and Agency plans the owner can set each teammate to View only or Can edit per platform.

Report calls and executed changes are recorded in your AdPlug Usage and Audit Log, so you can check what a Bot did while you were away.

If you use Grok in the browser rather than Grok Bot, add AdPlug as a custom connector. The Grok connector docs give three steps:

1. Go to grok.com/connectors.
2. Click New Connector, then select Custom.
3. Enter the AdPlug address above and complete the sign-in.

Connectors are available to all Grok users. On Grok Business and Enterprise a team admin provisions the connector first.

Click any item to expand the answer.

The same AdPlug account connects other platforms and assistants.

Email support@adplug.app with setup questions or bug reports. Most replies come back the same business day.