Meta Ads

Ad spend is the cost line a revenue team asks about most and sees least in the tools where pipeline lives. The Tulina connector lets an agent read Meta's numbers next to the CRM and the inbox, on a schedule, without anyone exporting a report. It reads only. Nothing is created, edited, paused or spent.

Does Meta Ads have an MCP?

Yes. Meta hosts its own ads MCP server at https://mcp.facebook.com/ads. As Meta's developer documentation reads on 1 November 2026, it covers reporting, creating and editing campaigns, ad sets and ads, catalogues, signal health, A/B tests, conversion lift studies and the activity log. It signs in with OAuth, a user access token or a system user access token, and only Employee-role system users are accepted. Tulina's Meta Ads connector is a second route to the same ad accounts, built for reading performance.

What is MCP in Facebook ads?

MCP, the Model Context Protocol, is the standard that lets an AI assistant call tools in another system. For Facebook and Instagram ads it means a chat can ask for last week's spend instead of someone opening Ads Manager. Meta's server exposes tools in seven categories. Tulina's connector exposes three, all of them for reading: accounts, objects and insights.

How do you connect Meta Ads to Claude and ChatGPT?

Through Tulina's own MCP server, in three steps:

1. In Tulina, open the Meta Ads card and choose Authorize oto on Facebook. Facebook asks which business and which ad accounts to share. Only those are visible to Tulina, and the access is read-only (ads_read and business_management).
2. To add an ad account later, reconnect and tick it.
3. Add https://mcp.tulina.ai/mcp to Claude or ChatGPT and sign in with your Tulina account. The MCP page has the same link.

Meta's ads MCP server and Tulina's Meta Ads connector

When the job is to build or change campaigns, Meta's own server is the right route. Tulina earns its place when ad spend should sit beside HubSpot deals or land in Slack every Monday.

What you can ask it

"Which campaigns spent the most in the last 30 days, and what did each cost per conversion?" The agent lists the ad accounts, pulls campaign-level insights for the period sorted by spend, and returns spend with the cost per action Meta reports.

"Break last week's spend by age and gender for the retargeting campaign." The agent finds the campaign among the account's campaigns, then asks for insights with an age and gender breakdown and a daily increment.

"Every Monday, post spend and clicks for each active campaign to Slack." The agent browses campaigns with an active status filter, reads their insights for the previous week and writes one message per account.

What runs on its own: any of these can be scheduled. Spend can also be written into a Google Sheet each week, so the finance side reads the same figures.

What the Meta Ads connector can't do

• It cannot create, edit, pause or spend anything. Meta's own server does that.
• Amounts are in each account's currency, and the connector does not convert between currencies.
• Figures are Meta's, with Meta's attribution: 7-day click and 1-day view by default, changeable per request. Reach is deduplicated and cannot be added up across days or campaigns.
• Recent days can still move for up to 28 days as late conversions arrive.
• Until Tulina's Meta app passes Meta's review it runs with standard access, which limits the number of calls. A large report can hit the limit; waiting a few minutes and retrying works.
• It reads only the ad accounts you ticked in the authorization.