Connect Claude Code, Cursor, VS Code, Codex or Claude Desktop to TrackingCoder. Your assistant scans the site, generates the GA4 and ad conversion tracking, pushes it into your Google Tag Manager workspace, answers questions about your monitoring and exports client reports. You approve the cost. You publish.
Works with Claude Code · Claude Desktop · Cursor · VS Code · OpenAI Codex
50-second tour: connect, scan, approve and generate, push to GTM, ask the monitoring, export a report.
Ten tools. The same engine as the app, with the same credits, the same Google connection and the same limits.
Platform, page builder, form plugin, e-commerce stack, the pixels already installed and what is worth tracking. Free.
scan_site
GA4 events, Google Ads, Meta, LinkedIn and Microsoft conversions, with Consent Mode v2. The assistant quotes the credits and waits for your yes.
generate_tracking
Tags, triggers and variables land in the workspace you name as unpublished changes, like the app's one-click button. You preview and publish.
push_to_gtm
How many form submissions this week? From which traffic sources? Is the purchase goal on track? Live answers from TC Pro monitoring.
get_monitoring
The branded client report for a site, or a consent report for any URL, as a PDF link valid 24 hours. Forward it as it is.
export_report
What fires before the cookie banner is touched, whether Consent Mode v2 is set up, which pixels a site runs. Free, on any public site.
check_consent
A key, one config entry, then you just ask.
On TC Pro, open Account, API keys, name the key after the machine it lives on, copy it once. Revoke it any time.
Claude Code is one command; the others take one entry in their MCP config, with the key as a bearer token. Each guide below has the exact file.
"Scan example.com and set up form tracking on GA4." The assistant quotes the credits, waits for your yes, generates, and pushes to the workspace you name.
Claude Code
claude mcp add --transport http trackingcoder https://trackingcoder.com/api/mcp --header "Authorization: Bearer tc_live_YOUR_KEY"
Plain English. The assistant picks the tool, quotes any cost, and waits for your yes.
Scan example.com and tell me what we can track for leads.
Set up form submissions and phone clicks on GA4 G-ABC123, with Consent Mode v2.
Generate the purchase conversion for Google Ads AW-123456789 label AbCdEf and for Meta pixel 1234567890. Quote the total first.
Push both to the Production workspace of GTM-ABC1234.
How many form submissions did example.com get this week, and from which traffic sources?
Export the client report for example.com for last month as a PDF.
Check whether competitor.com fires tracking before consent.
Agents make mistakes. These are the rails that keep a mistake cheap.
Keys work from the first paid month and pause the moment a subscription lapses. The trial does not include the API.
Generation refuses to run without an explicit confirm flag, and the assistant is instructed to quote scenario, channel, ID and cost first.
A push creates unpublished workspace changes. A version goes live only when a person presses Publish in GTM.
100 scans, 40 consent checks, 50 generations, 30 pushes, 20 reports, 60 calls a minute. Enough for real work, not enough for an expensive mistake.
Every tool call shows on your account with the key that made it. Revoke a key and anything using it stops at once.
Billing, buying credits, key and team management, and the IDs in your vault are not exposed to any assistant.
The config file, the prompts and the checks for each assistant.
A Model Context Protocol server at trackingcoder.com/api/mcp that gives AI assistants ten tools: scan a site, list what can be tracked and what it costs, generate tracking for an event and channel, list your Google Tag Manager containers, push a generation into a workspace, read your monitoring data, export reports, check your balance, check consent and detect pixels. It works with Claude Code, Claude Desktop, Cursor, VS Code and Codex, and with your own code through the same API.
TC Pro subscribers, from the first paid month. Create an API key under Account, API keys, and add the server to your assistant with the key as a bearer token. The free trial unlocks every other Pro feature but not the API.
In credits, from the same pool as the app: usually 1 credit per event per channel, plus 1 per advanced parameter and 1 for Consent Mode v2. TC Pro includes 10 credits a month and 15% off packs. Scans, consent checks, pushes, monitoring questions and reports cost no credits. The assistant cannot buy anything; when the pool is empty it points you to the app.
No. push_to_gtm places tags, triggers and variables in the workspace you name as unpublished changes, after you confirm the target. You open Preview, test, and press Publish in GTM yourself. It needs Google connected once in the TrackingCoder app, with the Tag Manager permission only.
For sites monitored with TC Pro: events per scenario and channel for any range, conversion rates against first-party visits, the traffic sources behind the events, daily volume, goals and the performance score, plus the workspace overview across all sites. It reads the same data as your dashboard.
As a link valid for 24 hours, unguessable, that opens the PDF (or the printable page). The client report uses your workspace's white-label branding; the consent report is written for the developer who has to fix the site. Ask for the HTML too and the assistant can save it as a file.
It is built for that. Spending and pushing both require an explicit confirmation, nothing is ever published, each key has daily caps and a per-minute limit, every call is logged, and billing, keys, team settings and the ID vault are not exposed at all. Revoke a key and it stops immediately.
Subscribe to TC Pro, create a key, paste one line into your assistant, and ask for the first scan. Nothing is spent and nothing is published without you.