|

Google Open-Sources an MCP Server for the Google Ads API, Bringing LLM-Native Access to Ads Data

ByRicardo

Google has open-sourced a Model Context Protocol (MCP) server that exposes read-only entry to the Google Ads API for agentic and LLM functions. The repository googleads/google-ads-mcp implements an MCP server in Python that surfaces two instruments right this moment: search (GAQL queries over Ads accounts) and list_accessible_customers (enumeration of buyer assets). It contains setup through pipx, Google Ads developer tokens, OAuth2 scopes (https://www.googleapis.com/auth/adwords), and Gemini CLI / Code Assist integration via a regular MCP consumer configuration. The venture is labeled “Experimental.”

So, why it issues?

MCP is rising as a typical interface for wiring fashions to exterior programs. By transport a reference server for the Ads API, Google lowers the integration price for LLM brokers that want marketing campaign telemetry, finances pacing, and efficiency diagnostics with out bespoke SDK glue.

How it really works? (developer view)

  • Protocol: MCP standardizes “instruments” that fashions can invoke with typed parameters and responses. The Ads MCP server advertises instruments mapped to Google Ads API operations; MCP purchasers (Gemini CLI/Code Assist, others) uncover and name them throughout a session.
  • Auth & scopes: You allow the Google Ads API in a Cloud venture, get hold of a developer token, and configure Application Default Credentials or the Ads Python consumer. Required scope is adwords. For manager-account hierarchies, set a login buyer ID.
  • Client wiring: Add a ~/.gemini/settings.json entry pointing to the MCP server invocation (pipx run git+https://github.com/googleads/google-ads-mcp.git google-ads-mcp) and cross credentials through env vars. Then question through /mcp in Gemini or by prompting for campaigns, efficiency, and many others.

Ecosystem sign

Google’s server arrives amid broader MCP adoption throughout distributors and open-source purchasers, reinforcing MCP as a practical path to agent-to-SaaS interoperability. For PPC and development groups experimenting with agentic workflows, the reference server is a low-friction method to validate LLM-assisted QA, anomaly triage, and weekly reporting with out granting write privileges.

Key Takeaways

  • Google open-sourced a read-only Google Ads API MCP server, showcasing two instruments: search (GAQL) and list_accessible_customers.
  • Implementation particulars: Python venture on GitHub (googleads/google-ads-mcp), Apache-2.0 license, marked Experimental; set up/run through pipx and configure OAuth2 with the https://www.googleapis.com/auth/adwords scope (dev token + elective login-customer ID).
  • Works with MCP-compatible purchasers (e.g., Gemini CLI / Code Assist) so brokers can challenge GAQL queries and analyze Ads accounts via natural-language prompts.

Conclusion

In sensible phrases, Google’s open-sourced Google Ads API MCP server offers groups a standards-based, read-only path for LLM brokers to run GAQL queries towards Ads accounts with out bespoke SDK wiring. The Apache-licensed repo is marked experimental, exposes search and list_accessible_customers, and integrates with MCP purchasers like Gemini CLI/Code Assist; manufacturing use ought to account for OAuth scope (adwords), developer token administration, and the data-exposure caveat famous in the README.

Check out the GitHub Page and technical blog. Feel free to take a look at our GitHub Page for Tutorials, Codes and Notebooks. Also, be happy to comply with us on Twitter and don’t overlook to be a part of our 100k+ ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well.

The submit Google Open-Sources an MCP Server for the Google Ads API, Bringing LLM-Native Access to Ads Data appeared first on MarkTechPost.

Similar Posts