google-tag-manager

This MCP server provides remote access to Google Tag Manager (GTM) via an MCP interface with built-in Google OAuth. It allows Claude and other MCP clients to connect to the GTM API through a remote MCP server, enabling tools and commands that interact with GTM data without requiring local GTM credentials. To use it, configure Claude Desktop (or your MCP client) to connect to the remote server, which authenticates via Google OAuth and exposes GTM tools through the MCP bridge. Once connected, you can access GTM-related capabilities such as retrieving container configurations, managing workspaces, and interacting with GTM API endpoints through the MCP tools provided by this server. The recommended flow is to add the server under mcpServers with the provided npx command, authenticate when prompted, and then invoke GTM tools as you would with other MCP-enabled tools.

Accessing via Claude Desktop: Open Claude Desktop → Settings → Developer → Edit Config, replace with the provided mcpServers configuration, and restart. A browser window will prompt you to log in with Google and authorize the MCP server. After authorization, the GTM tools will be available for use within Claude.

Prerequisites:

• Node.js installed on your machine (npx is included with Node.js)
• Internet access to fetch the mcp-remote package
• Access to configure Claude Desktop or your MCP client with a remote MCP server configuration

Step-by-step:

1. Ensure Node.js and npm are installed. You can verify with: node -v npm -v

2. Use the provided MCP server configuration in Claude Desktop or your MCP client. Create or edit your MCP configuration to include:

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

3. Save the configuration and restart Claude Desktop (or your MCP client). A browser window will open to complete Google OAuth authentication for the GTM MCP server. Complete the login flow to grant access.

4. After successful authentication, the GTM MCP tools will be available for use within Claude or your MCP client. Invoke GTM-related commands as you would with other MCP tools.

Optional: If you run into issues, you can rely on the MCP client to retry authentication or re-fetch tokens via the OAuth flow prompted by the client.

Tips and common issues:

• MCP Client Name Length: Some clients enforce a combined length limit for server name and tool name (e.g., 60 characters). If you specify a long server name like gtm-mcp-server-your-very-long-name, some tools may be filtered out. Use shorter server names such as gtm-mcp-server.
• Credential storage: The mcp-remote flow stores credentials locally (default at ~/.mcp-auth or as configured by MCP_REMOTE_CONFIG_DIR). If you encounter authentication issues, you can clear locally stored state by running: rm -rf ~/.mcp-auth and restarting your MCP client to re-enter OAuth flow.
• Troubleshooting login: Ensure your Google account has the necessary permissions for GTM API access and that the GTM account is accessible from the OAuth consent screen used by the MCP server.
• Network considerations: If behind a corporate firewall or VPN, ensure that outbound HTTPS to the MCP server URL (https://gtm-mcp.stape.ai/mcp) is allowed.