Google Search Console MCP vs Google Tag Manager MCP Server
In-depth architectural comparison of the Google Search Console 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
Google Search Console MCP
Marketing · Local stdio
Quality: 64/100 (Good) | Auth: OAuth 2.0
Google Tag Manager MCP Server
Marketing · Local stdio
Quality: 60/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Google Search Console 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 Google Search Console MCP when:
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: GSC_CLIENT_ID, GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN.
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.
Google Search Console MCP server: query performance data, inspect URLs, check indexing, and generate brandable HTML SEO audit reports with a 30/60/90-day roadmap. Read-only OAuth scope, installable via uvx mcp-google-search-console.
This server supports remote MCP connections, includes built-in Google OAuth, and provide an interface to the Google Tag Manager API.
Google Search Console 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 Google Search Console MCP when you need capabilities focused on marketing and Google Tag Manager MCP Server when you require tools for marketing.
