Meta Ads vs Synter Ads

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

Meta Ads logoMeta AdsSocial Media · Local subprocess (stdio)Meta (Facebook and Instagram) Ads: 34 read tools and 10 write tools that preview first.61GoodAuth: not declaredSynter Ads logoSynter AdsSocial Media · Local subprocess (stdio)Manage ad campaigns across Google, Meta, LinkedIn, Reddit, TikTok via AI agents65GreatAuth: not declared

Verdict: choose Meta Ads for social media work as a local process; choose Synter Ads for social media as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Meta Ads logoChoose Meta Ads when

  • You need dedicated capabilities in the Social Media domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: META_ACCESS_TOKEN.
  • You want tools like meta_health_check, meta_get_business_assets, meta_get_pages.
Explore Meta Ads

Synter Ads logoChoose Synter Ads when

  • You need dedicated capabilities in the Social Media domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: SYNTER_API_KEY.
  • You want tools like list_campaigns, create_search_campaign, create_display_campaign.
Explore Synter Ads

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMeta Ads logoMeta AdsSynter Ads logoSynter Ads
CategorySocial MediaSocial Media
Quality signal61/100 · Good65/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsMETA_ACCESS_TOKENSYNTER_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars121
Directory activity 4 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools4156

Tools & capabilities

Meta Ads tools 41

  • meta_health_checkAgent-ready read-only health check: validates token metadata, lists accessible ad accounts, and warns about missing read scopes without exposing the access token.
  • meta_get_business_assetsDiscover accessible Meta Business assets read-only: businesses, pages, Instagram accounts, pixels, and datasets when permissions allow.
  • meta_get_pagesList accessible Facebook Pages with id, name, category, tasks, picture, and linked Instagram account references when available.
  • meta_get_instagram_accountsList Instagram accounts linked to accessible Pages, Business Manager assets, or an ad account when permissions allow.
  • meta_get_pixelsList pixels and datasets from an ad account or Business Manager when accessible, returning actionable warnings for permission-limited edges.
  • meta_get_ad_activityRead ad account activity logs from /{ad_account_id}/activities with object, event, actor, timestamp, and extra_data fields.
  • meta_get_delivery_diagnosticsAggregate read-only delivery diagnostics across campaigns, ad sets, and ads using status/effective_status/issues_info where available plus simple delivery insights.
  • meta_get_creative_assetsReturn ad-linked creative media with actual ad names, collection covers, all carousel/flexible components, resolved image hashes and video URLs. Catalog-only ads are classified separately; use the hosted GetMCPAds service for an interactive visual gallery. Raw creative metadata remains available for diagnostics.
  • meta_get_audience_detailsRead detailed custom, saved, and lookalike audiences with pagination and rich fields where permissions allow.
  • meta_get_catalog_productsRead Product Catalogs and Product Items when catalog access is available. Returns join-ready product metadata without creating or updating catalog assets.
  • meta_join_product_insightsQuery product-breakdown insights and enrich rows with Product Catalog metadata when catalog access is available.
  • meta_get_brand_safety_controlsRead brand safety, suitability, placement, and context-control signals from ad account/ad set targeting and optional block-list edges.
  • +29 more on the listing page

