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

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

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

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

Which MCP server has more tools and community activity?

Google Tag Manager MCP Server lists 5 tools with 2 views and 212 GitHub stars. Token Meter lists 4 tools with 3 views and 1 GitHub stars.

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

Google Tag Manager MCP Server vs Token Meter

In-depth architectural comparison of the Google Tag Manager MCP Server and Token Meter 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

Google Tag Manager MCP Server

Marketing · Local stdio

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

Token Meter

Marketing · Local stdio

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

Verdict Summary: Choose Google Tag Manager MCP Server if you need specialized Marketing tools running via a local process. Choose Token Meter 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 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

Choose Token Meter when:

You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Freemium).
Primary tools included: .

Feature & Specification Comparison

Specification	Google Tag Manager MCP Server stape-io Marketing	Token Meter whdrnr2583-cmd Marketing
Summary	This server supports remote MCP connections, includes built-in Google OAuth, and provide an interface to the Google Tag Manager API.	Local-first dashboard + MCP server for Claude Code and Codex token usage. Cost, per-MCP/per-tool breakdown, hourly distribution, and session drill-down — your data never leaves your machine.
Category & Scope

Tools & Capabilities Breakdown

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

Token Meter Tools (4)

usage_summary

Daily table of token counts, USD-equivalent cost, and call counts — broken down by day and model

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

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"
      }
    }
  }
}

Token Meter Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "whdrnr2583-cmd-token-meter": {
      "command": "npx",
      "args": [
        "-y",
        "@whdrnr2583/token-meter"
      ]
    }
  }
}

Frequently Asked Questions

Google Tag Manager MCP Server is categorized under Marketing and uses a local stdio subprocess. In contrast, Token Meter belongs to Marketing using local stdio subprocess. Select Google Tag Manager MCP Server when you need capabilities focused on marketing and Token Meter when you require tools for marketing.

More alternatives to Google Tag Manager MCP Server More alternatives to Token Meter Marketing category hub