RouterGrowth vs Google Tag Manager MCP Server

In-depth architectural comparison of the RouterGrowth 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.

Which MCP Server Should You Choose?

R

Choose RouterGrowth when:

• You need dedicated capabilities in the Marketing domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: OAuth 2.0 (Paid Service).

Explore RouterGrowth Details

Choose Google Tag Manager MCP Server 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: GOOGLE_SERVICE_ACCOUNT_KEY.
• Primary tools included: 18 Google Tag Manager MCP tools, Hosted remote HTTP server, Built-in Google OAuth for hosted use.

Explore Google Tag Manager MCP Server Details

Feature & Specification Comparison

Specification	R RouterGrowth Marketing	Google Tag Manager MCP Server stape-io Marketing
Summary
Category & Scope	Marketing	Marketing
Quality signal

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "routergrowth": {
      "url": "https://api.routergrowth.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "stape-io-google-tag-manager-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "google-tag-manager-mcp-server"
      ],
      "env": {
        "GOOGLE_SERVICE_ACCOUNT_KEY": "YOUR_GOOGLE_SERVICE_ACCOUNT_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons