Connect an assistant · Personal agents

Connect Meta Muse to Apogee

Meta Muse (the Muse app) 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_…`) for a client Apogee's sign-in does not accept.
Scopes	Read (`read`), Launch (`launch`), Actions (`actions`): ticked on Apogee's page when Meta Muse signs in, or chosen when you create the key (scopes).
Apogee plan	Pro, Growth or Scale (not Starter)
Server instructions	On connection, Apogee tells Meta Muse how to launch: the interview, the recap, your yes (read them).

Set it up

Ask Muse: "Create a custom connector named Apogee, with a capital A, for the MCP server at https://app.apogee.ad/mcp". Muse guides you through it.
If Muse asks for a key: create one in Settings → API with only the scopes it needs, and paste it in the secure field Muse opens.
Give it a recurring task in plain words; it shows in Upcoming.
In Settings → Permissions → Connectors, keep Ask for actions (or Always ask).

Muse adds Apogee as a custom connector, the route Meta documents for a service missing from its catalog. Meta does not review custom connectors and does not describe MCP addresses for them: Muse may ask for an API key instead.

Muse connects Meta ad accounts on its own: Apogee adds TikTok and Snapchat, launches in bulk with your naming convention, and the Bridge.

Written from Meta Help Center: Muse connectors and Meta Help Center: Muse permissions.

Plans

On Meta Muse's side: Muse is available in the United States and Canada.
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): Meta Muse sees exactly what your Apogee account sees.

Check the connection

Ask Meta Muse, in your own words:

"Which Apogee account are you connected to, and with which scopes?" Meta Muse 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." Meta Muse 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 Meta Muse 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 Meta Muse 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

Meta Muse 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."

Every morning, yesterday on every platform with a CPA alert (personal agent)

Yesterday on Meta, TikTok and Snapchat, each platform on its own, in a few lines on your phone, and an alert when a platform's CPA drifts. Read only.

Recurring task

Every morning at [time], send me yesterday on Meta ([Meta ad account]), TikTok ([TikTok ad account]) and Snapchat ([Snapchat ad account]), each platform on its own: spend, CPA, ROAS, and the 3 best and 3 worst ads. Alert me when a platform's CPA is more than [threshold]% above its 7-day average, and say which ads moved it. Never add the platforms together. If something should change, propose it: Show me each change and wait for my yes before you make it.

What it asks you: Your targets once, when Apogee does not know them yet (it can remember them in your business profile).

As a recurring task: Claude Duet, Dots, Grok Bot. It only reads: nothing to approve.

Every evening, the ads that burn budget paused after your OK (personal agent)

Your own rule applied every evening on Meta and TikTok: the agent finds the ads that match it, prepares their pause and asks you. Nothing is paused without your yes.

Recurring task

Every evening at [time], find the ads of [ad account] that spent more than [multiple]× my target CPA without a purchase over the last [days] days, on Meta and TikTok. Prepare their pause and send me the list (name, platform, spend, why). Show me each change and wait for my yes before you make it.

What it asks you: Your target CPA once, when Apogee does not know it yet. The list of ads to pause, with what will change, and your yes (all of them, or the ones you name).

As a recurring task: Claude Duet, Dots, Grok Bot. Nothing is paused before you approve the list.

Every morning, your new creatives launched (personal agent)

A personal agent checks your "to launch" folder every morning, prepares the launch with your naming convention, and asks you before anything is created. You answer from your phone.

Recurring task

Every weekday at [time], check my Google Drive folder [folder link]. If there are creatives that are not launched yet, prepare a launch in my [campaign] campaign of [ad account], one ad set per concept, with my naming convention and the settings of the latest ad set launched there. Send me the full recap and wait for my yes before you launch. If there is nothing new, say nothing. Create everything paused, and show me the full recap before you create anything.

What it asks you: The first time: the launch interview's open questions, one topic at a time. Afterwards it reuses your answers. Each morning with something new: the whole recap (ads ← files, ad sets, texts, budget, status) and your yes.

As a recurring task: a personal agent that runs on its own and asks before acting (Claude Duet, Dots, Grok Bot). In a chat, ask it once.

More templates: the MCP server's prompt templates.

Guardrails and limits

The server enforces them, whatever Meta Muse 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 Meta Muse 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 Meta Muse 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.
Meta Muse 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.
Apogee's page refuses the sign-in (redirect not allowed)	Apogee's sign-in accepts only the callbacks of the assistants of its guide and your own computer (`http://localhost`): use an API key, as shown above.
`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 Meta Muse'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 Meta Muse 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 Meta Muse it is fixed.

Every code: errors.

Disconnect

In Apogee: Settings → Personal agents → Connected agents, then Disconnect next to Meta Muse. 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 Meta Muse: remove Apogee where you added it.

Guides and related pages

Meta Muse connector: your AI media buyer on TikTok and Snap too · also in Français, Español
Meta Ads MCP: run your ads from Claude, ChatGPT or Cursor: the options for a Meta Ads MCP, compared
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