Stape MCP Server vs Google Tag Manager MC… | AllMCPs
Side-by-Side Model Context Protocol Comparison
Stape MCP Server vs Google Tag Manager MCP Server
In-depth architectural comparison of the Stape 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
Stape MCP Server
Marketing · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Google Tag Manager MCP Server
Marketing · Local stdio
Quality: 60/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Stape MCP Server if you need specialized Marketing tools running via a local process. 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 Stape MCP Server when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Supports Stape API access via MCP protocol, Configurable authorization using API keys, EU region endpoint support with custom headers.
This project implements an MCP (Model Context Protocol) server for the Stape platform. It allows interaction with the Stape API using AI assistants like Claude or AI-powered IDEs like Cursor.
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
Stape MCP Server Tools (5)
Supports Stape API access via MCP protocol
Configurable authorization using API keys
EU region endpoint support with custom headers
Compatible with AI clients like Claude and Cursor
Open source implementation under Apache 2.0 license
Google Tag Manager MCP Server Tools (5)
Remote MCP server supporting Google OAuth authentication
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).
Stape MCP Server is categorized under Marketing and uses a local stdio subprocess. In contrast, Google Tag Manager MCP Server belongs to Marketing using local stdio subprocess. Select Stape MCP Server when you need capabilities focused on marketing and Google Tag Manager MCP Server when you require tools for marketing.