# Connect any MCP client to Apogee's MCP server: setup, checks, limits and errors

https://www.apogee.ad/developers/mcp/any-client/ (Markdown: https://www.apogee.ad/developers/mcp/any-client.md). Updated 2026-11-03.

Your client 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.

## 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 your client signs in, or chosen when you create the key ([scopes](https://www.apogee.ad/developers/authentication/#scopes)).
- Apogee plan: [Pro, Growth or Scale](https://www.apogee.ad/en/pricing/) (not Starter)
- Server instructions: On connection, Apogee tells your client how to launch: the interview, the recap, your yes ([read them](https://www.apogee.ad/developers/mcp/#instructions)).

## Set it up

1. Server URL `https://app.apogee.ad/mcp`, transport **Streamable HTTP**.
2. Sign-in: OAuth 2.1 with PKCE, discovered from the server, with Dynamic Client Registration. Apogee accepts it from the assistants of this guide and from your own computer (`http://localhost`); any other client uses an API key.
3. API key: create one in [Settings → API](https://app.apogee.ad/home?settings=api) with only the scopes the client needs, and send `Authorization: Bearer apk_…`.

A typical client configuration:

```json
{
  "mcpServers": {
    "apogee": {
      "type": "http",
      "url": "https://app.apogee.ad/mcp",
      "headers": {
        "Authorization": "Bearer apk_…"
      }
    }
  }
}
```

Notes:

- The key names differ by client (`url`, `serverUrl`, `httpUrl`…): check your client's MCP settings.

## 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](https://www.apogee.ad/en/pricing/), [credits](https://www.apogee.ad/developers/credits/)).
- **Your ad accounts** connected in the Apogee app (Meta, TikTok or Snapchat): your client sees exactly what your Apogee account sees.

## Check the connection

Ask your client, in your own words:

1. "Which Apogee account are you connected to, and with which scopes?" Your client calls [`whoami`](https://www.apogee.ad/developers/mcp/whoami/): the Apogee account this connection acts as, the credential used (an assistant's connection or an API key) and its scopes.
2. "List my Meta ad accounts on Apogee, then my TikTok and Snapchat ones." Your client calls [`list_ad_accounts`](https://www.apogee.ad/developers/mcp/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 your client does not find Apogee's tools, check that Apogee is turned on where the last step above says.

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.

```bash
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 your client makes:

```bash
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

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

- **Read** (`read`, 54 tools): 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). For example: [`whoami`](https://www.apogee.ad/developers/mcp/whoami/), [`list_ad_accounts`](https://www.apogee.ad/developers/mcp/list-ad-accounts/), [`get_account_overview`](https://www.apogee.ad/developers/mcp/get-account-overview/), [`get_top_performers`](https://www.apogee.ad/developers/mcp/get-top-performers/), [`get_platform_overview`](https://www.apogee.ad/developers/mcp/get-platform-overview/), [`get_launch_questions`](https://www.apogee.ad/developers/mcp/get-launch-questions/).
- **Launch** (`launch`, 9 tools): Import and upload creatives, prepare and launch ads, run Bridge transfers, create a campaign. For example: [`import_link`](https://www.apogee.ad/developers/mcp/import-link/), [`prepare_launch`](https://www.apogee.ad/developers/mcp/prepare-launch/), [`launch`](https://www.apogee.ad/developers/mcp/launch/), [`prepare_bridge_transfer`](https://www.apogee.ad/developers/mcp/prepare-bridge-transfer/), [`execute_action`](https://www.apogee.ad/developers/mcp/execute-action/).
- **Actions** (`actions`, 18 tools): Pause, activate, change budgets and targeting, duplicate, create ad sets and ads from existing posts. For example: [`pause_ad`](https://www.apogee.ad/developers/mcp/pause-ad/), [`update_budget`](https://www.apogee.ad/developers/mcp/update-budget/), [`execute_action`](https://www.apogee.ad/developers/mcp/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](https://www.apogee.ad/developers/mcp/#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 from a Frame.io, Google Drive or Dropbox link

The same launch from a link: no download, no upload on your side.

```text
Take every creative in [link] and launch them in a NEW ad set in my [testing campaign] campaign of [ad account]. Reuse the settings of the latest ad set and the latest ad launched in 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 files it found behind the link, then the ads it reads from their names: one ad per creative in all its formats. Confirm or correct them. The new ad set's name, and what it copies from the latest ad set and ad. Which Advantage+ enhancements to turn on. The whole recap, then your explicit yes.

Note: Works in every assistant. Google Drive, Dropbox and Frame.io links go through the account you connected in Apogee; a public Frame.io share works without one when downloads are allowed (reading it takes 20 to 30 seconds), a password-protected one does not.

### Weekly review: what to scale, what to cut

Your numbers read for you, and the changes proposed one by one. Nothing changes without your yes.

```text
Look at [ad account] over the last 7 days. Which ads should I scale and which should I cut, judged on [ROAS or CPA]? Show me the numbers, then propose the changes. Show me each change and wait for my yes before you make it.
```

What it asks you: Your targets, 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.

## Guardrails and limits

The server enforces them, whatever your client is told:

- **Your yes before anything changes.** A launch is [`prepare_launch`](https://www.apogee.ad/developers/mcp/prepare-launch/), the recap, then [`launch`](https://www.apogee.ad/developers/mcp/launch/); a change is an action tool, then [`execute_action`](https://www.apogee.ad/developers/mcp/execute-action/); a Bridge transfer is [`prepare_bridge_transfer`](https://www.apogee.ad/developers/mcp/prepare-bridge-transfer/), then [`bridge_transfer`](https://www.apogee.ad/developers/mcp/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`](https://www.apogee.ad/developers/errors/#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](https://www.apogee.ad/developers/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](https://www.apogee.ad/developers/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 your client as a result with `isError: true` and the reason in words, so it can tell you what to do. The common ones:

- [`401`](https://www.apogee.ad/developers/errors/#invalid_api_key): 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 your client 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](https://app.apogee.ad/home?settings=api) and replace it where you pasted it.
- Your client sees Apogee but says it cannot launch or change anything
  The connection lacks a [scope](https://www.apogee.ad/developers/authentication/#scopes), 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`](https://www.apogee.ad/developers/errors/#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`](https://www.apogee.ad/developers/errors/#credits_exhausted)
  This month's credits and the credit packs are used: buy a pack ([credits](https://app.apogee.ad/settings/credits)) or wait for the 1st of the month (UTC). Reads go on.
- [`429`](https://www.apogee.ad/developers/errors/#rate_limited) `rate_limited`, `quota_exceeded`, `daily_read_cap`
  A limit of the list above is reached: wait the seconds the answer gives ([rate limits](https://www.apogee.ad/developers/rate-limits/)).
- [`412 meta_not_connected`](https://www.apogee.ad/developers/errors/#meta_not_connected), `platform_not_connected`
  Apogee's own Facebook, TikTok or Snapchat connection expired, not your client's: log in to the Apogee app again, or reconnect the platform there.
- [`410 plan_expired`](https://www.apogee.ad/developers/errors/#plan_expired), `409 plan_already_launched`
  The recap was prepared more than 24 hours earlier, or already ran: ask your client to prepare it again.
- [`409 same_error_again`](https://www.apogee.ad/developers/errors/#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 your client it is fixed.

Every code: [errors](https://www.apogee.ad/developers/errors/).

## Disconnect

- **In Apogee:** Settings → MCP → **Connected assistants**, then **Disconnect** next to the client. 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](https://app.apogee.ad/home?settings=api) → **API keys**, then **Revoke**. Whatever uses the key stops at once.
- **In your client:** remove Apogee where you added it.

## Guides and related pages

- [Meta Ads MCP: run your ads from Claude, ChatGPT or Cursor](https://www.apogee.ad/en/blog/meta-ads-mcp/): the options for a Meta Ads MCP, compared
- [The MCP server](https://www.apogee.ad/developers/mcp/): how a launch works, every tool, prompt templates
- [Authentication](https://www.apogee.ad/developers/authentication/): API keys, OAuth, scopes
- [Every assistant, for AI agents](https://www.apogee.ad/developers/llms.txt)