MCP Gtm Tech Stack Si… vs Google Tag Manager MC… | AllMCPs
Side-by-Side Model Context Protocol Comparison
MCP Gtm Tech Stack Signal Scraper vs Google Tag Manager MCP Server
In-depth architectural comparison of the MCP Gtm Tech Stack Signal Scraper 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
MCP Gtm Tech Stack Signal Scraper
Marketing · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
Google Tag Manager MCP Server
Marketing · Local stdio
Quality: 59/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose MCP Gtm Tech Stack Signal Scraper 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 MCP Gtm Tech Stack Signal Scraper 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 need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, COOKIE_ENCRYPTION_KEY, WORKER_HOST, HOSTED_DOMAIN.
Primary tools included: Remote MCP server supporting Google OAuth authentication, Interface to Google Tag Manager API, Hosted server available at gtm-mcp.stape.ai.
Detect which GTM tools a company uses from its public-facing website. Returns CRM, sequencer, and marketing automation signals as a flat, Clay-ready JSON row, with per-tool boolean flags for HubSpot, Salesforce, Apollo, Gong, Intercom, and Marketo, plus a composite tech stack signal. Pass technologies to narrow the answer to named tools. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
Google Tag Manager MCP Server Tools (5)
Remote MCP server supporting Google OAuth authentication
Interface to Google Tag Manager API
Hosted server available at gtm-mcp.stape.ai
Local development mode with user-configured Google Cloud OAuth
OAuth login flow opening in browser for user consent
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).
MCP Gtm Tech Stack Signal Scraper 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 MCP Gtm Tech Stack Signal Scraper when you need capabilities focused on marketing and Google Tag Manager MCP Server when you require tools for marketing.
