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 a separate Meta Ads read only 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 Ads live Meta Ads live OAuth Read-only Source-labelled
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.
Google Ads and Meta Ads are the live providers for this read-only MCP today. A cross-channel view is a comparison of separately bounded 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 separately selected Meta 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
Enable platform Read
Choose Google Ads and/or Meta Ads. Your Adstudio role remains the boundary.
- 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 and Meta Ads are live today. The MCP compares separate, source-labelled reads; it does not treat provider metrics, currencies, attribution models, or periods as interchangeable.
Nothing. Every current public MCP tool is read-only. It does not create, edit, pause, or delete campaigns, ads, budgets, audiences, or other advertising objects.
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 workspaces you are a member of now and in the future. Platform Read permission applies across those memberships and never exceeds your Adstudio role.
Adstudio MCP
Bring accountable answers into the conversation.
Connect once, choose the account you mean, and keep the source context attached to every result.