Any MCP-compatible appRead live data
- Campaigns, ad sets and ads
- Spend, reach, frequency, CPM and link clicks
- Age, gender, region and hour of day
- Facebook against Instagram, by placement
Connect once, use it two ways
Connect Facebook Ads to Jepto once. What you build in Jepto and what you ask in Claude or ChatGPT read the same data, so the numbers match wherever you look.
Add the Jepto MCP server and ask about Facebook Ads in plain English, across all your brands. Included on every plan.
and any MCP-compatible appJepto runs a hosted Facebook Ads MCP server at mcp.jepto.com. Connect it once and Claude, ChatGPT, Cursor or any MCP-compatible app can query 36 Facebook Ads fields across every Meta ad account you manage, next to your other channels. There's nothing to install and no Meta developer app to set up. It reads your Facebook Ads data and never changes it.
Paste the URL into your AI assistant, or find Jepto in Claude's connector directory or ChatGPT's Plugins page. Sign in to Jepto once and every conversation can use your live Facebook Ads data.
Works with
OAuth sign-in. Each person sees only the brands their Jepto login can.
Your assistant shows a preview. Nothing saves until you confirm.
Nothing. The Jepto MCP reads your Facebook Ads data and never changes it.
Paste one into Claude or ChatGPT once Jepto is connected. Swap [brand] for one of yours.
“Which ads have a frequency above 4 this month, and how has their CTR moved since they launched?”
“Which hours of the day get the cheapest link clicks for [brand] over the last 30 days?”
“Compare amount spent, CPM and link clicks for Facebook and Instagram placements over the last 14 days.”
“Break down reach and cost per action by age and gender for the prospecting campaigns.”
“Put last month's Meta spend next to Google Ads spend and GA4 sessions from paid social.”
“Create a $3,000 monthly Meta budget for [brand] and email me if it's pacing over.”
Meta's own server is the better choice if you want an AI to edit Meta campaigns. Jepto is read-only on Meta, and wins when the question spans Meta and your other channels, or every brand you manage.
| Compared on | Jepto MCP | Meta's official Ads MCP | Community servers |
|---|---|---|---|
| Setup | Hosted. Paste one URL, or pick Jepto in the Claude or ChatGPT directory, then sign in. | Hosted. Sign in with Meta Business. | You install, host and update it, and supply your own API credentials. |
| Accounts | Every Facebook Ads account you've connected, across all your brands, in one connection. | Ad accounts your Meta login can reach. | Usually one login or token at a time. |
| Other channels | Ask across Facebook Ads and every other connected source in the same question. | Meta only. | One platform per server. You combine servers yourself. |
| Brand context | Reads each brand's details and knowledgebase, so answers reflect what the business sells and what it's aiming for. | None. | None. |
| Field guidance | Ships a Facebook Ads guide the AI reads first: which numbers add up, which don't, and what isn't available. | Meta's own tools. | Raw API fields. The AI works out what they mean. |
| Changes | Read-only in Facebook Ads. Budgets and KPI targets in Jepto can be set from chat, with a confirm step. | Read and write, including campaign changes. | Varies. Some write to your account with no confirm step. |
| Cost | Included on every Jepto plan, with no usage limits. | Free. | Free code. Your time to run and maintain it. |
Every Facebook Ads metric and dimension in the Jepto data model, with its definition. Each one works the same way in Reports, Data Chat and the Jepto MCP.
| How you connect | Sign in with Facebook. You need access to the Meta ad accounts. |
| Levels | Campaign, ad set, ad, platform, placement, age, gender, region, hour of day |
| Use it in | Reports, Data Chat, KPI forecasting, budget tracking, anomaly alerts and the Jepto MCP |
| AI assistants | Claude, ChatGPT, Cursor and any MCP client, at https://mcp.jepto.com |
| Changes from chat | None. The MCP reads your data and never changes it |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
ImpressionsfacebookAds.impressions | The number of times your ads were on screen, including when the same person saw your ad more than once. | Metric | number | Sum | — |
Link clicksfacebookAds.clicks | Clicks on links in your ads that go to destinations such as your website, app, or a Meta experience. | Metric | number | Sum | — |
Amount spentfacebookAds.spend | Total amount spent on your ads during the reporting period, in your account currency. | Metric | number | Sum | Currency |
ReachfacebookAds.reach | The number of people who saw your ads at least once. Reach is an estimated metric. | Metric | number | Maximum | — |
FrequencyfacebookAds.frequency | The average number of times each person saw your ad (impressions divided by reach). | Metric | number | Calculated: Impressions ÷ Reach | Number |
Unique link clicksfacebookAds.uniqueClicks | The number of people who performed at least one link click. Differs from link clicks when the same person clicks multiple times. | Metric | number | Maximum | — |
CTR (all)facebookAds.ctr | The percentage of impressions that received any click type (all clicks divided by impressions). | Metric | number | Calculated: Link clicks ÷ Impressions | Percentage |
Unique CTRfacebookAds.uniqueCtr | The percentage of people who saw your ad and clicked a link (unique link clicks divided by reach). | Metric | number | Calculated: Unique link clicks ÷ Reach | Percentage |
CPC (all)facebookAds.cpc | The average cost for each click of any type (amount spent divided by all clicks). | Metric | number | Calculated: Amount spent ÷ Link clicks | Currency |
CPMfacebookAds.cpm | The average cost per 1,000 impressions (amount spent divided by impressions, ×1,000). | Metric | number | Calculated: (Amount spent ÷ Impressions) × 1,000 | Currency |
Cost per purchasefacebookAds.cpp | The average cost for each purchase attributed to your ads. | Metric | number | Calculated: Amount spent ÷ Actions | Currency |
ActionsfacebookAds.actions | Counts of specific action types on your ads (for example purchases, leads, or other standard events), often used with action breakdowns. | Metric | number | Sum | — |
Action valuefacebookAds.actionValues | The total monetary value reported for actions on your ads, in your account currency. | Metric | number | Sum | Currency |
Cost per action typefacebookAds.costPerActionType | Average cost for each action of a given type when broken down by action type. | Metric | number | Average | Currency |
Website CTRfacebookAds.websiteCtr | The percentage of impressions that resulted in a link click to your website. | Metric | number | Calculated: Link clicks ÷ Impressions | Percentage |
Reach per spendfacebookAds.reachPerSpend | People reached per unit of currency spent (reach / spend). Distinct from cpp and other native cost metrics. | Metric | number | Calculated: Reach ÷ Amount spent | — |
Unique click share %facebookAds.uniqueClickSharePercent | Percentage of total clicks that came from unique users: unique clicks ÷ total clicks. | Metric | number | Calculated: (Unique link clicks ÷ Link clicks) × 100 | — |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
CampaignfacebookAds.campaignName | Name of the ad campaign. Shown in campaign reports and breakdowns. | Dimension | string | — | — |
Campaign IDfacebookAds.campaignId | Unique identifier for the ad campaign in Facebook Ads Manager. | Dimension | string | — | — |
Ad groupfacebookAds.adGroupName | Name of the ad group (adset). | Dimension | string | — | — |
Ad group IDfacebookAds.adGroupId | Unique identifier for the ad group (adset) in Facebook Ads Manager. | Dimension | string | — | — |
AdfacebookAds.adName | Name of the ad. Shown in ad-level reports and breakdowns. | Dimension | string | — | — |
Ad IDfacebookAds.adId | Unique identifier for the ad in Facebook Ads Manager. | Dimension | string | — | — |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
DatefacebookAds.date | Date when the ad metrics were recorded. | Dimension | string | — | — |
End datefacebookAds.dateStop | End date for the reporting period. | Dimension | string | — | — |
Hour of day (advertiser time zone)facebookAds.hourlyStatsAggregatedByAdvertiserTimeZone | Hour of the day the ad was served, aggregated in the advertiser's time zone. | Dimension | string | — | — |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
CountryfacebookAds.country | Country where people who saw your ads were located. | Dimension | string | — | — |
RegionfacebookAds.region | Region or state where people who saw your ads were located. | Dimension | string | — | — |
DMA regionfacebookAds.dma | Designated market area (US TV markets) for geographic breakdowns. Deprecated by Facebook; requests are routed to comscore_market. | Dimension | string | — | — |
Comscore marketfacebookAds.comscoreMarket | Comscore market for US geographic breakdowns (replaces deprecated dma). | Dimension | string | — | — |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
PlatformfacebookAds.publisherPlatform | Meta platform where the ad was shown (Facebook, Instagram, Audience Network, etc.). | Dimension | string | — | — |
Device platformfacebookAds.devicePlatform | Device class where the ad was shown (mobile, desktop, etc.). | Dimension | string | — | — |
Platform positionfacebookAds.platformPosition | Position where the ad was shown within the platform (e.g. feed, stories, right column). | Dimension | string | — | — |
Impression devicefacebookAds.impressionDevice | Device on which the ad impression was recorded (e.g. mobile, desktop). | Dimension | string | — | — |
| Field | Description | Kind | Type | Aggregation | Format |
|---|---|---|---|---|---|
AgefacebookAds.age | Age range of people who saw your ads (used with age breakdowns). | Dimension | string | — | — |
GenderfacebookAds.gender | Gender of people who saw your ads (used with gender breakdowns). | Dimension | string | — | — |
Reports, budgets, forecasts and alerts all use the same Facebook Ads fields listed above.
Describe the report you want and Jepto builds it from your Facebook Ads data, then writes an analysis of what changed and why.
Explore reportingTrack Facebook Ads spend against a budget for each account or group of campaigns, and see mid-month whether you're on course to overspend.
Explore budget trackingSet a target on any Facebook Ads metric and see where the month is likely to finish, while there's still time to act.
Explore KPI forecastingAdd an anomaly alert to the Facebook Ads metrics you care about, and Jepto tells you when one moves outside its normal range.
Explore anomaly detectionSign in with the Facebook account that has access to your Meta ad accounts.
In Jepto, add a Facebook Ads connection and sign in with a Facebook account that has access to the ad accounts.
Select the ad accounts you want to report on.
Your data is ready in Reports and Data Chat. Connect https://mcp.jepto.com to your AI assistant to ask about it from there too.
About Facebook Ads in Jepto and the Jepto MCP.
Yes. Jepto hosts an MCP server at https://mcp.jepto.com that gives Claude, ChatGPT, Cursor and other MCP-compatible apps access to your Facebook Ads data. There's nothing to install: you sign in to Jepto with OAuth, and the assistant can query every Facebook Ads field in the Jepto data model.
Yes. Meta opened a beta of its own Ads MCP server in April 2026, and it can read and change Meta campaigns. Jepto's server is read-only on Meta, and it lets one question cover Meta, Google, Microsoft and your analytics across every brand you manage.
Jepto includes Facebook Ads metrics such as Impressions, Link clicks, Amount spent, Reach, Frequency, Unique link clicks, CTR (all) and Unique CTR. You can break them down by dimensions for Campaign, ad set & ad, Date & time, Location, Device & placement and Segments. Every field, with its definition, is listed on this page.
No. Through the Jepto MCP, Facebook Ads data is read-only: the assistant can query it but can't change anything in Facebook Ads.
Yes. They're separate sources in Jepto, so you can report on each on its own, and the Platform dimension splits Facebook and Instagram delivery within either.
Yes. Ad name and ad ID are dimensions, so you can compare amount spent, CTR and results for each ad within a campaign or ad set.
Yes. When both are connected to the same brand, any report or chart can use fields from either source, and Data Chat and the Jepto MCP can answer questions that span the two. Cross-platform fields such as unified.spend also add Facebook Ads to totals across your other ad platforms.
No. You connect Facebook Ads to Jepto by signing in, and Jepto handles the API access. Your AI assistant then connects to Jepto at https://mcp.jepto.com.
Yes. Every Facebook Ads account connected to Jepto, across all your brands, is available through the one connection. What each person can see follows their Jepto login.
No. The Jepto MCP is included on every plan with no usage limits. Check that your AI assistant's plan lets you add connectors.
Related Articles
Start asking your data smarter questions today. Connect your first data source in minutes.
