Amazonads MCP vs Meta Ads MCP

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

Amazonads MCP logoAmazonads MCPMarketingMCP server for Amazon Ads API - manage campaigns, keywords, bids, and performance reports29EmergingAuth: not declaredMeta 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 required

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

Which MCP server should you choose?

Amazonads MCP logoChoose Amazonads MCP when

  • You need dedicated capabilities in the Marketing domain.
  • You have the keys it needs: AMAZON_ADS_CLIENT_ID, AMAZON_ADS_CLIENT_SECRET, AMAZON_ADS_REFRESH_TOKEN, AMAZON_ADS_REGION, AMAZON_ADS_SANDBOX.
Explore Amazonads MCP

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAmazonads MCP logoAmazonads MCPMeta Ads MCP logoMeta Ads MCP
CategoryMarketingMarketing
Quality signal29/100 · Emerging68/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredBYOK (pay the provider)
Required env varsAMAZON_ADS_CLIENT_IDAMAZON_ADS_CLIENT_SECRETAMAZON_ADS_REFRESH_TOKENAMAZON_ADS_REGIONAMAZON_ADS_SANDBOXMETA_ADS_ACCESS_TOKENMETA_AD_ACCOUNT_ID
Verified ownerCommunity listingCommunity listing
GitHub stars391
Directory activity 3 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed134

Tools & capabilities

Amazonads MCP tools

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

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

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.

Amazonads MCP

No confirmed install command for Amazonads MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.

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"
      }
    }
  }
}

Frequently asked questions

Amazonads MCP is categorized under Marketing and uses an install path we have not confirmed yet. Meta Ads MCP belongs to Marketing and uses a local stdio subprocess. Pick Amazonads MCP for marketing work and Meta Ads MCP 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. Amazonads MCP has no confirmed install command yet — follow its own setup instructions.

Amazonads MCP has no declared pricing — check the project's own site. Meta Ads MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 amazonads-mcp and mikusnuz-meta-ads-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Amazonads MCP has a quality signal of 29/100 (Emerging) with 3 views, 0 installs and 3 GitHub stars. Meta Ads MCP has 68/100 (Great) with 2 views, 0 installs and 91 GitHub stars.