Google Analytics 4
Admin API writes — audiences, key events, and links — under policy
Your agent configures GA4 properties through the Admin API: audiences, key events, custom dimensions, enhanced measurement, and Google Ads links. Fourteen tools, half of them writes, all of them governed.
$ claude mcp add --transport http ga4 \
https://mcp.getducto.com/ga4
✓ connected — 17 tools
read-only until you set a policy
What your agent does here
Real Google Analytics 4 work, in conversation
Build and maintain audiences
Create, patch, and archive audiences with the exact filter clauses the Admin API supports.
ga4_create_audiencega4_patch_audiencega4_archive_audiencega4_list_audiences
Define what counts as a conversion
Create key events and custom dimensions so reporting matches how your business actually measures.
ga4_create_key_eventga4_list_key_eventsga4_create_custom_dimension
Wire GA4 to Google Ads
Create and inspect Google Ads links, and control enhanced measurement per stream.
ga4_link_google_adsga4_list_google_ads_linksga4_set_enhanced_measurement
Governed writes
How writes are enforced
Admin writes reshape how a property measures, so each one dry-runs as a preview your agent must match before apply. Archiving an audience is flagged destructive and can sit behind approval.
The full request path is on the security architecture page.
Tool reference
Every tool in the ga4 mount
Generated from the running gateway's tool registry — this is the complete list, not a highlight reel.