Google Tag Manager MCP vs Magic Insights

In-depth architectural comparison of the Google Tag Manager MCP and Magic Insights 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?

G

Choose Google Tag Manager MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: list_accounts, get_account, list_containers.

Explore Google Tag Manager MCP Details

Choose Magic Insights when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: get_workspace, list_studies, get_study.

Explore Magic Insights Details

Feature & Specification Comparison

Specification	G Google Tag Manager MCP Developer Tools	Magic Insights Developer Tools
Summary	MCP server for the Google Tag Manager API v2: containers, workspaces, tags, triggers, publishing.	Query your customer feedback: studies, themes, suggestions, tags, and sentiment trends.
Category & Scope	Developer Tools	Developer Tools

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": {
    "google-tag-manager-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-tagmanager@latest"
      ]
    }
  }
}

{
  "mcpServers": {
    "magic-insights": {
      "url": "https://modelcontextprotocol.io"
    }
  }
}

Related MCP Server Comparisons