Meta Ads MCP vs NotFair GoogleAds

A side-by-side look at the Meta Ads MCP and NotFair GoogleAds MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Meta Ads MCP logoMeta Ads MCPMarketing · Local subprocess (stdio)MCP server for Meta Marketing API v25.0 — 123 tools for Facebook & Instagram ad campaigns, audiences, creatives, insights, catalogs, and automated rules.68GreatAuth: api key requiredNotFair GoogleAds logoNotFair GoogleAdsMarketing · Remote HTTP/SSEHosted Google Ads MCP with OAuth, 117 tools, MCC routing, image assets, and approval-gated writes.49FairAuth: oauth 2.0

Verdict: choose Meta Ads MCP for marketing work as a local process; choose NotFair GoogleAds for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Meta Ads MCP logoChoose Meta Ads MCP when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: META_ADS_ACCESS_TOKEN, META_AD_ACCOUNT_ID.
  • You want tools like list_campaigns, get_campaign, create_campaign.
Explore Meta Ads MCP

NotFair GoogleAds logoChoose NotFair GoogleAds when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore NotFair GoogleAds

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMeta Ads MCP logoMeta Ads MCPNotFair GoogleAds logoNotFair GoogleAds
CategoryMarketingMarketing
Quality signal68/100 · Great49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthAPI key requiredOAuth 2.0
PricingBYOK (pay the provider)Not declared
Required env varsMETA_ADS_ACCESS_TOKENMETA_AD_ACCOUNT_IDNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars913,970
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools134Not listed

Tools & capabilities

Meta Ads MCP tools 134

  • list_campaignsList campaigns in the ad account. Supports filtering by status and objective. Returns paginated results.
  • get_campaignGet details of a specific campaign by ID.
  • create_campaignCreate a new ad campaign. Defaults to PAUSED status. Requires name and objective. Budget can be set at campaign or ad set level.
  • update_campaignUpdate an existing campaign. Only provided fields will be modified.
  • delete_campaignDelete a campaign. This action is irreversible.
  • copy_campaignCopy an existing campaign. Creates a duplicate with optional name override. Copies structure including ad sets and ads.
  • get_campaign_adsetsGet all ad sets belonging to a specific campaign.
  • get_campaign_adsGet all ads belonging to a specific campaign.
  • get_campaign_leadsGet leads generated by a specific campaign. Requires leads_retrieval permission.
  • list_adsetsList ad sets in the ad account. Optionally filter by campaign or status.
  • get_adsetGet details of a specific ad set by ID.
  • create_adsetCreate a new ad set. Requires name, campaign_id, budget, optimization_goal, billing_event, and targeting. Defaults to PAUSED status.
  • +122 more on the listing page

NotFair GoogleAds tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Meta Ads MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mikusnuz-meta-ads-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mikusnuz/meta-ads-mcp"
      ],
      "env": {
        "META_ADS_ACCESS_TOKEN": "YOUR_META_ADS_ACCESS_TOKEN_HERE",
        "META_AD_ACCOUNT_ID": "YOUR_META_AD_ACCOUNT_ID_HERE"
      }
    }
  }
}

NotFair GoogleAds

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "notfair-googleads": {
      "url": "https://notfair.co/api/mcp/notfair"
    }
  }
}

Frequently asked questions

Meta Ads MCP is categorized under Marketing and uses a local stdio subprocess. NotFair GoogleAds belongs to Marketing and uses a remote HTTP/SSE transport. Pick Meta Ads MCP for marketing work and NotFair GoogleAds for marketing.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Meta Ads MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. NotFair GoogleAds has no declared pricing — check the project's own site. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mikusnuz-meta-ads-mcp and notfair-googleads as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Meta Ads MCP has a quality signal of 68/100 (Great) with 2 views, 0 installs and 91 GitHub stars. NotFair GoogleAds has 49/100 (Fair) with 1 views, 0 installs and 3,970 GitHub stars.