What AdLoop MCP server does
The AdLoop MCP server brings advertising and measurement data into an MCP-compatible AI client. Its documented integrations include Google Ads, GA4, Google Search Console, Google Merchant Center, PageSpeed Insights, and optional Reddit Ads connectivity for diagnostics. The toolset is aimed at marketing analysis: campaign performance, ad and keyword results, search terms, audience segments, conversion gaps, landing-page behavior, organic search visibility, and product-feed issues.
The AdLoop MCP server also provides discovery tools before reporting begins. You can list accessible Ads accounts, GA4 properties, Search Console sites, and Merchant Center accounts. This is useful when one authenticated identity can reach multiple properties or customer accounts.
How it works
AdLoop runs as an MCP server and calls the relevant provider APIs on behalf of the connected client. GA4 tools support custom reports, realtime reports, event volumes, key events, and property metadata. Google Ads tools return campaign, ad, keyword, search-term, recommendation, Performance Max, audience, demographic, and change-history data. Search Console reporting supports dimensions such as search queries and pages, with paging for larger result sets.
Several tools combine data from more than one system. analyze_campaign_conversions compares Ads campaign results with GA4 sessions and key events, while landing_page_analysis joins ad final URLs with page-level analytics. analyze_page_speed adds Lighthouse and available Chrome User Experience field data to a landing-page investigation. Responses generally include headers, rows, totals, identifiers, status values, or diagnostic insights relevant to the selected report.
The server can run health_check to test OAuth and API connectivity. It reports separate service statuses and provides guidance when a dependency is unavailable. Report validation happens before a GA4 request is sent, so invalid filters or ordering return error details rather than querying the API.
Setup and configuration
The self-hosted project requires Python 3.11 or newer. Installation can use the published package:
The repository also documents a source workflow using uv sync followed by uv run adloop init. Self-hosting requires a Google Cloud project, and the project documentation distinguishes this from AdLoop Cloud, which handles the hosted setup. The self-hosted model keeps data on the machine running the server. Specific environment variable names are not provided in the supplied material, so configuration should follow the repository or linked documentation rather than assumed variables.
Tools and capabilities
The AdLoop MCP server includes these supported areas:
- Discover GA4 properties, Ads accounts, Search Console sites, and Merchant Center accounts.
- Run GA4 standard and realtime reports, inspect events and key events, and list valid dimensions and metrics.
- Review campaign, ad, keyword, search-term, audience, demographic, recommendation, and Performance Max data.
- Inspect negative keyword lists, asset combinations, account changes, and policy-related ad information.
- Query Search Console performance, including clicks, impressions, CTR, and average position.
- Check Merchant Center disapprovals and account-level issues.
- Measure landing-page performance with PageSpeed Insights and connect paid traffic to GA4 outcomes.
Limitations and notes
GA4 realtime results cover the last 30 minutes. Search Console returns up to 25,000 rows per request and may require another call when a continuation value is returned. Merchant Center product-status information can lag by about 30 minutes. PageSpeed runs commonly take 10–30 seconds, and field data may be origin-wide when a specific page lacks enough traffic.
Performance Max reporting does not provide complete channel splits: the API may group traffic under MIXED. Individual PMax asset performance labels are not available; detailed asset combinations are provided instead. Google Ads change history is retained for 30 days. Reddit Ads is checked by health_check only when configured in the supplied tool list.
The project documentation states that changes use a preview and explicit confirmation, but the provided tool descriptions primarily document reporting and analysis operations. Confirm the current write-tool and client behavior in the repository documentation before relying on automated account mutations.