What is the key difference between Google Tag Manager MCP Server and TargetWise?

Google Tag Manager MCP Server belongs to the Marketing category with local stdio execution, while TargetWise belongs to the Marketing category with cloud HTTP/SSE execution.

How do I install Google Tag Manager MCP Server or TargetWise in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Google Tag Manager MCP Server and TargetWise free or paid?

Google Tag Manager MCP Server operates under a Free / Open Source model (OAuth 2.0). TargetWise operates under a Paid Service model (API Key required).

Which MCP server has more tools and community activity?

Google Tag Manager MCP Server lists 6 tools with 2 views and 223 GitHub stars. TargetWise lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Google Tag Manager MCP Server and TargetWise together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Google Tag Manager MCP Server vs TargetWise

In-depth architectural comparison of the Google Tag Manager MCP Server and TargetWise 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 Tag Manager MCP Server

Marketing · Local stdio

Quality: 60/100 (Good) | Auth: OAuth 2.0

TargetWise

Marketing · Remote HTTP/SSE

Quality: 55/100 (Good) | Auth: API Key required

Verdict Summary: Choose Google Tag Manager MCP Server if you need specialized Marketing tools running via a local process. Choose TargetWise if your workspace requires Marketing integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

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

Choose TargetWise when:

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

Explore TargetWise Details

Feature & Specification Comparison

Specification	Google Tag Manager MCP Server stape-io Marketing	T TargetWise Marketing
Summary	This server supports remote MCP connections, includes built-in Google OAuth, and provide an interface to the Google Tag Manager API.	Hosted B2B prospecting and enrichment MCP with 11 tools for company/contact discovery, employee search, profile enrichment, work email lookup, business phone lookup and reverse email lookup. Streamable HTTP at https://targetwise.ai/api/mcp; requires a TargetWise workspace Bearer API key. Requests consume workspace credits. Public repo provides connection examples, not the server implementation.
Category & Scope

Tools & Capabilities Breakdown

Google Tag Manager MCP Server Tools (6)

18 Google Tag Manager MCP tools

Hosted remote HTTP server

Built-in Google OAuth for hosted use

Local stdio CLI

Service account, refresh token, and access token authentication

Shared tool schemas across hosted and local modes

TargetWise Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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

Google Tag Manager MCP Server Configuration

mcpServers (Claude Desktop / Cursor)

{
  "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"
      }
    }
  }
}

TargetWise Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "targetwise": {
      "url": "https://targetwise.ai/api/mcp"
    }
  }
}

Frequently Asked Questions

Google Tag Manager MCP Server is categorized under Marketing and uses a local stdio subprocess. In contrast, TargetWise belongs to Marketing using remote streaming HTTP/SSE transport. Select Google Tag Manager MCP Server when you need capabilities focused on marketing and TargetWise when you require tools for marketing.

More alternatives to Google Tag Manager MCP Server More alternatives to TargetWise Marketing category hub