What is the main functional difference between Mailzzy and Google Tag Manager MCP Server?

Mailzzy is categorized under Marketing and uses a remote HTTP/SSE transport. Google Tag Manager MCP Server belongs to Marketing and uses a local stdio subprocess. Pick Mailzzy for marketing work and Google Tag Manager MCP Server for marketing.

How do I install Mailzzy or Google Tag Manager MCP Server in Claude Desktop, Cursor, or Windsurf?

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Are Mailzzy and Google Tag Manager MCP Server free to use, or do they require API keys?

Mailzzy has no declared pricing — check the project's own site. Google Tag Manager MCP Server is listed as free. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Can I run both Mailzzy and Google Tag Manager MCP Server at the same time in my AI client?

Yes. MCP clients support multiple servers: add mailzzy and stape-io-google-tag-manager-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Mailzzy has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Google Tag Manager MCP Server has 60/100 (Good) with 4 views, 0 installs and 227 GitHub stars.

Mailzzy vs Google Tag Manager MCP Server

A side-by-side look at the Mailzzy and Google Tag Manager MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

MailzzyMarketing · Remote HTTP/SSEAllows AI assistants to interact with Mailzzy for email marketing tasks, including campaign management, contact handling, template operations, sending, and automation.48FairAuth: not declared

Google Tag Manager MCP ServerMarketing · Local subprocess (stdio)This server supports remote MCP connections, includes built-in Google OAuth, and provide an interface to the Google Tag Manager API.60GoodAuth: oauth 2.0

Verdict: choose Mailzzy for marketing work over a hosted endpoint; choose Google Tag Manager MCP Server for marketing as a local process. You can also run both side by side in one mcpServers block.

Spec	M Mailzzy	Google Tag Manager MCP Server
Category	Marketing	Marketing
Quality signal	48/100 · Fair	60/100 · Good
Install command	Confirmed	Confirmed
Transport	Remote HTTP/SSE	Local subprocess (stdio)
Auth	Not declared	OAuth 2.0
Pricing	Not declared	Free
Required env vars	None listed	`GOOGLE_SERVICE_ACCOUNT_KEY`
Verified owner	Community listing	Community listing
GitHub stars	0	227
Directory activity	1 views 0 installs 0 upvotes	4 views 0 installs 0 upvotes
Tools	Not listed	Not listed
Full listing	View Mailzzy	View Google Tag Manager MCP Server

Mailzzy vs Google Tag Manager MCP Server

Which MCP server should you choose?

Choose Mailzzy when

Choose Google Tag Manager MCP Server when

Feature & specification comparison

Tools & capabilities

Mailzzy tools

Google Tag Manager MCP Server tools

Ready-to-paste client configs

Mailzzy

Google Tag Manager MCP Server

Frequently asked questions