Skip to content
Back to search

meta-ads-mcp

Meta Ads (Facebook/Instagram) MCP server for Claude, ChatGPT, Perplexity & Cursor — the Meta node of Pipeboard’s 5-platform family (+ Google, TikTok, Snap, Reddit). Hosted remote MCP, badged Meta Business Partner, free plan — no self-hosting required.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/pipeboard-co--meta-ads-mcp/badge.svg)](/listings/pipeboard-co--meta-ads-mcp)

HTML

<a href="/listings/pipeboard-co--meta-ads-mcp"><img src="/api/listings/pipeboard-co--meta-ads-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

The fastest and most reliable way to get started is to **[🚀 Get started with our Meta Ads Remote MCP](https://pipeboard.co)**. Our cloud service uses streamable HTTP transport for reliable, scalable access to your Meta Ads account. No technical setup required — just connect and start launching, updating, and analyzing campaigns with AI!

For Claude Pro/Max Users

1. Go to [claude.ai/settings/integrations](https://claude.ai/settings/integrations) (requires Claude Pro or Max) 2. Click "Add Integration" and enter: - **Name**: "Pipeboard Meta Ads" (or any name you prefer) - **Integration URL**: `https://meta-ads.mcp.pipeboard.co/` 3. Click "Connect" next to the integration and follow the prompts to: - Login to Pipeboard - Connect your Facebook Ads account

That's it! You can now ask Claude to analyze your Meta ad campaigns, get performance insights, and manage your advertising.

Advanced: Direct Token Authentication (Claude)

For direct token-based authentication without the interactive flow, use this URL format when adding the integration:

https://meta-ads.mcp.pipeboard.co/?token=YOUR_PIPEBOARD_TOKEN

Get your token at [pipeboard.co/api-tokens](https://pipeboard.co/api-tokens).

For Cursor Users

Add the following to your `~/.cursor/mcp.json`. Once you enable the remote MCP, click on "Needs login" to finish the login process.

{
  "mcpServers": {
    "meta-ads-remote": {
      "url": "https://meta-ads.mcp.pipeboard.co/"
    }
  }
}

Advanced: Direct Token Authentication (Cursor)

If you prefer to authenticate without the interactive login flow, you can include your Pipeboard API token directly in the URL:

{
  "mcpServers": {
    "meta-ads-remote": {
      "url": "https://meta-ads.mcp.pipeboard.co/?token=YOUR_PIPEBOARD_TOKEN"
    }
  }
}

Get your token at [pipeboard.co/api-tokens](https://pipeboard.co/api-tokens).

For Other MCP Clients

Use the Remote MCP URL: `https://meta-ads.mcp.pipeboard.co/`

**[📖 Get detailed setup instructions for your AI client here](https://pipeboard.co)**

Advanced: Direct Token Authentication (OpenClaw and other clients)

For MCP clients that support token-based authentication, you can append your Pipeboard API token to the URL:

https://meta-ads.mcp.pipeboard.co/?token=YOUR_PIPEBOARD_TOKEN

This bypasses the interactive login flow and authenticates immediately. Get your token at [pipeboard.co/api-tokens](https://pipeboard.co/api-tokens).

Other platforms

Meta Ads is one of five remote MCP servers in the family — see [The Pipeboard MCP Family](#the-pipeboard-mcp-family) for Google Ads, TikTok Ads, Snap Ads, and Reddit Ads, all set up the same way.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 543 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Meta Ads MCP
  2. A [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server that lets AI assistants — Claude, ChatGPT, Perplexity, Cursor, or any MCP client — run your Meta Ads end to end: launch campaigns, upload creatives, update budgets, and analyze performance through natural conversation across Facebook, Instagram, and every Meta ad surface. Available as a **hosted remote MCP** — no developer token, no self-hosting required.
  3. This is the **Meta Ads node** of the [Pipeboard](https://pipeboard.co) MCP family — five remote MCP servers (Meta, Google, TikTok, Snap, Reddit) plus a unified [Pipeboard CLI](https://github.com/pipeboard-co/pipeboard-cli), **230+ tools** in total, one auth, one safety model. If you are comparing single-platform MCPs, you are looking at one node of a network — see [The Pipeboard MCP Family](#the-pipeboard-mcp-family) below.
  4. > **Note:** This is an independent open-source project that uses Meta's public APIs. The hosted service behind it — [Pipeboard](https://pipeboard.co) — is a **badged Meta Business Partner** and an officially approved Meta app that manages **Meta, Google, TikTok, Snap & Reddit Ads** from one login (with a free plan) — so it is neither Meta-only nor something you have to self-host. Meta, Facebook, Instagram, and other Meta brand names are trademarks of their respective owners.
  5. [![Meta Ads MCP Server Demo](https://github.com/user-attachments/assets/3e605cee-d289-414b-814c-6299e7f3383e)](https://github.com/user-attachments/assets/3e605cee-d289-414b-814c-6299e7f3383e)
  6. [![MCP Badge](https://lobehub.com/badge/mcp/nictuku-meta-ads-mcp)](https://lobehub.com/mcp/nictuku-meta-ads-mcp)
  7. mcp-name: co.pipeboard/meta-ads-mcp
  8. ## Community & Support
  9. - [Discord](https://discord.gg/YzMwQ8zrjr). Join the community.
  10. - [Email Support](mailto:info@pipeboard.co). Email us for support.
  11. ## Table of Contents
  12. - [The Pipeboard MCP Family](#the-pipeboard-mcp-family)
  13. - [🚀 Getting started with Remote MCP (Recommended for Marketers)](#getting-started-with-remote-mcp-recommended)
  14. - [Pipeboard CLI (Alternative to MCP)](#pipeboard-cli-alternative-to-mcp)
  15. - [Local Installation (Technical Users Only)](#local-installation-technical-users-only)
  16. - [Features](#features)
  17. - [Configuration](#configuration)
  18. - [Available MCP Tools](#available-mcp-tools)
  19. - [Licensing](#licensing)
  20. - [Privacy and Security](#privacy-and-security)
  21. - [Testing](#testing)
  22. - [Troubleshooting](#troubleshooting)
  23. ## The Pipeboard MCP Family
  24. Pipeboard ships a remote [MCP server](https://modelcontextprotocol.io/) for every major ad platform — plus a single-binary [CLI](https://github.com/pipeboard-co/pipeboard-cli) that wraps all of them. **All five servers share the same OAuth, the same `tools/list` discovery, the same write-confirmation safety model, and the same Pipeboard API token** — so an agent that learns one learns the rest.
  25. ### Remote MCP servers
  26. | Platform | Remote MCP URL | Surface |
  27. |---|---|---|
  28. | **Meta Ads MCP** (Facebook + Instagram) | `https://meta-ads.mcp.pipeboard.co/` | **42 tools** — campaigns, ad sets, ads, creatives (incl. dynamic creative testing), image upload, insights, interest / behavior / demographic / geo targeting, page management |
  29. | **Google Ads MCP** | `https://google-ads.mcp.pipeboard.co/` | **59 tools** — campaigns, ad groups, responsive search ads, Performance Max, keywords, GAQL queries, extensions (sitelinks, callouts, structured snippets), audiences, asset uploads, generic mutate |
  30. | **TikTok Ads MCP** | `https://tiktok-ads.mcp.pipeboard.co/` | **59 tools** — campaigns, ad groups, ads, identities, image and video upload, audience and creative management, insights |
  31. | **Snap Ads MCP** | `https://snap-ads.mcp.pipeboard.co/` | **37 tools** — ad accounts, campaigns, ad squads, ads, creatives, media upload, insights |
  32. | **Reddit Ads MCP** | `https://reddit-ads.mcp.pipeboard.co/` | **33 tools** — accounts, campaigns, ad groups, ads, performance reports |
  33. **That is 230+ tools across five ad platforms behind one auth.** Plug any of these URLs into Claude, Cursor, ChatGPT, Perplexity, or any MCP-compatible client. Connect your ad accounts once at [pipeboard.co](https://pipeboard.co) and every client gets access.
  34. ### Pipeboard CLI — the same tools, in your shell
  35. [**Pipeboard CLI**](https://github.com/pipeboard-co/pipeboard-cli) is a single Go binary that exposes every MCP tool above as a typed shell command — built for AI coding agents (Claude Code, Cline, OpenClaw, Codex) and automation scripts that prefer subprocess calls over JSON-RPC:
  36. ```bash
  37. brew install pipeboard-co/tap/pipeboard
  38. export PIPEBOARD_API_TOKEN=<your-token>
  39. pipeboard meta-ads get-campaigns --account-id act_123
  40. pipeboard google-ads execute-gaql-query --customer-id 1234567890 --query "..."
  41. pipeboard tiktok-ads get-campaigns --advertiser-id 7605685552884596737
  42. ```
  43. Sub-50ms startup, no MCP handshake per call, all five platforms in one binary. Full docs in the [pipeboard-cli repo](https://github.com/pipeboard-co/pipeboard-cli).
  44. ### Why a family instead of one MCP per repo?
  45. - **One account, every platform** — auth once at [pipeboard.co](https://pipeboard.co); manage Meta + Google + TikTok + Snap + Reddit from the same agent session
  46. - **Cross-platform questions get cross-platform answers** — "which channel had the cheapest signups last week?" actually works
  47. - **Same safety contract everywhere** — writes are explicit, new campaigns start paused where the platform supports it, and confirmation prompts look identical across all five servers
  48. - **One token, one rate-limit ceiling, one place to revoke** — no juggling separate OAuth flows or per-vendor installs
  49. Single-platform MCP benchmarks miss the point. The value is the network, not the node.
  50. ### How Pipeboard compares
  51. If you are choosing between the ways to run Meta Ads from an AI assistant, here is the honest landscape:
  52. | | **Pipeboard** | **Meta's official MCP** | **Open-source / self-hosted servers** |
  53. |---|---|---|---|
  54. | **Platforms** | Meta + Google + TikTok + Snap + Reddit, one login | Meta only | Usually Meta only |
  55. | **Setup** | Hosted remote MCP — no developer token, ~2 minutes | Hosted by Meta (Meta only) | Self-host, manage your own tokens & upgrades |
  56. | **Trust** | Badged Meta Business Partner + approved Meta app | First-party (Meta) | Varies — audit the code yourself |
  57. | **Safety** | Explicit confirmation on every write; new campaigns start paused | Meta-defined | You build the guardrails |
  58. | **Price** | Free plan, then paid tiers | Free (open beta) | Free, but you run the infra |
  59. Meta's official connector is the safest **single-platform** option. Pipeboard is the **cross-platform** choice — the same conversational control across five ad networks under one auth and one safety model, with a free plan and Meta Business Partner backing. Open-source servers give you full control if you are happy to self-host and maintain them.
  60. ## Getting started with Remote MCP (Recommended)
  61. The fastest and most reliable way to get started is to **[🚀 Get started with our Meta Ads Remote MCP](https://pipeboard.co)**. Our cloud service uses streamable HTTP transport for reliable, scalable access to your Meta Ads account. No technical setup required — just connect and start launching, updating, and analyzing campaigns with AI!
  62. ### For Claude Pro/Max Users
  63. 1. Go to [claude.ai/settings/integrations](https://claude.ai/settings/integrations) (requires Claude Pro or Max)
  64. 2. Click "Add Integration" and enter:
  65. - **Name**: "Pipeboard Meta Ads" (or any name you prefer)
  66. - **Integration URL**: `https://meta-ads.mcp.pipeboard.co/`
  67. 3. Click "Connect" next to the integration and follow the prompts to:
  68. - Login to Pipeboard
  69. - Connect your Facebook Ads account
  70. That's it! You can now ask Claude to analyze your Meta ad campaigns, get performance insights, and manage your advertising.
  71. #### Advanced: Direct Token Authentication (Claude)
  72. For direct token-based authentication without the interactive flow, use this URL format when adding the integration:
  73. ```
  74. https://meta-ads.mcp.pipeboard.co/?token=YOUR_PIPEBOARD_TOKEN
  75. ```
  76. Get your token at [pipeboard.co/api-tokens](https://pipeboard.co/api-tokens).
  77. ### For Cursor Users
  78. Add the following to your `~/.cursor/mcp.json`. Once you enable the remote MCP, click on "Needs login" to finish the login process.
  79. ```json
  80. {
  81. "mcpServers": {
  82. "meta-ads-remote": {
  83. "url": "https://meta-ads.mcp.pipeboard.co/"
  84. }
  85. }
  86. }
  87. ```
  88. #### Advanced: Direct Token Authentication (Cursor)
  89. If you prefer to authenticate without the interactive login flow, you can include your Pipeboard API token directly in the URL:
  90. ```json
  91. {
  92. "mcpServers": {
  93. "meta-ads-remote": {
  94. "url": "https://meta-ads.mcp.pipeboard.co/?token=YOUR_PIPEBOARD_TOKEN"
  95. }
  96. }
  97. }
  98. ```
  99. Get your token at [pipeboard.co/api-tokens](https://pipeboard.co/api-tokens).
  100. ### For Other MCP Clients
  101. Use the Remote MCP URL: `https://meta-ads.mcp.pipeboard.co/`
  102. **[📖 Get detailed setup instructions for your AI client here](https://pipeboard.co)**
  103. #### Advanced: Direct Token Authentication (OpenClaw and other clients)
  104. For MCP clients that support token-based authentication, you can append your Pipeboard API token to the URL:
  105. ```
  106. https://meta-ads.mcp.pipeboard.co/?token=YOUR_PIPEBOARD_TOKEN
  107. ```
  108. This bypasses the interactive login flow and authenticates immediately. Get your token at [pipeboard.co/api-tokens](https://pipeboard.co/api-tokens).
  109. ### Other platforms
  110. Meta Ads is one of five remote MCP servers in the family — see [The Pipeboard MCP Family](#the-pipeboard-mcp-family) for Google Ads, TikTok Ads, Snap Ads, and Reddit Ads, all set up the same way.
  111. ## Pipeboard CLI (Alternative to MCP)
  112. If your agent prefers shell commands over JSON-RPC, the [Pipeboard CLI](https://github.com/pipeboard-co/pipeboard-cli) exposes every tool in the family as a typed subcommand — see [the family section above](#pipeboard-cli--the-same-tools-in-your-shell) for the quick install and the [pipeboard-cli repo](https://github.com/pipeboard-co/pipeboard-cli) for full docs.
  113. ## Local Installation (Advanced Technical Users Only)
  114. 🚀 **We strongly recommend using [Remote MCP](https://pipeboard.co) instead** - it's faster, more reliable, and requires no technical setup.
  115. Meta Ads MCP also supports a local streamable HTTP transport, allowing you to run it as a standalone HTTP API for web applications and custom integrations. See **[Streamable HTTP Setup Guide](STREAMABLE_HTTP_SETUP.md)** for complete instructions.
  116. ## Features
  117. - **Campaign Management**: Launch campaigns, ad sets, and ads, update budgets, pause and resume, and apply targeting changes — all from a conversation, with explicit confirmation on every write
  118. - **Creative Operations**: Upload images, build creatives, and update copy, headlines, descriptions, and CTAs without leaving your AI client
  119. - **Dynamic Creative Testing**: One API for both simple ads (single headline/description) and full A/B testing (multiple headlines/descriptions)
  120. - **AI-Powered Campaign Analysis**: Let your favorite LLM analyze performance and surface actionable insights
  121. - **Strategic Recommendations**: Receive data-backed suggestions for optimizing ad spend, targeting, and creative content
  122. - **Budget Optimization**: Get recommendations for reallocating budget to better-performing ad sets
  123. - **Creative Improvement**: Receive feedback on ad copy, imagery, and calls-to-action
  124. - **Automated Monitoring**: Ask any MCP-compatible LLM to track performance metrics and alert you about significant changes
  125. - **Cross-Platform Integration**: Works with Facebook, Instagram, and all Meta ad surfaces
  126. - **Universal LLM Support**: Compatible with any MCP client including Claude Desktop, Cursor, Cherry Studio, and more
  127. - **Partner-Backed, Not Just Open Source**: Built by [Pipeboard](https://pipeboard.co), a badged Meta Business Partner and officially approved Meta app — with a free plan and hosted remote MCP (no self-hosting required)
  128. - **Enhanced Search**: Generic search function includes page searching when queries mention "page" or "pages"
  129. - **Simple Authentication**: Easy setup with secure OAuth authentication
  130. - **Cross-Platform Support**: Works on Windows, macOS, and Linux
  131. ## Configuration
  132. ### Remote MCP (Recommended)
  133. **[✨ Get started with Remote MCP here](https://pipeboard.co)** - no technical setup required! Just connect your Facebook Ads account and start asking AI to analyze your campaigns.
  134. ### Local Installation (Advanced Technical Users)
  135. For advanced users who need to self-host, the package can be installed from source. Local installations require creating your own Meta Developer App. **We recommend using [Remote MCP](https://pipeboard.co) for a simpler experience.**
  136. ### Available MCP Tools
  137. 1. `mcp_meta_ads_get_ad_accounts`
  138. - Get ad accounts accessible by a user
  139. - Inputs:
  140. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  141. - `user_id`: Meta user ID or "me" for the current user
  142. - `limit`: Maximum number of accounts to return (default: 200)
  143. - Returns: List of accessible ad accounts with their details
  144. 2. `mcp_meta_ads_get_account_info`
  145. - Get detailed information about a specific ad account
  146. - Inputs:
  147. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  148. - `account_id`: Meta Ads account ID (format: act_XXXXXXXXX)
  149. - Returns: Detailed information about the specified account
  150. 3. `mcp_meta_ads_get_account_pages`
  151. - Get pages associated with a Meta Ads account
  152. - Inputs:
  153. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  154. - `account_id`: Meta Ads account ID (format: act_XXXXXXXXX) or "me" for the current user's pages
  155. - Returns: List of pages associated with the account, useful for ad creation and management
  156. 4. `mcp_meta_ads_get_campaigns`
  157. - Get campaigns for a Meta Ads account with optional filtering
  158. - Inputs:
  159. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  160. - `account_id`: Meta Ads account ID (format: act_XXXXXXXXX)
  161. - `limit`: Maximum number of campaigns to return (default: 10)
  162. - `status_filter`: Filter by status (empty for all, or 'ACTIVE', 'PAUSED', etc.)
  163. - Returns: List of campaigns matching the criteria
  164. 5. `mcp_meta_ads_get_campaign_details`
  165. - Get detailed information about a specific campaign
  166. - Inputs:
  167. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  168. - `campaign_id`: Meta Ads campaign ID
  169. - Returns: Detailed information about the specified campaign
  170. 6. `mcp_meta_ads_create_campaign`
  171. - Create a new campaign in a Meta Ads account
  172. - Inputs:
  173. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  174. - `account_id`: Meta Ads account ID (format: act_XXXXXXXXX)
  175. - `name`: Campaign name
  176. - `objective`: Campaign objective (ODAX, outcome-based). Must be one of:
  177. - `OUTCOME_AWARENESS`
  178. - `OUTCOME_TRAFFIC`
  179. - `OUTCOME_ENGAGEMENT`
  180. - `OUTCOME_LEADS`
  181. - `OUTCOME_SALES`
  182. - `OUTCOME_APP_PROMOTION`
  183. Note: Legacy objectives such as `BRAND_AWARENESS`, `LINK_CLICKS`, `CONVERSIONS`, `APP_INSTALLS`, etc. are no longer valid for new campaigns and will cause a 400 error. Use the outcome-based values above. Common mappings:
  184. - `BRAND_AWARENESS` → `OUTCOME_AWARENESS`
  185. - `REACH` → `OUTCOME_AWARENESS`
  186. - `LINK_CLICKS`, `TRAFFIC` → `OUTCOME_TRAFFIC`
  187. - `POST_ENGAGEMENT`, `PAGE_LIKES`, `EVENT_RESPONSES`, `VIDEO_VIEWS` → `OUTCOME_ENGAGEMENT`
  188. - `LEAD_GENERATION` → `OUTCOME_LEADS`
  189. - `CONVERSIONS`, `CATALOG_SALES`, `MESSAGES` (sales-focused flows) → `OUTCOME_SALES`
  190. - `APP_INSTALLS` → `OUTCOME_APP_PROMOTION`
  191. - `status`: Initial campaign status (default: PAUSED)
  192. - `special_ad_categories`: List of special ad categories if applicable
  193. - `daily_budget`: Daily budget in account currency (in cents)
  194. - `lifetime_budget`: Lifetime budget in account currency (in cents)
  195. - `bid_strategy`: Bid strategy. Must be one of: `LOWEST_COST_WITHOUT_CAP`, `LOWEST_COST_WITH_BID_CAP`, `COST_CAP`, `LOWEST_COST_WITH_MIN_ROAS`.
  196. - Returns: Confirmation with new campaign details
  197. - Example:
  198. ```json
  199. {
  200. "name": "2025 - Bedroom Furniture - Awareness",
  201. "account_id": "act_123456789012345",
  202. "objective": "OUTCOME_AWARENESS",
  203. "special_ad_categories": [],
  204. "status": "PAUSED",
  205. "buying_type": "AUCTION",
  206. "bid_strategy": "LOWEST_COST_WITHOUT_CAP",
  207. "daily_budget": 10000
  208. }
  209. ```
  210. 7. `mcp_meta_ads_get_adsets`
  211. - Get ad sets for a Meta Ads account with optional filtering by campaign
  212. - Inputs:
  213. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  214. - `account_id`: Meta Ads account ID (format: act_XXXXXXXXX)
  215. - `limit`: Maximum number of ad sets to return (default: 10)
  216. - `campaign_id`: Optional campaign ID to filter by
  217. - Returns: List of ad sets matching the criteria
  218. 8. `mcp_meta_ads_get_adset_details`
  219. - Get detailed information about a specific ad set
  220. - Inputs:
  221. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  222. - `adset_id`: Meta Ads ad set ID
  223. - Returns: Detailed information about the specified ad set
  224. 9. `mcp_meta_ads_create_adset`
  225. - Create a new ad set in a Meta Ads account
  226. - Inputs:
  227. - `account_id`: Meta Ads account ID (format: act_XXXXXXXXX)
  228. - `campaign_id`: Meta Ads campaign ID this ad set belongs to
  229. - `name`: Ad set name
  230. - `status`: Initial ad set status (default: PAUSED)
  231. - `daily_budget`: Daily budget in account currency (in cents) as a string
  232. - `lifetime_budget`: Lifetime budget in account currency (in cents) as a string
  233. - `targeting`: Targeting specifications (e.g., age, location, interests)
  234. - `optimization_goal`: Conversion optimization goal (e.g., 'LINK_CLICKS')
  235. - `billing_event`: How you're charged (e.g., 'IMPRESSIONS')
  236. - `bid_amount`: Bid amount in cents. Required for LOWEST_COST_WITH_BID_CAP, COST_CAP, TARGET_COST.
  237. - `bid_strategy`: Bid strategy (e.g., 'LOWEST_COST_WITHOUT_CAP', 'LOWEST_COST_WITH_MIN_ROAS')
  238. - `bid_constraints`: Bid constraints dict. Required for LOWEST_COST_WITH_MIN_ROAS (e.g., `{"roas_average_floor": 20000}`)
  239. - `start_time`, `end_time`: Optional start/end times (ISO 8601)
  240. - `access_token` (optional): Meta API access token
  241. - Returns: Confirmation with new ad set details
  242. 10. `mcp_meta_ads_get_ads`
  243. - Get ads for a Meta Ads account with optional filtering
  244. - Inputs:
  245. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  246. - `account_id`: Meta Ads account ID (format: act_XXXXXXXXX)
  247. - `limit`: Maximum number of ads to return (default: 10)
  248. - `campaign_id`: Optional campaign ID to filter by
  249. - `adset_id`: Optional ad set ID to filter by
  250. - Returns: List of ads matching the criteria
  251. 11. `mcp_meta_ads_create_ad`
  252. - Create a new ad with an existing creative
  253. - Inputs:
  254. - `account_id`: Meta Ads account ID (format: act_XXXXXXXXX)
  255. - `name`: Ad name
  256. - `adset_id`: Ad set ID where this ad will be placed
  257. - `creative_id`: ID of an existing creative to use
  258. - `status`: Initial ad status (default: PAUSED)
  259. - `bid_amount`: Optional bid amount (in cents)
  260. - `tracking_specs`: Optional tracking specifications
  261. - `access_token` (optional): Meta API access token
  262. - Returns: Confirmation with new ad details
  263. 12. `mcp_meta_ads_get_ad_details`
  264. - Get detailed information about a specific ad
  265. - Inputs:
  266. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  267. - `ad_id`: Meta Ads ad ID
  268. - Returns: Detailed information about the specified ad
  269. 13. `mcp_meta_ads_get_ad_creatives`
  270. - Get creative details for a specific ad
  271. - Inputs:
  272. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  273. - `ad_id`: Meta Ads ad ID
  274. - Returns: Creative details including text, images, and URLs
  275. 14. `mcp_meta_ads_create_ad_creative`
  276. - Create a new ad creative using an uploaded image hash
  277. - Inputs:
  278. - `account_id`: Meta Ads account ID (format: act_XXXXXXXXX)
  279. - `name`: Creative name
  280. - `image_hash`: Hash of the uploaded image
  281. - `page_id`: Facebook Page ID for the ad
  282. - `link_url`: Destination URL
  283. - `message`: Ad copy/text
  284. - `headline`: Single headline for simple ads (cannot be used with headlines)
  285. - `headlines`: List of headlines for dynamic creative testing (cannot be used with headline)
  286. - `description`: Single description for simple ads (cannot be used with descriptions)
  287. - `descriptions`: List of descriptions for dynamic creative testing (cannot be used with description)
  288. - `dynamic_creative_spec`: Dynamic creative optimization settings
  289. - `call_to_action_type`: CTA button type (e.g., 'LEARN_MORE')
  290. - `instagram_actor_id`: Optional Instagram account ID
  291. - `access_token` (optional): Meta API access token
  292. - Returns: Confirmation with new creative details
  293. 15. `mcp_meta_ads_update_ad_creative`
  294. - Update an existing ad creative with new content or settings
  295. - Inputs:
  296. - `creative_id`: Meta Ads creative ID to update
  297. - `name`: New creative name
  298. - `message`: New ad copy/text
  299. - `headline`: Single headline for simple ads (cannot be used with headlines)
  300. - `headlines`: New list of headlines for dynamic creative testing (cannot be used with headline)
  301. - `description`: Single description for simple ads (cannot be used with descriptions)
  302. - `descriptions`: New list of descriptions for dynamic creative testing (cannot be used with description)
  303. - `dynamic_creative_spec`: New dynamic creative optimization settings
  304. - `call_to_action_type`: New call to action button type
  305. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  306. - Returns: Confirmation with updated creative details
  307. 16. `mcp_meta_ads_upload_ad_image`
  308. - Upload an image to use in Meta Ads creatives
  309. - Inputs:
  310. - `account_id`: Meta Ads account ID (format: act_XXXXXXXXX)
  311. - `image_path`: Path to the image file to upload
  312. - `name`: Optional name for the image
  313. - `access_token` (optional): Meta API access token
  314. - Returns: JSON response with image details including hash
  315. 17. `mcp_meta_ads_get_ad_image`
  316. - Get, download, and visualize a Meta ad image in one step
  317. - Inputs:
  318. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  319. - `ad_id`: Meta Ads ad ID
  320. - Returns: The ad image ready for direct visual analysis
  321. 18. `mcp_meta_ads_update_ad`
  322. - Update an ad with new settings
  323. - Inputs:
  324. - `ad_id`: Meta Ads ad ID
  325. - `status`: Update ad status (ACTIVE, PAUSED, etc.)
  326. - `bid_amount`: Bid amount in account currency (in cents for USD)
  327. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  328. - Returns: Confirmation with updated ad details and a confirmation link
  329. 19. `mcp_meta_ads_update_adset`
  330. - Update an ad set with new settings including frequency caps
  331. - Inputs:
  332. - `adset_id`: Meta Ads ad set ID
  333. - `frequency_control_specs`: List of frequency control specifications
  334. - `bid_strategy`: Bid strategy (e.g., 'LOWEST_COST_WITH_BID_CAP', 'LOWEST_COST_WITH_MIN_ROAS')
  335. - `bid_amount`: Bid amount in cents. Required for LOWEST_COST_WITH_BID_CAP, COST_CAP, TARGET_COST.
  336. - `bid_constraints`: Bid constraints dict. Required for LOWEST_COST_WITH_MIN_ROAS (e.g., `{"roas_average_floor": 20000}`)
  337. - `status`: Update ad set status (ACTIVE, PAUSED, etc.)
  338. - `targeting`: Targeting specifications including targeting_automation
  339. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  340. - Returns: Confirmation with updated ad set details and a confirmation link
  341. 20. `mcp_meta_ads_get_insights`
  342. - Get performance insights for a campaign, ad set, ad or account
  343. - Inputs:
  344. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  345. - `object_id`: ID of the campaign, ad set, ad or account
  346. - `time_range`: Time range for insights (default: maximum)
  347. - `breakdown`: Optional breakdown dimension (e.g., age, gender, country)
  348. - `level`: Level of aggregation (ad, adset, campaign, account)
  349. - `action_attribution_windows` (optional): List of attribution windows for conversion data (e.g., ["1d_click", "1d_view", "7d_click", "7d_view"]). When specified, actions and cost_per_action_type include additional fields for each window. The 'value' field always shows 7d_click attribution.
  350. - Returns: Performance metrics for the specified object
  351. 21. `mcp_meta_ads_get_login_link`
  352. - Get a clickable login link for Meta Ads authentication
  353. - Inputs:
  354. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  355. - Returns: A clickable resource link for Meta authentication
  356. 22. `mcp_meta_ads_create_budget_schedule`
  357. - Create a budget schedule for a Meta Ads campaign
  358. - Inputs:
  359. - `campaign_id`: Meta Ads campaign ID
  360. - `budget_value`: Amount of budget increase
  361. - `budget_value_type`: Type of budget value ("ABSOLUTE" or "MULTIPLIER")
  362. - `time_start`: Unix timestamp for when the high demand period should start
  363. - `time_end`: Unix timestamp for when the high demand period should end
  364. - `access_token` (optional): Meta API access token
  365. - Returns: JSON string with the ID of the created budget schedule or an error message
  366. 23. `mcp_meta_ads_search_interests`
  367. - Search for interest targeting options by keyword
  368. - Inputs:
  369. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  370. - `query`: Search term for interests (e.g., "baseball", "cooking", "travel")
  371. - `limit`: Maximum number of results to return (default: 25)
  372. - Returns: Interest data with id, name, audience_size, and path fields
  373. 24. `mcp_meta_ads_get_interest_suggestions`
  374. - Get interest suggestions based on existing interests
  375. - Inputs:
  376. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  377. - `interest_list`: List of interest names to get suggestions for (e.g., ["Basketball", "Soccer"])
  378. - `limit`: Maximum number of suggestions to return (default: 25)
  379. - Returns: Suggested interests with id, name, audience_size, and description fields
  380. 25. `mcp_meta_ads_validate_interests`
  381. - Validate interest names or IDs for targeting
  382. - Inputs:
  383. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  384. - `interest_list`: List of interest names to validate (e.g., ["Japan", "Basketball"])
  385. - `interest_fbid_list`: List of interest IDs to validate (e.g., ["6003700426513"])
  386. - Returns: Validation results showing valid status and audience_size for each interest
  387. 26. `mcp_meta_ads_search_behaviors`
  388. - Get all available behavior targeting options
  389. - Inputs:
  390. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  391. - `limit`: Maximum number of results to return (default: 50)
  392. - Returns: Behavior targeting options with id, name, audience_size bounds, path, and description
  393. 27. `mcp_meta_ads_search_demographics`
  394. - Get demographic targeting options
  395. - Inputs:
  396. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  397. - `demographic_class`: Type of demographics ('demographics', 'life_events', 'industries', 'income', 'family_statuses', 'user_device', 'user_os')
  398. - `limit`: Maximum number of results to return (default: 50)
  399. - Returns: Demographic targeting options with id, name, audience_size bounds, path, and description
  400. 28. `mcp_meta_ads_search_geo_locations`
  401. - Search for geographic targeting locations
  402. - Inputs:
  403. - `access_token` (optional): Meta API access token (will use cached token if not provided)
  404. - `query`: Search term for locations (e.g., "New York", "California", "Japan")
  405. - `location_types`: Types of locations to search (['country', 'region', 'city', 'zip', 'geo_market', 'electoral_district'])
  406. - `limit`: Maximum number of results to return (default: 25)
  407. - Returns: Location data with key, name, type, and geographic hierarchy information
  408. ## Licensing
  409. Meta Ads MCP is licensed under the [Business Source License 1.1](LICENSE), which means:
  410. - ✅ **Free to use** for individual and business purposes
  411. - ✅ **Modify and customize** as needed
  412. - ✅ **Redistribute** to others
  413. - ✅ **Becomes fully open source** (Apache 2.0) on January 1, 2029
  414. The only restriction is that you cannot offer this as a competing hosted service. For questions about commercial licensing, please contact us.
  415. ## Privacy and Security
  416. Meta Ads MCP follows security best practices with secure token management and automatic authentication handling.
  417. - **Remote MCP**: All authentication is handled securely in the cloud - no local token storage required
  418. - **Local Installation**: Tokens are cached securely on your local machine
  419. ## Testing
  420. ### Basic Testing
  421. Test your Meta Ads MCP connection with any MCP client:
  422. 1. **Verify Account Access**: Ask your LLM to use `mcp_meta_ads_get_ad_accounts`
  423. 2. **Check Account Details**: Use `mcp_meta_ads_get_account_info` with your account ID
  424. 3. **List Campaigns**: Try `mcp_meta_ads_get_campaigns` to see your ad campaigns
  425. For detailed local installation testing, see the source repository.
  426. ## Troubleshooting
  427. ### 💡 Quick Fix: Skip the Technical Setup!
  428. The easiest way to avoid any setup issues is to **[🎯 use our Remote MCP instead](https://pipeboard.co)**. No downloads, no configuration - just connect your ads account and start getting AI insights on your campaigns immediately!
  429. ### Local Installation Issues
  430. For local installation issues, refer to the source repository. **For the easiest experience, we recommend using [Remote MCP](https://pipeboard.co) instead.**

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.