Google Ads MCP Server

The materials state there are no required keys or environment variables, and no explicit request for additional sensitive credentials is shown. However, since it claims Google Ads write capabilities, users should still verify whether authentication is indirectly supplied by the host environment or an existing session.

It is expected to connect to the declared remote endpoint {host}. Based on its stated features—ads management, reporting, and bulk mutations—it will likely send account query or change data to that endpoint. The materials do not show a concrete red flag of exfiltration to unrelated or unknown third-party endpoints.

System checks indicate this MCP tool executes code or runs a local process, which is a normal property of this class of tools. The materials do not indicate unusual system privileges or execution behavior beyond the ads-management use case.

Its described capabilities—campaign writes, GAQL reporting, bulk mutation, validation, and previews—imply access to and modification of Google Ads business data. The current materials do not disclose any broad local file access, and no data permissions clearly disproportionate to the stated function are evident.

Positive signals include an official registry listing, an open-source repository, and updates within the last year, giving some auditability. However, the missing README, undeclared license, and very low community adoption (0 stars) limit available security context and external validation, so a caution rating is appropriate.