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

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

Token Meter operates under a Freemium 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?

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

Can I use both Token Meter 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

Token Meter vs Google Tag Manager MCP Server

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

Token Meter

Marketing · Local stdio

Quality: 57/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 Token Meter 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 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: usage_summary, recent_sessions, session_tools.

Explore Token Meter 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.

Feature & Specification Comparison

Specification	Token Meter whdrnr2583-cmd Marketing	Google Tag Manager MCP Server stape-io Marketing
Summary	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.	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

Token Meter Tools (4)

usage_summary

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

recent_sessions

Latest sessions with paste-ready `claude --resume` / `codex resume` commands

session_tools

Per-tool breakdown inside a session: call count, total tokens, average latency, response size

refresh_data

Re-scans your local JSONL logs for new activity, then returns a fresh summary

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

Token Meter Configuration

mcpServers (Claude Desktop / Cursor)

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

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

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

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