Google Tag Manager MCP Server vs Tin

A side-by-side look at the Google Tag Manager MCP Server and Tin MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Google Tag Manager MCP Server logoGoogle Tag Manager MCP ServerMarketing · Local subprocess (stdio)This server supports remote MCP connections, includes built-in Google OAuth, and provide an interface to the Google Tag Manager API.61GoodAuth: oauth 2.0Tin logoTinMarketing · Remote HTTP/SSEOpen-source marketing system, designed for coding agents.45FairAuth: not declared

Verdict: choose Google Tag Manager MCP Server for marketing work as a local process; choose Tin for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Google Tag Manager MCP Server logoChoose Google Tag Manager MCP Server when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
  • You have the keys it needs: GOOGLE_SERVICE_ACCOUNT_KEY.
Explore Google Tag Manager MCP Server

Tin logoChoose Tin when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a remote HTTP/SSE transport.
Explore Tin

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGoogle Tag Manager MCP Server logoGoogle Tag Manager MCP ServerTin logoTin
CategoryMarketingMarketing
Quality signal61/100 · Good45/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthOAuth 2.0Not declared
PricingFreeNot declared
Required env varsGOOGLE_SERVICE_ACCOUNT_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars236264
Directory activity 5 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Google Tag Manager MCP Server tools

No tool names declared yet. Check the project README from the listing page.

Tin tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Google Tag Manager MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "stape-io-google-tag-manager-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "google-tag-manager-mcp-server"
      ],
      "env": {
        "GOOGLE_SERVICE_ACCOUNT_KEY": "YOUR_GOOGLE_SERVICE_ACCOUNT_KEY_HERE"
      }
    }
  }
}

Tin

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "tin": {
      "url": "https://app.tin.computer/mcp"
    }
  }
}

Frequently asked questions

Google Tag Manager MCP Server is categorized under Marketing and uses a local stdio subprocess. Tin belongs to Marketing and uses a remote HTTP/SSE transport. Pick Google Tag Manager MCP Server for marketing work and Tin for marketing.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Google Tag Manager MCP Server is listed as free. Auth: oauth 2.0. Tin has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add stape-io-google-tag-manager-mcp-server and tin as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Google Tag Manager MCP Server has a quality signal of 61/100 (Good) with 5 views, 0 installs and 236 GitHub stars. Tin has 45/100 (Fair) with 1 views, 0 installs and 264 GitHub stars.