Revup vs Google Tag Manager MC… — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Revup vs Google Tag Manager MCP Server
In-depth architectural comparison of the Revup 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
Revup
Marketing · Remote HTTP/SSE
Quality: 65/100 (Great) | Auth: OAuth 2.0
Google Tag Manager MCP Server
Marketing · Local stdio
Quality: 60/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Revup 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 Revup when:
You need dedicated capabilities in the Marketing domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: OAuth 2.0 (Freemium).
Create, customize, preview and report on sweepstakes, contests, forms, surveys, quizzes and other promotions in a connected Revup account. Connect through OAuth; access follows your account role and granted permissions.
This server supports remote MCP connections, includes built-in Google OAuth, and provide an interface to the Google Tag Manager API.
Category & Scope
Tools & Capabilities Breakdown
Revup 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).
Revup 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 Revup when you need capabilities focused on marketing and Google Tag Manager MCP Server when you require tools for marketing.