01
OAuth instead of pasted credentials
The client connection is completed through OAuth; the public endpoint URL itself is not a secret or credential.
MCP security
Your accounts. Your rules.
You choose what your AI can do. It never reaches more than you can, and one switch turns it off. Adstudio MCP uses OAuth and a personal connection that follows the workspaces you are a member of now and in the future.
Personal OAuth
Workspace membership
Your access level
Selected account
You choose Read only or Read and write. One switch in Settings → MCP turns access off.
Google, Meta and TikTok One sign-in You choose the access Source-labelled
The connection has visible gates
The endpoint is public. Your permission is not.
OAuth connects the client without asking you to paste an access token into chat. Discover active integrations, then select the workspace, platform, and account for each scoped read.
In Adstudio Settings → MCP you choose Read only or Read and write. Write only applies where Adstudio has a verified way to make the change, and only in workspaces where you are an admin. Turn MCP access off and every connected AI loses access at once. If a returned scope looks wrong, contact Support.
Grounded work, less context switching
Context that survives the question.
02
Never more than you
A personal connection spans workspaces you are a member of now and in the future, but never exceeds your own role in each one.
03
Provenance makes the boundary reviewable
Responses name provider and selected account, with period, currency, attribution, freshness, truncation, and unresolved coverage where relevant.
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
Security and access, plainly stated.
Turn off MCP access in Adstudio Settings → MCP. Every connected AI loses access at once. Then remove the connector from your AI client. If a returned scope looks wrong, contact Support.
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.