Meta Ads MCP

What mikusnuz/meta-ads-mcp does

mikusnuz/meta-ads-mcp exposes Meta Marketing API operations through MCP tools. The repository describes 134 tools covering Facebook and Instagram advertising, including campaign hierarchies, creatives, media assets, audiences, targeting, reporting, catalogs, and automated rules.

Campaign tools can list, inspect, create, update, copy, and delete campaigns, ad sets, and ads. Creation tools support common campaign-building sequences: create a campaign, add an ad set with targeting and budget, create a creative, and create an ad. New campaigns, ad sets, and ads default to paused status. The server also provides lead retrieval, ad previews, delivery estimates, and human-readable ad set targeting descriptions.

The broader toolset supports custom and lookalike audiences, audience health checks, targeting searches, location searches, reach estimates, image and video uploads, account and object-level insights, asynchronous reports, ad library searches, experiments, catalogs, feeds, and automated rules.

How it works

An MCP-compatible host starts the package with npx, and the server sends requests to the Meta Marketing API using the configured credentials. Agents can combine read and write tools into workflows, such as finding campaigns with weak performance and then pausing them, or creating a full funnel from campaign through ad.

Insight tools accept date ranges and can query account, campaign, ad set, or ad performance. Large reporting jobs use an asynchronous flow: create the report, poll its status, and retrieve the completed results. Audience workflows can create an audience, add users, and then create a lookalike audience. The MCP server does not automatically make write operations safe or reversible; deletion and audience creation require particular care.

Setup and configuration

mikusnuz/meta-ads-mcp requires Node.js 20 or later. Configure the MCP host to run:

{
  "mcpServers": {
    "meta-ads": {
      "command": "npx",
      "args": ["-y", "@mikusnuz/meta-ads-mcp"],
      "env": {
        "META_ADS_ACCESS_TOKEN": "your-access-token",
        "META_AD_ACCOUNT_ID": "123456789"
      }
    }
  }
}

META_ADS_ACCESS_TOKEN and META_AD_ACCOUNT_ID are required. The account ID is numeric and should not include the act_ prefix. META_APP_ID and META_APP_SECRET support token exchange, extension, and debugging. META_BUSINESS_ID is used by business tools, while META_PIXEL_ID is used by conversion tools.

Tools and capabilities

The mikusnuz/meta-ads-mcp MCP server includes tools for:

• Campaign, ad set, ad, and creative lifecycle management
• Image, video, canvas, and other media asset operations
• Custom, saved, and lookalike audience management
• Targeting, location, reach, and delivery estimates
• Account, campaign, ad set, and ad insights
• Asynchronous report creation and result retrieval
• Experiments, conversion events, catalogs, product feeds, and automated rules
• Facebook Ad Library searches and ad previews

Recent capabilities include ad set validation without mutation through validate_only, bid and scheduling fields, rule-based custom audiences, and creative destination settings for Shops. EU-targeted ads may require both DSA beneficiary and payer values or corresponding account defaults.

Limitations and notes

Meta permissions and account configuration still govern what the tools can access or change. Lead retrieval requires leads_retrieval permission. Some business and conversion operations need the optional business or pixel identifiers. Deleting campaigns, ad sets, ads, creatives, media, or audiences can be irreversible.

The repository targets Meta Marketing API v26.0. In that version, several delivery-estimate fields are no longer returned, including daily_outcomes_curve, budget_guardrail, and estimate_dau. Poll and fetch asynchronous reports rather than expecting large insight queries to complete immediately. Detailed insight breakdowns may require Ads Manager opt-in, so an empty response does not necessarily indicate zero performance.