Grok Bot for Meta Ads: your AI media buyer on TikTok and Snap too

Grok Bot can take the media buyer seat on your Meta, TikTok and Snapchat accounts. Connected to Apogee through its MCP server, it sends the morning brief, launches your new creatives, prepares the pause of fatigued ads and moves your Meta winners to TikTok and Snapchat. It prepares, you approve: nothing goes live without your yes. Here is its job description, how to hire it in two minutes and the prompts to copy.

Grok Bot’s job description as a media buyer

Grok Bot is xAI’s personal agent, run with Cursor. It lives in desktop apps (macOS, Windows, Linux) and mobile apps (iPhone, Android), works in the background and repeats tasks at set times with its routines. On its own, it has no access to your ad accounts. Apogee gives it that access through its Meta Ads MCP server, on three platforms, with guardrails.

What it never does: launch or change anything without your yes, add platforms together, or touch an account that is not connected to Apogee.

Hiring Grok Bot: connect it to Apogee as an MCP server

You need two subscriptions: one that gives you Grok Bot, and an Apogee plan that includes the MCP server. According to Cursor’s help:

The message to send Grok Bot, in any conversation:

1. In Apogee, open Settings → Personal agents and pick Grok Bot: the server URL shows with a Copy button.
2. Send the message above to Grok Bot and accept the card that adds the server.
3. Click Authenticate on a computer, or Authorize on a phone: your browser opens Apogee’s sign-in page.
4. Log in to Apogee, check the access and click Authorize.
5. In Grok Bot, Settings → Plugins: Apogee must no longer show Needs auth.

Neither xAI nor Cursor describes this procedure in their documentation yet: the labels come from practice and from Cursor’s forum. If your menus differ, look for Plugins in the Bot’s settings. The Grok Bot page of Apogee’s developer guide covers the same steps.

The access you grant

Grok Bot goes through Cursor’s MCP client, so Apogee’s page reads “Cursor wants to access your Apogee account”. That is expected: it really is Grok Bot you are connecting. Once the connection is made, Apogee recognizes it and lists it as Grok Bot under Settings → Personal agents.

A Bot that only sends briefs is fine with Read. Untick whatever it does not need.

Day one: check that it sees your accounts

The Bot calls list_ad_accounts and answers with the accounts connected to Apogee. If it cannot find the tool, the connection is not finished. One connection serves every Bot on your account.

Grok Bot on Meta Ads: launching the new batch of creatives

The Meta launch is the core of the job. Give Grok Bot a link to your creatives (Google Drive, Dropbox, Frame.io) and the target campaign:

What it does next, with Apogee’s tools:

1. The creatives: import_link imports them into Apogee. Nothing reaches Meta at this stage.
2. The settings: get_latest_in_campaign picks up the latest ad set and the latest ad in the campaign.
3. The interview: get_launch_questions returns the Apogee app’s questions, each with a recommended answer. The Bot asks them one topic at a time, without answering for you.
4. Ads and texts: one creative in 9:16, 4:5 and 1:1 makes a single ad; one primary text, one headline and one description per ad, in the market’s language.
5. The recap, then the launch: prepare_launch creates nothing. After your yes, launch, then launch_status until it is done.

If Meta rejects an ad, launch_status says why and what to do. The Bot does not relaunch an error that needs fixing until you confirm the cause is sorted.

The launch routine: the new batch, every morning

The folder must be shared with “Anyone with the link” or sit in the Drive connected to Apogee. The first time, the Bot asks every question; on later mornings, it reuses your answers.

Grok Bot on TikTok Ads and Snapchat Ads

Sending Meta winners over with the Bridge

An ad that works on Meta deserves its shot on TikTok and Snapchat. Apogee’s Bridge creates paused copies, with texts adapted to each platform, without touching the original Meta ads:

The Bot relies on get_top_performers, on list_bridge_transfers so it never resends an ad that already went over, then on prepare_bridge_transfer and bridge_transfer after your yes. The first time, it asks you for what TikTok requires and Meta does not provide, such as the identity and the call to action. Only videos go through the Bridge.

As a routine, every Monday:

Launching straight on TikTok and Snapchat

The flow is the same as on Meta, with the TikTok or Snapchat account named in the prompt. TikTok creates an ad group (an image becomes a carousel there), Snapchat an ad squad. See TikTok Ads bulk upload and Snapchat Ads bulk upload for what each platform accepts.

For a big sales moment on all three platforms at once:

The Bot asks you what each platform requires: on Meta the objective, the pixel, the Page and the Instagram account; on TikTok the identity and whether to use Smart+; on Snapchat the public profile, the pixel and the countries. Each platform gets its own recap and waits for its own yes.

Its morning routine: the brief, then the pauses

A routine repeats a prompt without you having to ask again:

1. Describe it in the chat, with its frequency and time. On a phone, you can also go through the Bot’s profile, Routines → Add routine.
2. Set the time zone in Settings → Bot → Timezone.
3. Find it on a computer under the Bot’s name, Details tab, then Routines: Pause/Resume, Test, Edit, Delete routine. Test runs a real pass, with real actions.

The morning brief, read-only:

The pause of the ads that burn budget, prepared every evening:

An approval card raised by a routine expires after 30 minutes, but Apogee’s plan stays valid 24 hours. A missed card loses nothing: write “Show me the pending Apogee recap again”, then approve. The numbers come from Apogee’s cross-platform stats.

The Monday report, platform by platform

Apogee never adds platforms together: a TikTok conversion and a Meta conversion are not measured the same way, and a total would suggest otherwise.

Prompts to copy

On top of the routines above, six prompts that earn their keep every week:

Its rules: what it never does without you

Grok Bot checks its own actions with Auto-review, on by default: before a sensitive action, a card offers Allow once, Always allow or Deny. For Apogee, set a rule in Settings → General, Bot section, Auto-review → Custom Rules: describe the action (launching, pausing or changing ads through Apogee), pick Ask first, then Add Rule. Never click Always allow on a launch.

Apogee keeps its own guardrails, whatever the Bot’s settings:

Reads are free within your plan’s daily limit; a change that runs or an ad that gets created uses credits, only when it succeeds. To cut access: Settings → Personal agents in Apogee, then Disconnect next to Grok Bot.

Grok Bot, Grok or Grok Build: which one should run your ads?

xAI’s three products use the same Apogee MCP server, for different jobs. The developer guide covers connecting Grok on grok.com and connecting Grok Build in the terminal:

For a media buyer that works while you are away, Grok Bot is the right pick: it is the only one with routines. On Grok’s Business and Enterprise plans, an admin first has to allow custom connectors.

What if the connection gets stuck?

• Needs auth or Disconnected: open Apogee in the Bot’s plugins, click Authenticate (computer) or Authorize (phone) and log in again.
• The wrong Apogee account shows on the consent page: click Switch before Authorize.
• Cursor team: an admin first allows the server under Plugins & MCPs in the Cursor dashboard; otherwise Apogee shows Disabled by team admin.
• The Bot cannot find list_ad_accounts: the connection is not finished, go back to step 3.

Going further

• Apogee vs the official Meta Ads MCP, and the same comparison for TikTok Ads and Snapchat Ads;
• the same job with Anthropic’s, OpenAI’s and Meta’s agents: Claude Duet as your media buyer, ChatGPT dots on your ads and Muse as your media buyer;
• Running Meta Ads with an AI agent;
• The technical guide to Apogee’s MCP server, with every tool named here.