Facebook Ads Mcp Server vs Google Tag Manager Mcp Server
Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.
MCP server acting as an interface to the Facebook Ads, enabling programmatic access to Facebook Ads data and management features.
This server supports remote MCP connections, includes built-in Google OAuth, and provide an interface to the Google Tag Manager API.
Quality signal
47/100 (Fair)
47/100 (Fair)
Install path
npx · high
Remote · high
Engagement
0 0 0 349
1 0 0 197
Tools
Lists ad accounts linked to a Meta access tokenRetrieves detailed information for campaigns, ad sets, ads, and creativesFetches collections of ads and ad sets by account or campaignProvides performance insights for accounts, campaigns, and ad setsSupports automatic Meta token creation via GoMarble's serverEasy local setup with Python and optional virtual environment
Remote MCP server supporting Google Tag Manager APIBuilt-in Google OAuth authentication flowConfigurable for local development with Google Cloud OAuthSupports integration with MCP clients like Claude DesktopIncludes troubleshooting guidance for cache and naming limits
