Log inSubmit server
Meta Ads logo

Meta Ads

Connects Meta ad accounts to MCP clients for campaign analysis, asset discovery, and optional preview-first changes.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Meta Ads

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "meta-ads": {
      "command": "npx",
      "args": [
        "-y",
        "@getmcpads/meta-ads-mcp-server"
      ],
      "env": {
        "META_ACCESS_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 41 tools correctly (5d ago).

Overview

The Meta Ads MCP server connects MCP clients to Meta ad accounts through the Graph API. It provides read tools for campaigns, ad sets, ads, insights, creatives, audiences, business assets, catalogs, Pages, Instagram accounts, activity, and studies. Optional write tools can manage selected campaign settings, but they are disabled by default and preview changes before applying them. Reach for it when an agent needs account-level Meta Ads analysis or controlled campaign operations from a local stdio MCP setup.

Use cases

  • Compare campaign and ad-set performance
  • Inspect delivery problems and account diagnostics
  • Discover Pages, Instagram accounts, pixels, and catalogs
  • Validate insight metric and breakdown combinations
  • Preview controlled campaign changes

Key features

  • Meta campaign, ad-set, ad, and insight reads
  • Business asset, audience, pixel, and catalog discovery
  • Metric and breakdown compatibility validation
  • Creative, delivery, activity, and experiment analysis
  • Optional preview-first write tools
  • Forward-compatible Graph API reads

Tools41

What Meta Ads lets your agent do. Expand a tool for its parameters.

Verified live~11.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

5/6 checks healthy over the last 41d

What it can do

From the 41 tools this server returned when we ran it; 41 declare their own safety hints.

Handles credentials · 4Makes network requests · 41Read-only tools · 41
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age48 days
Maintainers1

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3h ago via OSV.dev · @getmcpads/meta-ads-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads953Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed41Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Meta Ads works

What the Meta Ads MCP server does

The Meta Ads MCP server exposes Meta advertising and related Business assets through MCP tools. Read operations cover ad accounts, campaigns, ad sets, ads, performance insights, creatives, audiences, pixels, catalogs, Pages, Instagram accounts, activity logs, delivery diagnostics, brand-safety signals, and A/B or conversion lift studies.

The repository release also includes optional write tools for actions such as changing status, budgets, schedules, names, and creating campaigns. Writes are not registered unless explicitly enabled, and each enabled write returns a preview before making a change. The hosted product and its MCP Apps interface are separate from this standalone native API tool release.

How it works

The Meta Ads MCP server runs as a local Node.js process and communicates with an MCP client over stdio. Requests use the configured Meta access token and go directly to the platform. The server can list accessible ad accounts, inspect account and business assets, retrieve hierarchical campaign structure, and query reporting data.

Insights queries can be checked with meta_validate_query before execution. The server contains compatibility information for metrics and breakdowns, allowing requests that cannot be sent as one valid query to be split into valid calls and combined. Additional resources provide metric, breakdown, compatibility, and workflow reference data. Forward-compatible read tools can access Graph fields or responses not yet modeled by dedicated tools.

Setup and configuration

Use Node.js 22.12 or newer. From the source release, clone the repository, install dependencies with npm ci, build with npm run build, and configure the client to run the resulting dist/cli.js. A source-based setup can also use npm install && npm run build, followed by npm start.

Set META_ACCESS_TOKEN to a Meta access token with ads_read; this permission is needed for read-only campaign and insight access. Optional permissions include ads_management for writes, business_management for Business Manager discovery, Page permissions for Page content, instagram_basic for linked Instagram accounts, and catalog_management for catalog reads.

Set META_ENABLE_WRITES=1 to register the write tools. META_API_VERSION defaults to v26.0 and can pin another Graph API version, while LOG_LEVEL accepts debug, info, warn, or error. Run npm run doctor to check the local setup.

Tools and capabilities

The Meta Ads MCP server includes capabilities for:

  • Listing accessible ad accounts and reading account details.
  • Browsing campaigns, ad sets, ads, campaign hierarchy, and named entities.
  • Querying performance insights across supported metrics and breakdowns.
  • Inspecting creative text, media, links, calls to action, carousel components, and video URLs.
  • Reading custom, saved, and lookalike audiences, pixels, datasets, catalogs, and product items.
  • Discovering Pages, linked Instagram accounts, Page posts, and organic content enrichment where permissions allow.
  • Reviewing delivery diagnostics, ad activity, brand-safety controls, and experiment results.
  • Reading arbitrary flat fields from a Meta Graph node and using raw forward-compatible reads.
  • Previewing optional campaign changes before they are applied.

Limitations and notes

Access depends on the token, assigned assets, and granted permissions. The health-check tool reports token metadata, accessible accounts, and missing read scopes without exposing the token. Page, Instagram, catalog, Business Manager, and other asset results may be incomplete when their corresponding permissions are unavailable.

The repository’s v2.0.0 release requires Node.js 22.12 or newer and drops Node.js 18 and 20 support. Write tools remain opt-in and require explicit confirmation through the preview flow. The README distinguishes this local release from the separately managed hosted connection, including supported ChatGPT setups.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Meta Ads

Meta Ads is an MCP server that connects MCP clients to Meta ad accounts through the Graph API. Its main tools read campaigns, ad sets, ads, insights, creatives, audiences, business assets, catalogs, Pages, Instagram accounts, and studies, with optional preview-first tools for selected campaign changes.

Install it by cloning the v2.0.0 source release, running `npm ci` and `npm run build`, then configuring your MCP client to run the built Node.js entry point.

The server needs `ads_read` for read-only campaign and reporting access. Add `ads_management` only for writes; `business_management`, Page permissions, `instagram_basic`, and `catalog_management` are optional for their related asset types. Results depend on the assets assigned to the token.

Enable them by setting `META_ENABLE_WRITES=1` before starting the server. Writes are disabled by default, and each enabled write returns a preview without applying the change until it is explicitly confirmed. The token also needs `ads_management` for write access.

Yes, Meta Ads works with Cursor through a project `.cursor/mcp.json` configuration. Provide the server command and `META_ACCESS_TOKEN` in the MCP configuration, then use the local stdio connection from Cursor.

Related MCP servers

All in Social Media All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMeta Ads AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/meta-ads?style=directory)](https://allmcps.com/mcp/meta-ads)
HTML Embed
<a href="https://allmcps.com/mcp/meta-ads"><img src="https://allmcps.com/api/badge/meta-ads?style=directory" alt="Meta Ads on AllMCPs" /></a>