Connect any MCP client to Apogee

At a glance

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 with only the scopes the client needs, and send Authorization: Bearer apk_….

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

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, 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: 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, 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.

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"}'

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.

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

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.

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.

More templates: the MCP server's prompt templates.

Guardrails and limits

The server enforces them, whatever your client 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 your client as a result with isError: true and the reason in words, so it can tell you what to do. The common ones:

Every code: 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 → 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: 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