What it does
The server gives an MCP client tools for reading Google Ads data across several client or in-house accounts, and switching the default account without restarting the server. Its tools cover account selection (listing accounts, setting a default, listing accessible customers), spend summaries with period-over-period comparison, campaign inventory and range-based metrics, and query-level reporting on keywords, search terms and ads.
It suits operators who manage more than one ad account and want a single MCP surface for them. Account routing is handled by an account manager in the server, and queries run through shared helpers that include retry logic for API calls.
Setup means installing the package, copying the accounts configuration template and adding your accounts, then registering the server in your MCP client. The publisher lists validation steps that compile the gads module, build the package and check that local documentation links resolve.
Limitations and requirements
The publisher describes this as a beta package (version 0.1.0). Accounts must be defined in the accounts configuration file, which loads OAuth or service-account credentials.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
MCP Google Ads
Multi-account Google Ads MCP: campaigns, keywords, search terms, and ad performance.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it