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.
Google Ads + Claude
Hosted MCPAI 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.
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.
Adscriptly OAuth sign-in
The client redirects to Adscriptly for authorization, so the resulting access stays tied to the authenticated workspace.
Google Ads account context
Use account discovery and structured Google Ads tools so Claude can ground answers in the selected workspace.
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 AdsAdscriptly logicClaude
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.
- 01
Copy the server URL
Use https://adscriptly.com/api/mcp as the remote MCP server address.
- 02
Add it to Claude
In Claude, open Settings, then Connectors, add a custom connector, and paste the Adscriptly MCP server URL.
- 03
Sign in to Adscriptly
Complete the Adscriptly OAuth prompt and authorize the workspace the client should use.
- 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.
- The AI client does not receive the underlying advertising-platform credential.
- Account context must resolve before an account-specific tool runs.
- Write tools use a separate scope and should follow an explicit approval.
- The Adscriptly OAuth token can be revoked.
Related integrations
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.
