Skip to content

Connecting Meta Ads

Cora can report on your Meta ads (Facebook and Instagram), in the missions you choose. It is read-only. Cora can read your ad accounts, campaigns, ad sets, ads, their results and Meta’s insights about them, and she cannot create, change, turn on, pause or spend on anything.

It uses Meta’s own hosted MCP server, https://mcp.facebook.com/ads. Meta does not let Cora register itself there, so your organisation uses its own Meta app: your Meta admin makes it once, and a Cora org admin enters its App ID in Cora. Cora needs no app secret. Then each person signs in with their own Facebook login, the same way as Connecting with the service’s sign-in. The connection is theirs: they decide which missions Cora may use it in. See Personal connections for the rules. This page uses an invented company, Kestrel Cycles, and a team member, Megan.

  • MCP turned on for the organisation (see Connecting an MCP server). An org admin does that once.
  • Someone who can make apps in Meta for Developers for your business.
  • For each person who will connect: a Facebook login that can see the ad accounts Cora should read, and a role on your Meta app.
  • Connect turned on by the operator. If the Organisation setup step says Connect is not set up, ask the operator.

Do this once, in Meta for Developers.

  1. Open My Apps and create an app, or use one your business already has.
  2. Open Use cases, choose Add use cases, then Ads and monetization, and add Create & manage ads with ads MCP server.
  3. Open the settings of Facebook Login for Business and add Cora’s callback address as a Valid OAuth Redirect URI. Copy it from the Organisation setup section of Meta Ads’s page on Cora’s Connections page; it looks like https://<your Cora console>/v1/oauth/callback and must match exactly.
  4. Open App roles and give each person who will connect a role on the app, for example Developer or Tester. People without a role cannot sign in with the app.
  5. Copy the App ID from the top of the app’s dashboard. You do not need the app secret, and Cora never asks for it.

App review. Your app does not need Meta’s app review while the people who connect have a role on it and read your own business’s ad accounts. Meta asks for review (Advanced Access to ads_mcp_management) only when an app works on behalf of other businesses, such as an agency’s clients.

Step 2: a Cora org admin enters the App ID

Section titled “Step 2: a Cora org admin enters the App ID”
  1. Open Connections on the left rail. Under Needs an admin to set up first, Meta Ads says Organisation setup needed: press Set up beside it. The first section of its page, Organisation setup, has the Meta Ads card: choose Set up.
  2. Paste the App ID (digits only) and choose Save. There is no address and no secret to enter.

The card then shows Set up, the server address, the App ID and No secret needed. Change lets you enter another App ID; Remove forgets the app. Either one stops every Meta Ads connection in the organisation at once, because each was made with the old app, so everyone needs to Reconnect. Only org admins see this card. A member sees Waiting for an org admin and the names of the organisation’s admins instead.

  1. Open Connections on the left rail and press Connect beside Meta Ads.
  2. In the Account section, choose Connect…. The short name (meta) and the address are filled in for you. If it says “Meta Ads is not set up for your organisation yet”, ask one of the org admins it names to do step 2.
  3. In the dialog choose Connect. Meta’s page opens in a new window. Sign in with Facebook, check the permissions and approve.
  4. The window closes by itself and the card shows the connection. Finish the sign-in in the same browser you pressed Connect in.

Cora asks Meta for two permissions only: ads_mcp_management (to use the MCP server) and ads_read (to read your ads). She never asks for ads_management, catalogue, page or Instagram permissions, even though Meta’s server offers them.

Then, in the Shared with missions section, choose + Share in a mission, and pick the missions where Cora may read your Meta ads.

In a mission where you shared the connection, ask Cora in the dialogue, for example:

  • “Which Meta ad sets spent the most last week, and what did each return?”
  • “Is anything unusual in our Meta results this month?”
  • “How do our ad sets compare with similar advertisers?”

Cora finds your ad accounts first if she needs to know which one to use, then reads the results and answers with the figures and the dates they cover.

Only these kinds of tools, and all of them only read:

  • Your ad accounts and the Facebook pages they advertise with.
  • What is running and how it did: campaigns, ad sets and ads with their results, the field reference, and Meta’s opportunity score.
  • Meta’s insights: your business context, unusual changes, auction ranking, industry benchmarks and trends over time.
  • Why something is wrong and who changed what: ad errors, Meta’s help articles and the account’s activity log.
  • Creative: creatives and the ads that use them, images, videos, ad previews, and searches of Meta’s public Ad Library.
  • Measurement: datasets, their quality and statistics, custom conversions, and A/B tests and lift studies.

Cora’s own rule decides this, not Meta’s labels. Her list of Meta tools is a fixed list of names that only read. A tool that is not on the list is never switched on, never shared in a mission and never given to Cora, even if Meta adds one later. That means she cannot:

  • create, change, turn on or pause a campaign, ad set or ad, or change a budget;
  • create creatives or boost Instagram posts;
  • create, change, upload people to or delete custom audiences;
  • create or change catalogues, product feeds, pixels or tests.

Some of Meta’s tools only read but are not about ad results, so they are left out too: custom audiences (they describe people), catalogues and product feeds, pixel rules, and Instagram accounts and posts. If you need one of these, tell the product team; each is added on its own after a check.

Meta is still rolling tools out. Meta says it opens its MCP tools to ad accounts gradually. So your account may list fewer tools than the list above. After you connect, the card says how many tools are on.

Meta ends each sign-in after a few hours, and gives Cora no way to renew it. Meta’s own guide says a sign-in like this usually lasts one to two hours. When it ends, the card says Needs reconnect and “Access ended at mcp.facebook.com. Meta ends each sign-in after a few hours and gives no way to renew it.” Cora skips the connection until then. Choose Reconnect, sign in with Facebook again and approve. The same connection comes back, with the missions it was shared in.

So connect again just before you ask Cora for a Meta report. A longer sign-in is planned for later.

The card also says Needs reconnect, with “Your organisation changed its sign-in app for Meta Ads”, when an org admin changes or removes the App ID.

  • Meta’s page shows an error before you can approve. The app does not list Cora’s callback address exactly, or you have no role on the app. Ask your Meta admin to check step 1.
  • Cora says “The service did not accept your organisation’s sign-in app”. The App ID is wrong, or you have no role on the app. Ask an org admin to check the App ID in the Organisation setup section of Meta Ads’s page in Connections, and your Meta admin to check your role.
  • Cora keeps no Meta app secret. The org admin enters the App ID only. Sign-in uses a one-time code and a proof that only Cora’s own request can give (PKCE).
  • Your sign-in is kept in one place. It goes to the secrets store. Cora’s worker holds it for one step at a time. It never appears in the database, logs, audit entries or prompts.
  • Cora never sees your Facebook password. You sign in on Meta’s page.