How to connect Claude to AdsPower: local API, profiles and agent permissions
Connecting Claude to AdsPower lets the agent open a profile with an ad account and work inside it. Here is what the setup consists of and how to limit what the agent can do.
Updated: · Meta RDP, agency Meta ad accounts since 2023
Short answer: AdsPower starts browser profiles through a local API on your computer and returns an address for controlling the browser. Claude connects to that API through a tool (an MCP server or a script), opens the right profile and works in it. You limit the agent with a list of allowed profiles and a rule that launches and budgets need your confirmation.
What the setup consists of
- AdsPower with profiles, each with its own fingerprint, proxy and ad account.
- AdsPower local API, enabled in the app settings and available only on your computer.
- A tool for Claude: an MCP server or a script that calls the AdsPower API and hands browser control to the agent.
- Claude in the desktop app or a developer environment where tools are connected.
Steps
- Enable the local API in AdsPower and check that it responds.
- Connect an AdsPower tool to Claude and give it the list of profiles it may use.
- Test on a simple task: open the profile, go to Ads Manager, export yesterday's spend.
- Write down the agent's rules: what it may do alone and what needs confirmation.
What permissions to give
- Access only to profiles with working ad accounts, no personal accounts.
- Reading statistics and building drafts: no confirmation needed.
- Publishing campaigns, changing budgets and top-ups: only after your yes.
Common mistakes
- One profile for several ad accounts: the agent gets confused about where it is working.
- A vague brief: the agent guesses audiences and budget instead of following the task.
- No report: without a daily sheet it is hard to check what the agent did.