01
Start with the campaign behind the number
Read a selected Google Ads account, then move into campaigns, ad groups, ads, and other child entities when the answer needs more context.
Google Ads MCP
Trace every Google Ads result to the work behind it.
Ask an AI client to inspect a selected Google Ads account, then trace performance into campaign, ad group, ad, and creative context. Bring in Meta, TikTok or any other channel when the wider picture helps.
Selected Google Ads account
01
Campaign
02
Ad group
03
Ad / creative
Separate Meta context lane
Meta Ads is a separate selected account read, never a combined total.
Google, Meta and TikTok One sign-in You choose the access Source-labelled
Pick your AI
Connect Google Ads to the AI you use.
Google Ads, in its own terms
A result is only useful when you can follow its shape.
Google Ads has its own account hierarchy and measurement context. Adstudio keeps that context attached while an authorized AI client follows the selected account from a question to the entities and creatives behind it.
The same connection covers Meta Ads and TikTok Ads. A cross-channel view compares separate source reads, never a hidden combined total.
Grounded work, less context switching
Context that survives the question.
02
Keep Google reporting details in view
A bounded read carries its account, period, currency, attribution, freshness, truncation, and unresolved coverage where relevant.
03
Compare without pretending it is one dataset
Place a Meta Ads or TikTok Ads result beside Google Ads context without claiming their metrics are interchangeable.
Connection, with boundaries
Three deliberate steps.
A useful answer starts with a connection whose scope is clear.
- 01
Create a personal connection
In Adstudio Settings → MCP, create your personal connection.
- 02
Choose the access
Pick Read only or Read and write. Your Adstudio role stays the limit.
- 03
Select before you ask
Discover accounts, then explicitly name the workspace, platform, and account for a scoped read.
FAQ
Google Ads MCP, without the fine-print surprise.
Use the public MCP endpoint, https://useadstudio.com/api/mcp, in your compatible AI client and complete OAuth. Start with account discovery before an account-scoped question.
Google Ads, Meta Ads (Facebook and Instagram) and TikTok Ads. Answers stay separate, source-labelled reads: currencies, attribution models and periods are never mixed into one invented number.
You decide. Choose Read only or Read and write in Adstudio Settings → MCP. With Read and write, changes happen only where Adstudio has a verified way to make them, and only in workspaces where you are an admin.
Start with account discovery, then explicitly choose one workspace, platform, and account for every scoped call. The server never guesses an account on your behalf.
A personal connection reaches the workspaces you are a member of, now and in the future. It never goes beyond your own role in each one, and turning MCP off in Settings ends every client's access at once.
Adstudio MCP
Bring accountable answers into the conversation.
Connect once, choose the account you mean, and keep the source context attached to every result.