Connect an assistant · Coding tools

Connect Grok Build to Apogee

Grok Build (xAI's coding agent, in the terminal) connects to Apogee's MCP server at https://app.apogee.ad/mcp with Apogee's sign-in (OAuth) or an API key. It then works on your Meta, TikTok and Snapchat ad accounts through Apogee's 80 tools: it reads freely, and launches or changes ads only after your explicit yes to a recap.

OAuth or API key Streamable HTTP Apogee: Pro, Growth or Scale Markdown

At a glance

Server URL	`https://app.apogee.ad/mcp`
Transport	Streamable HTTP, stateless: every request is a `POST` answered with JSON.
Sign-in	Apogee's sign-in (OAuth 2.1 with PKCE): the assistant opens Apogee's page, you log in and click Authorize; or an API key (`Authorization: Bearer apk_…`), shown below.
Scopes	Read (`read`), Launch (`launch`), Actions (`actions`): ticked on Apogee's page when Grok Build signs in, or chosen when you create the key (scopes).
Apogee plan	Pro, Growth or Scale (not Starter)
Server instructions	On connection, Apogee tells Grok Build how to launch: the interview, the recap, your yes (read them).

Set it up

Add the server from your terminal:
Terminal
```
grok mcp add --transport http apogee https://app.apogee.ad/mcp
```
The first time Grok uses Apogee, a browser opens: log in to Apogee and click Authorize. To sign in again, type /mcps in Grok, select apogee and press i.

Default: for you, in every project (~/.grok/config.toml). --scope project writes .grok/config.toml in this project: never put a key there. grok mcp doctor apogee checks the connection.

Grok Build also reads Claude Code's MCP servers: if Apogee is in Claude Code, it is already there.

With an API key instead

Terminal, with an API key

grok mcp add --transport http apogee https://app.apogee.ad/mcp \
  --header "Authorization: Bearer apk_…"

Written from xAI docs: Grok Build MCP servers and xAI docs: Grok Build plugins.

Plans

On Apogee's side: the Pro, Growth or Scale plan includes the MCP server, with credits every month (10,000 on Pro, 30,000 on Growth, 100,000 on Scale); Starter does not. A 7-day trial for €1 includes a quarter of the plan's credits (plans, credits).
Your ad accounts connected in the Apogee app (Meta, TikTok or Snapchat): Grok Build sees exactly what your Apogee account sees.

Check the connection

Ask Grok Build, in your own words:

"Which Apogee account are you connected to, and with which scopes?" Grok Build calls whoami: the Apogee account this connection acts as, the credential used (an assistant's connection or an API key) and its scopes.
"List my Meta ad accounts on Apogee, then my TikTok and Snapchat ones." Grok Build calls list_ad_accounts, with platform set to tiktok or snapchat for the others. An empty list means no ad account of that platform is connected in the Apogee app.

Both are reads: free within the daily free reads, nothing changes. If Grok Build does not find Apogee's tools, check that Apogee is turned on where the last step above says.

Check the server from a terminal

Without a credential the server answers 401 with a WWW-Authenticate header pointing to https://app.apogee.ad/.well-known/oauth-protected-resource/mcp: that is where OAuth discovery starts.

No credential: expect 401

curl -i -X POST https://app.apogee.ad/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

With your API key in $APOGEE_API_KEY, the same whoami call Grok Build makes:

whoami with an API key

curl -X POST https://app.apogee.ad/mcp \
  -H "Authorization: Bearer $APOGEE_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}}'

What it can do

Grok Build gets Apogee's 80 tools, filtered by the scopes of its connection: a tool outside them is not even listed.

Scope	What it allows	Tools	For example
Read `read`	Read ad accounts, campaigns, ad sets, ads and their numbers on Meta, TikTok and Snapchat, the comments of your ads and the Bridge's stats; follow imports, launches and transfers (nothing is sent).	54	`whoami`, `list_ad_accounts`, `get_account_overview`, `get_top_performers`, `get_platform_overview`, `get_launch_questions`
Launch `launch`	Import and upload creatives, prepare and launch ads, run Bridge transfers, create a campaign.	9	`import_link`, `prepare_launch`, `launch`, `prepare_bridge_transfer`, `execute_action`
Actions `actions`	Pause, activate, change budgets and targeting, duplicate, create ad sets and ads from existing posts.	18	`pause_ad`, `update_budget`, `execute_action`

By effect: 54 only read; 19 prepare a plan or an action; 4 write in Apogee only and 3 change the ad account, after your yes. Every tool, its parameters and its cost: all the tools.

Prompts to start with

Replace the [brackets] with your own names. Each prompt ends with Apogee's safety reminder: "Create everything paused, and show me the full recap before you create anything." or "Show me each change and wait for my yes before you make it."

Launch files whose names mean nothing

Files named IMG_4512.mp4 or final_v3_OK(1).mov, launched without a naming convention: you check the ads, rename them and put them in groups, one ad set per group.

Prompt

Launch the videos in [folder or link] in my [campaign] campaign of [ad account]. The file names mean nothing: group the formats of each creative, show me the ads, let me rename them and put them in groups, one ad set per group. Reuse the settings of the latest ad set and ad of that campaign. Create everything paused, and show me the full recap before you create anything.

What it asks you: Which ad account, when you have several. The ads it built: files whose names differ only by their format words (feed and story, 4x5 and 9x16…) are the 4:5, 9:16 and 1:1 of one creative, linked into one ad; every other file is its own ad, named after the file. Link the files of one creative, or split them. A name for each ad, if you want other names than the files'. Which ads go together in a group: each group becomes one ad set (One Concept One Adset). What it copies from the latest ad set and ad of the campaign, and whether anything should change. The whole recap, then your explicit yes.

A folder on your computer needs an assistant that can run commands on it (Claude Code, Cursor…). In Claude or ChatGPT on the web, use a Frame.io, Google Drive or Dropbox link.

Weekly report on every platform

Last week on Meta, TikTok and Snapchat, each platform on its own (its own currency, never added up): spend and results against the week before, the best and the worst ads, what the Bridge's copies did, and what to do next.

Prompt

Give me my weekly report for [brand]: the last 7 days against the 7 days before, on Meta ([Meta ad account]), TikTok ([TikTok ad account]) and Snapchat ([Snapchat ad account]), each platform on its own. Spend, ROAS and CPA, the 3 best and the 3 worst ads, and what to scale or cut. Show me each change and wait for my yes before you make it.

What it asks you: Your targets (ROAS or CPA) when Apogee does not know them yet: it can remember them in your business profile. Each proposed change (pause, budget up or down) with what it will change, and your OK for each one.

More templates: the MCP server's prompt templates.

Guardrails and limits

The server enforces them, whatever Grok Build is told:

Your yes before anything changes. A launch is prepare_launch, the recap, then launch; a change is an action tool, then execute_action; a Bridge transfer is prepare_bridge_transfer, then bridge_transfer. Nothing is created, changed or transferred before your explicit yes to the whole recap.
Ads are created paused unless you ask otherwise.
A prepared plan or action is valid 24 hours and runs once.
Daily budget cap: a daily budget above 500 in the ad account's currency is refused (budget_above_cap).
25 launches and Bridge transfers per ad account in 24 hours through the MCP and the API.
2,000 units per assistant connection or API key in 24 hours: a read 1, a change 2, Apogee's AI 5, a launch or a transfer 10.
MCP requests: 600 on Pro, 1,200 on Growth and Scale per 15 minutes (rate limits).
Credits: reads are free up to 5,000 on Pro, 10,000 on Growth and Scale a day; a change on an ad platform, an ad created and Apogee's AI cost credits, only when they succeed (credits).
Each platform on its own: Meta, TikTok and Snapchat keep their own currency and attribution; Apogee never adds them up.

Errors and fixes

A refused tool call comes back to Grok Build as a result with isError: true and the reason in words, so it can tell you what to do. The common ones:

What you see	Why, and the fix
`401`: Apogee needs authentication, or every call fails	The sign-in was disconnected in Apogee, or its refresh token (valid 60 days) expired: connect again from the authorization step. An access token lasts 1 hour and Grok Build renews it on its own. With a key: the key is wrong, revoked or past its end date. Create a new one in Settings → API and replace it where you pasted it.
Grok Build sees Apogee but says it cannot launch or change anything	The connection lacks a scope, so those tools are not listed. Connect again and keep Launch and Actions ticked on Apogee's page, or create a key with those scopes.
`403 upgrade_required`	The Apogee account is not on a plan with the MCP. It works again as soon as the account is on Pro, Growth or Scale.
`402 credits_exhausted`	This month's credits and the credit packs are used: buy a pack (credits) or wait for the 1st of the month (UTC). Reads go on.
`429` `rate_limited`, `quota_exceeded`, `daily_read_cap`	A limit of the list above is reached: wait the seconds the answer gives (rate limits).
`412 meta_not_connected`, `platform_not_connected`	Apogee's own Facebook, TikTok or Snapchat connection expired, not Grok Build's: log in to the Apogee app again, or reconnect the platform there.
`410 plan_expired`, `409 plan_already_launched`	The recap was prepared more than 24 hours earlier, or already ran: ask Grok Build to prepare it again.
`409 same_error_again`	The last launches on this ad account failed with the same error: fix its cause (the platform's message says what), then tell Grok Build it is fixed.

Every code: errors.

Disconnect

In Apogee: Settings → MCP → Connected assistants, then Disconnect next to Grok Build. It loses access at once; ads already launched are not touched, and you can connect it again at any time.
An API key: Settings → API → API keys, then Revoke. Whatever uses the key stops at once.
In Grok Build: remove the apogee server with the CLI's MCP commands (grok mcp --help lists them).

Guides and related pages

Meta Ads MCP: run your ads from Claude, ChatGPT or Cursor: the options for a Meta Ads MCP, compared
Same vendor: Grok, Grok Bot
The MCP server: how a launch works, every tool, prompt templates; every assistant
Authentication: API keys, OAuth, scopes
This page in Markdown, and llms.txt for AI agents