Gam Seller MCP Node vs Meta Ads MCP

A side-by-side look at the Gam Seller MCP Node 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.

Gam Seller MCP Node logoGam Seller MCP NodeMarketing · Local subprocess (stdio)Governed, read-only MCP server exposing Google Ad Manager inventory discovery to buyer agents44FairAuth: 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 Gam Seller MCP Node for marketing work as a local process; 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?

Gam Seller MCP Node logoChoose Gam Seller MCP Node when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: MCP_CONFIG_DIR, MCP_REQUIRE_IDEMPOTENCY_KEY.
Explore Gam Seller MCP Node

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.

SpecGam Seller MCP Node logoGam Seller MCP NodeMeta Ads MCP logoMeta Ads MCP
CategoryMarketingMarketing
Quality signal44/100 · Fair68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredBYOK (pay the provider)
Required env varsMCP_CONFIG_DIRMCP_REQUIRE_IDEMPOTENCY_KEYMETA_ADS_ACCESS_TOKENMETA_AD_ACCOUNT_ID
Verified ownerCommunity listingCommunity listing
GitHub stars091
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed134

Tools & capabilities

Gam Seller MCP Node 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.

Gam Seller MCP Node

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "gam-seller-mcp-node": {
      "command": "npx",
      "args": [
        "-y",
        "gam-seller-mcp-node"
      ],
      "env": {
        "MCP_CONFIG_DIR": "YOUR_MCP_CONFIG_DIR_HERE",
        "MCP_REQUIRE_IDEMPOTENCY_KEY": "YOUR_MCP_REQUIRE_IDEMPOTENCY_KEY_HERE"
      }
    }
  }
}

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

Gam Seller MCP Node is categorized under Marketing and uses a local stdio subprocess. Meta Ads MCP belongs to Marketing and uses a local stdio subprocess. Pick Gam Seller MCP Node 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.

Gam Seller MCP Node 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 gam-seller-mcp-node and mikusnuz-meta-ads-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Gam Seller MCP Node has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Meta Ads MCP has 68/100 (Great) with 2 views, 0 installs and 91 GitHub stars.