MCP Server for Google Tag Manager

Name: MCP Server for Google Tag Manager
Author: stape-io

@stape-io

代码仓库主页

关于 MCP Server for Google Tag Manager

MCP server for Google Tag Manager

#mcp #gtm #gtm-server-side #stape #mcp-server

基本信息

分类

其他

许可证

Apache-2.0

运行时

node

传输方式

stdio

发布者

stape-io

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "gtm-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://gtm-mcp.stape.ai/mcp"
      ]
    }
  }
}

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is MCP Server for Google Tag Manager?

This server supports remote MCP connections with built-in Google OAuth and provides an interface to the Google Tag Manager API. It is designed for users who want to manage Google Tag Manager resources via an MCP-compatible client (e.g., Claude Desktop).

How to use MCP Server for Google Tag Manager?

Configure your MCP client (e.g., Claude Desktop) with the command npx -y mcp-remote and the URL https://gtm-mcp.stape.ai/mcp. After restarting the client, a browser window will open for Google OAuth authentication; once granted, the server's tools become available.

Key features of MCP Server for Google Tag Manager

Remote MCP connection support
Built-in Google OAuth authentication
Interfaces with the Google Tag Manager API

Use cases of MCP Server for Google Tag Manager

—

FAQ from MCP Server for Google Tag Manager

How do I configure the server for Claude Desktop?

Add the following to your Claude Desktop config file (Settings -> Developer -> Edit Config): { "mcpServers": { "gtm-mcp-server": { "command": "npx", "args": ["-y", "mcp-remote", "https://gtm-mcp.stape.ai/mcp"] } } }. Restart Claude and complete the OAuth flow.

Why are some tools missing after configuration?

Some MCP clients (e.g., Cursor AI) have a 60-character limit for the combined server name + tool name. Using a long server name (e.g., gtm-mcp-server-your-additional-long-name) may cause tools to be filtered out. Use a short server name like gtm-mcp-server to avoid this.

How do I clear cached credentials if I encounter issues?

The mcp-remote tool stores credentials in ~/.mcp-auth (or $MCP_REMOTE_CONFIG_DIR). Run rm -rf ~/.mcp-auth to clear locally stored state and tokens, then restart your MCP client.