In-depth architectural comparison of the Meta Ads MCP and Google Tag Manager MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Meta Ads MCP
Marketing · Local stdio
Quality: 65/100 (Great) | Auth: API Key required
Google Tag Manager MCP Server
Marketing · Local stdio
Quality: 60/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Meta Ads MCP if you need specialized Marketing tools running via a local process. Choose Google Tag Manager MCP Server if your workspace requires Marketing integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Meta Ads MCP when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: META_ADS_ACCESS_TOKEN, META_AD_ACCOUNT_ID, META_APP_ID, META_APP_SECRET, META_BUSINESS_ID, META_PIXEL_ID.
MCP server for Meta Marketing API v25.0 — 123 tools for Facebook & Instagram ad campaigns, audiences, creatives, insights, catalogs, and automated rules.
This server supports remote MCP connections, includes built-in Google OAuth, and provide an interface to the Google Tag Manager API.
Category & Scope
Tools & Capabilities Breakdown
Meta Ads MCP Tools (80)
list_campaigns
List campaigns with filtering and pagination
get_campaign
Get campaign details by ID
create_campaign
Create a new campaign
update_campaign
Update campaign settings
delete_campaign
Delete a campaign
copy_campaign
Copy an existing campaign with ad sets and ads
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Meta Ads MCP is categorized under Marketing and uses a local stdio subprocess. In contrast, Google Tag Manager MCP Server belongs to Marketing using local stdio subprocess. Select Meta Ads MCP when you need capabilities focused on marketing and Google Tag Manager MCP Server when you require tools for marketing.
Popular comparisons with Google Tag Manager MCP Server
Primary tools included: Remote MCP server supporting Google OAuth authentication, Interface to Google Tag Manager API, Hosted server available at gtm-mcp.stape.ai.