37 live GTM tools for containers, workspaces, tags, triggers, and version publishing from chat, inside the same server that runs GA4, Google Ads, Meta, and LinkedIn. Named shortcuts for Google Ads conversion, GA4 event, and form tracking setup.
PaidSync is a Google Tag Manager MCP server that creates tags, triggers, and variables and publishes container versions from Claude, ChatGPT, and Gemini. 37 tools cover the full lifecycle (create, update, delete workspaces, tags, triggers, variables; preview, version, publish, sync) plus named shortcuts for Google Ads conversion tracking, GA4 events, and form tracking. Every write is held for your confirmation. Free at $0 for 15 tasks a month, Pro from $99/mo. Pairs with the GA4 MCP and Google Ads MCP for end-to-end conversion tracking in one conversation.
An MCP server turns an API into typed tools an AI assistant can call. Connect one to Claude or ChatGPT and "add a purchase conversion tag to the marketing site's container, wire it to the thank-you page, publish it, and confirm it fires" becomes something the assistant can check, propose, and, once you approve, execute against the container. This page covers PaidSync's GTM surface in full: the 37 tools, the workspace + version publish flow, the named setup shortcuts, and how it fits with the GA4 and Google Ads MCPs in the same server.
It is written for both audiences. Analysts and marketers who want to change GTM from chat without opening the container UI, and agent builders who want to know the protocol surface before wiring it into a workflow. Each section is labeled.
What a GTM MCP server does
Three things, in practice. It reads, so the assistant can list containers, workspaces, tags, triggers, variables, versions, and environments, and it can audit a container. It writes, so tags, triggers, variables, and workspaces can be created, updated, and deleted from conversation. And it publishes, so a workspace can be previewed, versioned, and pushed live through the same conversation.
The bit most GTM MCP servers do not cover: the setup shortcuts. Because conversion tracking is where GTM actually earns its keep, PaidSync exposes named tools (setup_google_ads_conversion, setup_ga4_event, setup_form_tracking) that sequence the underlying tag, trigger, and variable creation into one confirmed step, then hand off to preview_gtm_workspace and publish_gtm_version for the ship.
All 37 GTM tools by category
PaidSync's live server exposes 37 GTM tools (server total 430+ across 13 platforms). The table names the operational core; the full current catalog is discoverable live from any session via paidsync_context with include_tools:['gtm'].
| Category | Named tools |
|---|---|
| Account and container discovery | connect_gtm, gtm_auth_status, list_gtm_accounts, list_gtm_containers, get_gtm_container, get_gtm_container_snippet, list_gtm_workspaces, get_gtm_workspace_status, audit_gtm_container |
| Tag, trigger, variable read | list_gtm_tags, get_gtm_tag, list_gtm_triggers, get_gtm_trigger, list_gtm_variables, list_gtm_builtin_variables |
| Version read | list_gtm_versions, get_gtm_version_live, list_gtm_environments |
| Workspace lifecycle | setup_gtm, create_gtm_workspace, delete_gtm_workspace, sync_gtm_workspace |
| Tag lifecycle | create_gtm_tag, update_gtm_tag, delete_gtm_tag, revert_gtm_tag |
| Trigger lifecycle | create_gtm_trigger, update_gtm_trigger, delete_gtm_trigger |
| Variable lifecycle | create_gtm_variable, update_gtm_variable, delete_gtm_variable, enable_gtm_builtin_variables |
| Named setup shortcuts | setup_google_ads_conversion, setup_ga4_event, setup_form_tracking |
| Preview and publish | preview_gtm_workspace, create_gtm_version, publish_gtm_version |
Four of these carry most of the operational work. setup_google_ads_conversion sequences a Google Ads conversion tag, its trigger, and the necessary variables from a natural-language ask like "add a purchase conversion for the checkout page". setup_ga4_event creates a GA4 Event tag with the right trigger and dataLayer variable. audit_gtm_container surfaces broken tags, orphan variables, and misconfigured triggers before you touch anything. And the publish flow (preview_gtm_workspace, create_gtm_version, publish_gtm_version) means shipping tags is a chat approval, not a UI walk.
Publish GTM changes from a chat window
The practical shape of a Tuesday afternoon on PaidSync's GTM stack looks like this. You want a purchase conversion added end-to-end. You ask "add a Google Ads purchase conversion firing on the /thanks page, and mark it as a conversion in GA4". The assistant proposes: create the GA4 event via create_gtm_tag, the Google Ads conversion via setup_google_ads_conversion, the two triggers, the necessary dataLayer variable via create_gtm_variable, then preview_gtm_workspace so you can smoke-test in preview, then create_gtm_version and publish_gtm_version to ship. Every step is a draft you approve.
Because GA4 and Google Ads are in the same server, the follow-up "mark that event as a conversion in GA4 and import it in Google Ads for tROAS bidding" runs in the same conversation. That composite (PaidSync GTM MCP + GA4 MCP + Google Ads MCP) is how conversion tracking becomes one prompt instead of a Monday-morning ticket.
Trust is procedural, not promissory. Nothing applies without your confirmation, previews show the exact planned change first, and destructive operations require a second explicit confirmation. Sessions can be revoked at any time.
Connect a GTM container to Claude, ChatGPT, or Gemini and publish the first change in minutes.
Start free, 15 tasks, no card See the GA4 half of the setupThe protocol surface behind the 37 tools
PaidSync is one MCP endpoint covering 13 platforms; details on the MCP server page. To keep client context small, tools/list returns a lean starter set. The full catalog is discovered at runtime through paidsync_context, which returns the active account, connected platforms, and the grouped tool catalog (include_tools:['gtm'] returns the exact GTM tool names), and executed through paidsync_exec. That two-call pattern means an agent can enumerate and invoke all 37 GTM tools without a 430-tool schema payload sitting in every conversation.
Safety is enforced server-side. Writes are approval-gated, most mutation tools accept dry_run for a no-op preview, and destructive operations (delete workspace, delete tag, delete trigger, delete variable) require confirm_destructive. Because GTM writes land in a workspace first, preview_gtm_workspace gives an agent an inspectable outcome before publish_gtm_version makes it live. For discovery and verification, the domain publishes OAuth authorization-server and protected-resource metadata (RFC 8414 and RFC 9728), an MCP server card, agent-auth.json, security.txt, and a Content-Signal directive.
PaidSync vs community GTM MCP servers
Open-source GTM MCP servers on GitHub typically wrap parts of the GTM API for querying containers, tags, or triggers. They are self-hosted, single-container, and full publish workflow plus named conversion-tracking shortcuts are rarely first-class capabilities. Zapier does not maintain a first-class Google Tag Manager app, so Zapier is not a practical MCP path for GTM work. PaidSync is hosted, covers the full lifecycle end-to-end, and includes the setup shortcuts that turn "add a conversion" into one conversation instead of six.
| Dimension | PaidSync | Community GTM MCP | Zapier |
|---|---|---|---|
| GTM tools | 37 named, full lifecycle | Read plus light editing subsets | No first-class GTM app |
| Create and update tags, triggers, variables | Yes | Varies by project | Not the model |
| Preview and publish workflow | Yes, preview_gtm_workspace, create_gtm_version, publish_gtm_version | Rare | No |
| Named setup shortcuts | setup_google_ads_conversion, setup_ga4_event, setup_form_tracking | No | No |
| Container audit | audit_gtm_container | No | No |
| Pairs with GA4 and Google Ads in the same session | Yes, /ga4-mcp + /google-ads-mcp | Separate servers if any | Zapier apps, not MCP-native |
| Approval gates on writes | Yes, every write held for confirmation | Not applicable | Not applicable |
| Hosted vs self-hosted | Hosted | Self-hosted | Hosted |
| Price | Free $0 (15 tasks), Pro from $99/mo | Free, self-hosted | Free tier plus paid Zapier plans |
Quick verdict.
You want a free self-hosted GTM MCP for personal container queries: a community GTM MCP on GitHub.
You want to add conversion tags, publish container versions, and pair with GA4 plus Google Ads from chat: PaidSync. The publish flow and setup shortcuts are the point.
What this does not do
Stated plainly, because scoping a tool accurately beats overselling it.
- No server-side GTM container management. The tool set targets web containers today.
- No user or permission management. Access control stays in the GTM admin.
- No arbitrary custom-HTML tag writing beyond what the API allows. Custom-template installs from the Community Gallery are done in the GTM UI.
- No unattended writes. Every configuration change and every publish waits for your confirmation.
Pricing
Every plan includes all 13 platforms and there is no per-container or per-platform charge. Every tool call counts as one task, whether it lists tags or publishes a version. Full detail at paidsync.ai/pricing.
| Plan | Price | Included |
|---|---|---|
| Free | $0/mo | 15 tasks a month, no card required |
| Pro | From $99/mo | 600 tasks ($99), 1,200 tasks ($149), or 4,000 tasks ($199) |
| Team | From $249/mo | 5 seats, 6,000 shared tasks |
| Done For You | Custom | Fully managed paid media and measurement |
Put 37 GTM tools, plus GA4 and Google Ads in the same session, in front of your AI assistant today.
Frequently asked questions
What is a GTM MCP server?
An MCP (Model Context Protocol) server exposes Google Tag Manager API actions as typed tools that AI assistants like Claude, ChatGPT, and Gemini can call. A GTM MCP lets the assistant list containers, workspaces, tags, triggers, and variables; create, update, and delete each of those; preview and publish workspace versions; and manage environments and built-in variables, all through conversation instead of clicks in GTM. PaidSync's GTM surface is 37 tools with write access.
How many GTM tools does PaidSync have?
37 live GTM tools, inside a server of 430+ tools across 13 platforms. The set covers discovery, tag/trigger/variable read, version read, workspace lifecycle, tag lifecycle, trigger lifecycle, variable lifecycle, named setup shortcuts (Google Ads conversion, GA4 event, form tracking), and the preview/publish flow.
Can PaidSync publish a GTM container from chat?
Yes. The publish flow lives in the tool set: preview_gtm_workspace to test the changes, create_gtm_version to snapshot them, publish_gtm_version to push them live, and sync_gtm_workspace to bring in outside changes before publishing. Every write step waits for your confirmation, and destructive operations require an explicit confirm_destructive step.
How is PaidSync GTM MCP different from community GTM MCP servers?
Open-source GTM MCP servers on GitHub typically wrap parts of the GTM API for querying and light editing. They are self-hosted, single-container, and full publish workflow plus named conversion-tracking shortcuts are rarely first-class. PaidSync is hosted, covers the full lifecycle end-to-end, and includes named shortcuts for Google Ads and GA4 conversion tracking.
Is it safe to give an AI write access to a live GTM container?
PaidSync never applies a change without your confirmation. Every write is approval-gated in chat, most write tools support a dry_run preview, and destructive operations require an explicit confirm_destructive step. GTM writes land in a workspace first, so preview_gtm_workspace lets you see the outcome before create_gtm_version and publish_gtm_version make it live.
How much does the PaidSync GTM MCP cost?
Free is $0 for 15 tasks a month with no card. Pro starts at $99 per month for 600 tasks, with 1,200 tasks at $149 and 4,000 at $199. Team starts at $249 per month for 5 seats and 6,000 shared tasks. Done For You is custom-priced fully managed paid media and measurement.