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 + AI clients
Hosted MCPAI connector
Connect Google Ads to any MCP-compatible AI client.
Use one hosted Adscriptly MCP endpoint to bring authenticated Google Ads account context into compatible remote-MCP clients. Start with account discovery and read-only analysis; supported writes use a separate scope and approval boundary.
GA
Ad account
Google Ads
Ac
AI client
AI clients
Intended outcome
Ask account-specific questions and run permissioned advertising workflows without placing Google Ads credentials inside the chat client.
Connection scope
Google also publishes official Google Ads MCP resources. This page covers the Adscriptly-hosted cross-client server, account context, and approval model.
What the connection does
Control what AI clients 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
Discover accessible accounts and use Adscriptly tools for account-specific reporting, keyword research, and analysis.
Separate read and write scopes
Supported Google Ads write tools use a separate write scope and require the client to present the intended impact before execution.
Data flow
Know what moves between systems.
Google AdsAdscriptly logicAI clients
Google Ads
Authorized Google Ads account
Adscriptly logic
Authenticated workspace and account selection
AI clients
AI clients tool context
Google Ads
Natural-language request
Adscriptly logic
Adscriptly tool selection and schema validation
AI clients
Structured tool call
Google Ads
Google Ads response
Adscriptly logic
Normalize the result for the conversation
AI clients
Answer with account evidence
Google Ads
Approved write request
Adscriptly logic
Explicit write scope and approval boundary
AI clients
Scoped account change
Setup
Connect AI clients 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 AI clients
Add the server as a remote or custom MCP connector. The exact menu name depends on the client.
- 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 AI clients 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 AI clients 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 AI clients 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 AI clients.
Google Ads + AI clients
Use Google Ads account data in AI clients.
Add the hosted MCP server, authorize Adscriptly, select the intended ad account, and begin with a read-only question.
