PumpGTM MCP server vs Google Tag Manager MC… | AllMCPs
Side-by-Side Model Context Protocol Comparison
PumpGTM MCP server vs Google Tag Manager MCP Server
In-depth architectural comparison of the PumpGTM MCP server 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
PumpGTM MCP server
Marketing · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: OAuth 2.0
Google Tag Manager MCP Server
Marketing · Local stdio
Quality: 60/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose PumpGTM MCP server if you need specialized Marketing tools running via a hosted cloud SSE transport. 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 PumpGTM MCP server 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).
PumpGTM is a hosted MCP server that lets Claude, ChatGPT, Cursor, Codex or any AI agent find buyers showing intent, run LinkedIn, email and X outreach from your own accounts inside each platform's limits, and hand every reply back to a human. Sign in with OAuth; no API key is needed for AI clients.Key tools: get_workspace, find_people, review_people, save_sequence_draft, set_sequence_status, add_leads, list_leads, get_cold_message_examples, reach_post_engagers.Remote URL: https://mcp.pumpgtm.com/mcp (Streamable HTTP, OAuth 2.1 with dynamic client registration). Claude Code: claude mcp add --transport http pumpgtm https://mcp.pumpgtm.com/mcp then claude mcp login pumpgtm. Paid SaaS, plans from $75/month. Docs: https://pumpgtm.com/docs/mcp
Tools & Capabilities Breakdown
PumpGTM MCP server Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
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
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).
PumpGTM MCP server is categorized under Marketing and uses a remote streaming HTTP/SSE transport. In contrast, Google Tag Manager MCP Server belongs to Marketing using local stdio subprocess. Select PumpGTM MCP server when you need capabilities focused on marketing and Google Tag Manager MCP Server when you require tools for marketing.