Skip to main content

Meta Ads MCP Server

The Meta Ads MCP server gives AI agents read-only access to Facebook and Instagram advertising data — ad accounts, campaigns, and performance insights — through standard MCP tool calls.

Read-only, by design

This is a deliberate first pass (#6860): only reporting tools are implemented. Mutating tools (create/update campaigns, ad sets, ads, creatives) spend real money and are intentionally out of scope for the hosted server.

Installation​

Use AINative's hosted remote MCP — no local process, no credential handling on your side:

.mcp.json
{
"mcpServers": {
"meta-ads": {
"url": "https://mcp.ainative.studio/meta-ads",
"headers": {
"Authorization": "Bearer your-api-key"
}
}
}
}

Credentials for the underlying Meta account are configured centrally on the AINative side — you authenticate to AINative, not to Meta.

Tools (3)​

  • get_ad_accounts — List Meta ad accounts accessible to the configured access token (limit)
  • get_campaigns — List campaigns in a Meta ad account (account_id, limit, status_filter)
  • get_insights — Get read-only performance insights (impressions, clicks, spend, etc.) at the account, campaign, ad set, or ad level (object_id, level, date_preset, fields)

Example usage​

User: How did our campaigns perform over the last 30 days?

Agent:
1. get_ad_accounts() → act_123456789
2. get_campaigns("act_123456789") → 4 active campaigns
3. get_insights("act_123456789", level="campaign", date_preset="last_30d")
4. → spend, impressions, CPC per campaign