Claude Code can use a GTM MCP connection to build an evidence-based tracking change proposal. The useful workflow starts with the current container and a named workspace, rather than an unqualified request to fix tracking. This guide covers connection, verification and a reviewable proposal before any publication.
What do you need before connecting?
Use Claude Code installed on the computer where you will run these commands. Its CLI supports remote HTTP MCP servers and browser OAuth. This route registers an explicit user-scoped server for use across your projects; project-scoped team configuration is a separate choice. You do not need to run a local Google API server.
- A Google login that can read the intended Tag Manager container.
- A LoomaScale account with Google Tag Manager connected separately from Analytics or Google Ads.
- The container you want to inspect, plus a named workspace if you later request a draft change. Editing, creating versions and publishing require their corresponding Google permissions.
How do you connect Claude Code to GTM?
1. Connect GTM in LoomaScale
Create or sign in to your LoomaScale account, then open Connections. Choose Google Tag Manager, sign in with the Google email that has access to the required data, and review the requested permissions. Signing in to LoomaScale with Google is not a substitute for connecting this data source. You can connect this service without connecting an advertising account.
2. Register the remote MCP server in Claude Code
Run this command in your system terminal, outside a Claude Code conversation. User scope makes the connection available across your projects. The URL selects this Google service's tools.
claude mcp add --transport http --scope user loomascale-gtm https://api.loomascale.com/mcp/gtmIf you already use the full LoomaScale agent plugin, check its tools before adding a second connection. The plugin route is documented in the Claude Code setup guide; this article uses direct MCP setup.
3. Authenticate from Claude Code's MCP menu
Open Claude Code and enter /mcp. Select loomascale-gtm and complete its authentication flow in the browser. Use the LoomaScale account with your Google source connected. Return to Claude Code and confirm the server is connected. You can inspect the saved server from the system terminal with claude mcp get loomascale-gtm or claude mcp list. A successful add command saves configuration; it does not prove that the Google account lookup succeeded.
4. Verify access with an actual account lookup
Use LoomaScale to call gtm_list_containers. Show each container's name, public GTM ID and account. Ask me which one to inspect. Read its published version and list its workspaces. Do not edit, create a version or publish anything.
Check that the response identifies your actual container, including its GTM- public ID. Distinguish the published version from each draft workspace before discussing a tracking issue. The container's API account and container IDs are different identifiers from its public GTM- ID; let the tools discover the required values. A successful inventory confirms access to configuration, not that a browser event fires correctly.
How do you prepare a GTM change proposal in Claude Code?
Identify one tracking issue and inspect its dependencies. If repository code emits the relevant event, read that contract too. Ask for the smallest proposed tag, trigger or variable change and a test plan. Before requesting a write, choose the workspace and review its existing changes so the eventual version has a clear scope.
Use LoomaScale for the selected GTM container. Read its published tracking configuration and list available workspaces. For the lead event I describe, compare relevant repository instrumentation with GTM tags and triggers. Produce a proposal containing current configuration, exact proposed fields, affected dependencies and a Tag Assistant test plan. Ask me to choose a workspace before any future edit. For now, change nothing and do not publish.
A proposal should be concrete enough to review without granting a broad instruction to repair everything. Where write tools are available, a draft edit remains separate from version creation and publication. Verify behavior in Preview and inspect the specific version before approval. Container inspection alone cannot certify that the site handles every consent or navigation state.
Which MCP endpoint does this guide use?
https://api.loomascale.com/mcp/gtmThe service-specific endpoint exposes GTM tools and LoomaScale account helpers. The full directory plugin or connector uses https://api.loomascale.com/mcp and can reach all sources you separately connect. Choose the full connection for work across services; use the specific endpoint when you want this source's tool set. An endpoint choice limits exposed tools, not the Google roles your login holds.
What can Claude Code read or change in GTM?
LoomaScale reads containers, tags, triggers, variables, workspaces, versions and tracking-audit findings. Where enabled and authorized, changes go into the workspace you select; creating a version and publishing it are separate operations. Review the exact version before approving publication. Configuration inspection cannot observe a visitor's browser or prove that consent and tags behave correctly on the site. Validate proposed changes in Tag Manager Preview and Tag Assistant before a live release.
Why is the connection or data missing?
If the server needs authentication, open /mcp and sign in again. If tools are missing, check claude mcp list, the source endpoint, and whether an organization policy restricts the server. Restart the session after a configuration change if needed. A Claude web connector and an explicit CLI server can overlap; check the active tools before adding duplicate connections.
A missing container usually calls for checking the Google login, container access and Tag Manager connection. If discovery says accounts are still loading, retry after discovery finishes. If an audit describes different tags from the live site, check whether you requested the published version or a draft workspace. A write-permission error is separate from read access: check the relevant edit, version or publish permission and the feature's availability before reconnecting.
Related connection guides and official references
Use GTM in another assistant
- How to Connect ChatGPT to GTM
- How to Connect Claude to GTM
- How to Connect Codex to GTM
- How to Connect Grok Build to GTM
Connect another Google source to Claude Code
Official setup references
- Anthropic's Claude Code MCP, scopes and authentication guide
- Google's Tag Manager Preview and debugging guide
Setup references checked on November 12, 2026. Menu labels and workspace policies can change; use the linked vendor guidance for your account. For LoomaScale's supported workflows, see the documentation hub.
