01
Choose first, then investigate
Make an explicit account selection before an account-scoped read, so the conversation never uses a similarly named account by assumption.
Claude + MCP
Give Claude permissioned access to your ad context.
Connect Adstudio as a custom connector, complete OAuth, and choose the exact workspace, platform, and account before Claude reads. The result remains evidence-rich without crossing the boundary you did not name.
Question
Show the accounts available to me. I will select the exact account before we continue.
Selection required
Workspace: Northstar | Platform: Google Ads | Account: 123-456-7890
Claude can now make one bounded read.
The answer will retain the selected account and its provider details instead of inferring another account.
Google, Meta and TikTok One sign-in You choose the access Source-labelled
Pick a platform
Connect Claude to Google Ads, Meta Ads and TikTok Ads.
Explicit selection is part of the workflow
A good answer starts by knowing which account it is about.
In Claude, add the public Adstudio MCP endpoint through a compatible connector flow and complete OAuth. Start with account discovery, then copy the explicit workspace, platform, and account identifiers into the next request.
Claude connector menus can change. What stays the same: Adstudio covers Google Ads, Meta Ads and TikTok Ads, you choose the access level in Settings → MCP, and a request without scope asks rather than guesses.
Grounded work, less context switching
A better conversation begins with clear scope.
02
Receive a bounded evidence trail
Follow a selected read through provider, period, currency, attribution, freshness, truncation, and unresolved coverage where relevant.
03
Compare sources without hiding their differences
Bring Google Ads, Meta, TikTok and your other accounts into one discussion through separate bounded calls, not a false unified metric.
Connection, with boundaries
Three deliberate steps.
Claude receives a useful answer only after the source account 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
Claude connection, made explicit.
In Claude, open Customize, choose Connectors, then Add custom connector. Enter the public MCP endpoint, complete OAuth, and start with account discovery before a scoped request.
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.