Connect Cursor to Apogee

At a glance

Set it up

1. Create an API key in Settings → API with the scopes Cursor needs.
2. Open ~/.cursor/mcp.json (create it if needed) and add Apogee with your key:
   ~/.cursor/mcp.json Copy

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

3. Turn Apogee on from Customize in the sidebar, then ask in the agent chat.

Keep the key in ~/.cursor/mcp.json (yours only), never in a project's .cursor/mcp.json that you share. Or write "Bearer ${env:APOGEE_API_KEY}" and set that variable.

Cursor also signs in with OAuth, from the desktop app, its web agents and Grok Bot (which runs on Cursor's connectors).

Checked on 10 October 2026 against Cursor docs: MCP.

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): Cursor sees exactly what your Apogee account sees.

Check the connection

Ask Cursor, in your own words:

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

Cursor 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 [folder] on my computer 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.

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.

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.

More templates: the MCP server's prompt templates.

Guardrails and limits

The server enforces them, whatever Cursor 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 Cursor 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

• An API key: Settings → API → API keys, then Revoke. Whatever uses the key stops at once.
• In Cursor: delete the apogee entry from ~/.cursor/mcp.json.

Guides and related pages

• Cursor MCP server: add Apogee to run your Facebook Ads · 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