---
title: "Claude Google Ads Integration via MCP | Adscriptly"
description: Connect Claude to Google Ads through the hosted Adscriptly MCP server, OAuth account context, read tools, and scoped write approvals.
image: https://adscriptly.com/opengraph-image.png
canonical: https://adscriptly.com/integrations/claude-google-ads
source: https://adscriptly.com/llms.txt
---
Google Ads + Claude

Hosted MCP AI connector

# Use Google Ads account data in Claude with scoped permissions.

Add Adscriptly as a custom connector in Claude, sign in through Adscriptly OAuth, and choose the Google Ads account for the conversation. Claude can begin with read-only analysis; supported writes remain separated by scope and approval.

[Open MCP setup guide](https://adscriptly.com/docs/mcp) [See all integrations](https://adscriptly.com/integrations) GA

Ad account

Google Ads

+ C

AI client

Claude

Intended outcome

Ask Claude account-specific Google Ads questions with a visible permission boundary.

Connection scope

This is an Adscriptly custom connector for Claude. It is not an Anthropic or Google partnership.

What the connection does

## Control what Claude can access in Google Ads.

01

### One hosted server URL

Connect the remote Adscriptly MCP endpoint instead of running a local advertising connector or handling platform credentials in the chat client.

02

### Adscriptly OAuth sign-in

The client redirects to Adscriptly for authorization, so the resulting access stays tied to the authenticated workspace.

03

### Google Ads account context

Use account discovery and structured Google Ads tools so Claude can ground answers in the selected workspace.

04

### Separate read and write scopes

Supported write tools are exposed separately and should run only after Claude presents the intended account impact and receives approval.

Data flow

## Know what moves between systems.

Google Ads Adscriptly logic Claude Google Ads

Authorized Google Ads account

Adscriptly logic

Authenticated workspace and account selection

Claude

Claude tool context

Google Ads

Natural-language request

Adscriptly logic

Adscriptly tool selection and schema validation

Claude

Structured tool call

Google Ads

Google Ads response

Adscriptly logic

Normalize the result for the conversation

Claude

Answer with account evidence

Google Ads

Approved write request

Adscriptly logic

Explicit write scope and approval boundary

Claude

Scoped account change

Setup

## Connect Claude to the hosted Adscriptly MCP server.

1. 01

   ### Copy the server URL

   Use https://adscriptly.com/api/mcp as the remote MCP server address.
2. 02

   ### Add it to Claude

   In Claude, open Settings, then Connectors, add a custom connector, and paste the Adscriptly MCP server URL.
3. 03

   ### Sign in to Adscriptly

   Complete the Adscriptly OAuth prompt and authorize the workspace the client should use.
4. 04

   ### Choose a Google Ads account

   Start with account discovery, select the intended Google Ads account, and use read-only analysis before any supported write is proposed.

Connection controls

## Review the account, permission scopes, and write approval settings.

- OKThe AI client does not receive the underlying advertising-platform credential.
- OKAccount context must resolve before an account-specific tool runs.
- OKWrite tools use a separate scope and should follow an explicit approval.
- OKThe Adscriptly OAuth token can be revoked.

Related integrations

Related workflows

[Google Ads + AI clients Hosted MCP / AI connector View](https://adscriptly.com/integrations/google-ads-mcp) [Google Ads + Slack Native Slack app / Team reporting View](https://adscriptly.com/integrations/google-ads-slack-reports)

Product and guides

[Adscriptly MCP setup guide View](https://adscriptly.com/docs/mcp) [Google Ads optimization software View](https://adscriptly.com/google-ads-optimization-software) [Server-side tracking View](https://adscriptly.com/server-side-tracking)

Integration FAQ

## Before you connect.

What is the Adscriptly Google Ads MCP server URL?+

Use https://adscriptly.com/api/mcp. The hosted endpoint supports OAuth, so compatible clients can redirect you to Adscriptly to authorize access.

Does Claude need my Google Ads password or token?+

No. Connect Google Ads inside Adscriptly and authorize the MCP client through Adscriptly OAuth. The chat client does not need the underlying platform credential.

Can Claude change Google Ads campaigns?+

Supported write tools use a separate write scope. Adscriptly instructs clients to present the intended impact and obtain approval before a write.

Is this an official Google Ads or Claude integration?+

No partnership is implied. This is an Adscriptly-hosted MCP connection that uses the permissions granted to the authenticated Adscriptly workspace and the remote-connector support available in Claude.

Google Ads + Claude

## Use Google Ads account data in Claude.

Add the hosted MCP server, authorize Adscriptly, select the intended ad account, and begin with a read-only question.

[Open MCP setup guide](https://adscriptly.com/docs/mcp) [Get a demo](https://calendly.com/adscriptly/adscriptly-demo)[![](https://img.logo.dev/claude.ai?token=pk_Gqyn4kIpSmSBRdvJf3B-Yw&size=76&format=png) Connect Claude with  
Google & Meta Ads in 1 click ›](https://adscriptly.com/marketing-mcp)