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

Leadace belongs to the Marketing category with local stdio execution, while Google Tag Manager MCP Server belongs to the Marketing category with local stdio execution.

How do I install Leadace or Google Tag Manager MCP Server 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 Leadace and Google Tag Manager MCP Server free or paid?

Leadace operates under a Free / Open Source model (No auth required). Google Tag Manager MCP Server operates under a Free / Open Source model (OAuth 2.0).

Which MCP server has more tools and community activity?

Leadace lists 0 tools with 0 views and 3 GitHub stars. Google Tag Manager MCP Server lists 5 tools with 2 views and 210 GitHub stars.

Can I use both Leadace and Google Tag Manager MCP Server 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

Leadace vs Google Tag Manager MCP Server

In-depth architectural comparison of the Leadace 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

Leadace

Marketing · Local stdio

Quality: 51/100 (Good) | Auth: No auth required

Google Tag Manager MCP Server

Marketing · Local stdio

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

Verdict Summary: Choose Leadace 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 Leadace 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).

Explore Leadace Details

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_CLIENT_ID, GOOGLE_CLIENT_SECRET, COOKIE_ENCRYPTION_KEY, WORKER_HOST, HOSTED_DOMAIN.
Primary tools included: Remote MCP server supporting Google OAuth authentication, Interface to Google Tag Manager API, Hosted server available at gtm-mcp.stape.ai.

Explore Google Tag Manager MCP Server Details

Feature & Specification Comparison

Specification	Leadace aitit-inc Marketing	Google Tag Manager MCP Server stape-io Marketing
Summary	Outbound sales agent for Claude Code. Per-prospect website research, one email per prospect, sending from the user's own Gmail, reply tracking, and structured rejection feedback published as JSON Schema. Open source, self-hostable backend.	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

Leadace Tools (0)

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

Google Tag Manager MCP Server Tools (5)

Remote MCP server supporting Google OAuth authentication

Interface to Google Tag Manager API

Hosted server available at gtm-mcp.stape.ai

Local development mode with user-configured Google Cloud OAuth

OAuth login flow opening in browser for user consent

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

Leadace Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "aitit-inc-leadace": {
      "command": "npx",
      "args": [
        "-y",
        "supabase"
      ]
    }
  }
}

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_CLIENT_ID": "YOUR_GOOGLE_CLIENT_ID_HERE",
        "GOOGLE_CLIENT_SECRET": "YOUR_GOOGLE_CLIENT_SECRET_HERE",
        "COOKIE_ENCRYPTION_KEY": "YOUR_COOKIE_ENCRYPTION_KEY_HERE",
        "WORKER_HOST": "YOUR_WORKER_HOST_HERE",
        "HOSTED_DOMAIN": "YOUR_HOSTED_DOMAIN_HERE"
      }
    }
  }
}

Frequently Asked Questions

Leadace 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 Leadace when you need capabilities focused on marketing and Google Tag Manager MCP Server when you require tools for marketing.

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