Synter Ads tools 56

  • list_campaignsList campaigns for ONE ad platform across all 16 ad platforms. `platform` is required -- this tool does not aggregate across platforms. Returns campaign name, status, budget, and performance metrics. 100% Free to Read ($0.00 / 0 credits — works out-of-the-box with zero configuration or API key; live write execution starts on the $20/month Solo plan).
  • create_search_campaignCreate a Google Ads Search campaign with an ad group, responsive search ad, and keywords — all in one atomic request. Supports `dry_run: true` ($0.00 / 0 credits, zero credentials required) to preview payload and policy checks. Live execution passes the server-side Agent Shield safety gate (daily spend caps, paused-on-create default, human approval mode, and immutable workspace audit log) on the $20/month Solo plan ($20.00 included monthly credits, 0% ad-spend markup). IMPORTANT — creative floor: supply 11-15 headlines (15 recommended, max 30 chars each) and 4 descriptions (max 90 chars each), echoing your target keywords across at least 5 headlines. The API accepts as few as 3 headlines / 2 descriptions, but ads built near that minimum score 'Poor' on Google Ad Strength, get throttled in the auction, and may be rejected by the platform — treat 11 headlines / 4 descriptions as the real minimum. Fewer than 3 headlines or fewer than 2 descriptions will cause the campaign to be rejected before any API call is made.
  • create_display_campaignCreate a Google Ads Display campaign with responsive display ads. Supports image uploads from URLs, `dry_run: true` ($0.00 / 0 credits, zero credentials required), and server-side safety gates (daily spend caps, paused-on-create default, approval mode, and audit log).
  • create_pmax_campaignCreate a Google Ads Performance Max campaign. Requires images, headlines, descriptions, and a business name. Supports `dry_run: true` ($0.00 / 0 credits, zero credentials required) and server-side safety gates (daily spend caps, paused-on-create default, approval mode, and audit log).
  • pause_campaignPause a campaign by ID across all 16 connected ad platforms. Supports `dry_run: true` ($0.00 / 0 credits, zero credentials required). Live execution is audited in the workspace audit log ($0.05 / 2 credits on Solo $20/mo plan).
  • update_campaign_budgetUpdate the daily budget for a campaign across all 16 connected ad platforms. Supports `dry_run: true` ($0.00 / 0 credits, zero credentials required). Live execution passes the server-side Agent Shield safety gate (daily spend ceiling, max 2x budget-change multiplier, approval mode, and immutable audit log).
  • get_performanceGet performance metrics (impressions, clicks, spend, conversions, ROAS) for campaigns across any of the 16 ad platforms. Free read-only tool ($0.00 / 0 credits).
  • get_daily_spendGet daily spend breakdown for ONE ad platform across any of the 16 ad platforms. `platform` is required -- this tool does not aggregate across platforms. Free read-only tool ($0.00 / 0 credits).
  • pacing_reportReturn a deterministic budget-pacing snapshot for the current workspace across every connected ad platform and the overall portfolio (month-to-date spend, today's spend, expected spend to date, pacing percent, projected end-of-period spend, on_track/underspending/overspending/critical status, and off-pace warnings). Free read-only tool ($0.00 / 0 credits).
  • user_budget_pacing_reportReturn a deterministic per-user/trader budget ownership and pacing snapshot from saved workspace assignments (target budget, actual spend, expected spend, projected spend, variance, and pacing status). Free read-only tool ($0.00 / 0 credits).
  • optimize_budgetRecommend a cross-channel budget allocation across connected ad platforms using diminishing-returns modeling. Recommend-only (dry_run defaults to true); apply approved changes with update_campaign_budget. Free read-only recommendation tool ($0.00 / 0 credits).
  • add_keywordsAdd keywords to a Google Ads campaign or ad group.
  • +44 more on 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

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "meta-ads": {
      "command": "npx",
      "args": [
        "-y",
        "@getmcpads/meta-ads-mcp-server"
      ],
      "env": {
        "META_ACCESS_TOKEN": "YOUR_META_ACCESS_TOKEN_HERE"
      }
    }
  }
}

Synter Ads

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "synter-ads-2": {
      "command": "npx",
      "args": [
        "-y",
        "@synterai/mcp-server"
      ],
      "env": {
        "SYNTER_API_KEY": "YOUR_SYNTER_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Meta Ads is categorized under Social Media and uses a local stdio subprocess. Synter Ads belongs to Social Media and uses a local stdio subprocess. Pick Meta Ads for social media work and Synter Ads for social media.

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 has no declared pricing — check the project's own site. Synter Ads has no declared pricing — check the project's own site. 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 meta-ads and synter-ads-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Meta Ads has a quality signal of 61/100 (Good) with 4 views, 0 installs and 1 GitHub stars. Synter Ads has 65/100 (Great) with 1 views, 0 installs and 21 GitHub stars.