Does Claude Work With Google Ads?

Yes — Claude can work with Google Ads through an MCP (Model Context Protocol) server. Google now provides an official, self-managed server for read-only account discovery and GAQL analysis. NotFair provides a hosted alternative when the work also requires selected-account OAuth access, approval of proposed changes before supported writes, and an operations record for live account actions.

Which Claude products work with Google Ads?

• Claude clients with local MCP support — Google's official server runs over stdio, so it fits clients that can run or reach that local process.
• Hosted MCP-compatible clients — NotFair uses a hosted Streamable HTTP endpoint, so setup does not require local Google Ads API credentials.
• Before connecting — confirm that the particular Claude surface and plan you use support the transport you intend to install. Client capabilities change faster than the Google Ads API itself.

What you need to make it work

• A Google Ads account with at least one active customer ID.
• A Google identity that has access to that account (direct or via a manager / MCC account).
• A Claude surface that supports the MCP transport you selected. Check the current client documentation before installing a local stdio server or a hosted HTTP connector.
• For NotFair's hosted workflow, allow about 5 minutes for the OAuth flow and connector install.

What safety should look like when Claude can write

Read access and write access should not be treated alike. With NotFair, the connected user selects the accounts in scope. Write-capable tools do not run silently: the client presents the proposed action for explicit approval. Applied changes are recorded with who acted, the target, and before/after values; supported changes include undo metadata. That gives an operator something concrete to review before and after an AI-assisted change.

What does not work

• Claude cannot read your Google Ads account by URL or screenshot. Pasting an Ads dashboard URL into Claude does nothing without an MCP connection.
• Claude does not control Google Ads merely by opening a dashboard URL. A browser-driving agent is a separate approach; an MCP connection gives the client structured account data and defined tool calls instead.
• A Claude surface that does not support the selected MCP transport cannot connect to Google Ads through that server. Check the client documentation before troubleshooting the account connection.

How does Claude actually talk to Google Ads?

Claude does not call the Google Ads API directly. It calls the MCP server you configured, which calls Google Ads on your behalf. With Google's official server, that is a local read-only process using your credentials. With NotFair, it is a hosted service that connects the accounts you selected and can require approval for supported writes. In both cases, the server—not Claude itself—owns the Google Ads API interaction.

FAQ