mcpdirectory.dev
9,129 servers · updated 23 Sept

Meta Ads MCP server

community Active last commit 22 d
{
  "mcpServers": {
    "getmcpads-meta-ads": {
      "command": "npx",
      "args": [
        "-y",
        "@getmcpads/meta-ads-mcp-server@latest"
      ],
      "env": {
        "META_ACCESS_TOKEN": "<meta_access_token>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @getmcpads/meta-ads-mcp-serverversion 1.0.2

What it does

An MCP server that connects to Meta's Ads Marketing API, giving Claude and other AI clients access to read Facebook and Instagram advertising data and optionally make changes. You run it locally, keeping your access token on your machine with no third-party proxying.

  • Analyze campaign performance across 190 metrics with automatic handling of incompatible metric/breakdown combinations that would normally fail.
  • Preview and apply changes to ad campaigns—adjusting status, budgets, schedules, or creating new campaigns—with a confirmation step before any write executes.
  • Query ads data by 56 breakdowns and 90 dimensions, checking compatibility before making API calls to avoid rejected requests.

Tools this server exposes

ToolDoes
meta_get_node_fieldsReach Graph API fields not yet modeled by the server for forward compatibility.
meta_list_edge_rawRetrieve raw edge data from the Graph API without schema modeling.
meta_get_insights_rawFetch raw insights data for forward compatibility with unmapped Graph fields.
meta_validate_queryCheck if a metric and breakdown combination is valid before making an API call.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.