AliasMode integrations
Connect profile control and browser automation.
Use the AliasMode Local API for supported AdsPower-compatible operations, then attach Playwright over CDP to automate the persistent browser session.
Automation integrations
Local API and browser automation.
AI agent clients
Give coding agents and assistants controlled access to real browser profiles.
Register the AliasMode local stdio MCP server in Claude Code with one command, verify the tool list, and drive persistent browser profiles from chat.
Open →IntegrationCodex CLIAdd the AliasMode MCP server to Codex CLI over local stdio, verify the generated config.toml entry, and automate persistent browser profiles from the terminal.
Open →IntegrationOpenClawRegister the AliasMode MCP server in OpenClaw over local stdio so the assistant can open persistent browser profiles and run Playwright actions on Windows.
Open →IntegrationHermesRegister the AliasMode MCP server in the Hermes agent over local stdio and let it create, open, and automate persistent AliasMode browser profiles.
Open →IntegrationClaude.aiAdd your pinned AliasMode Remote MCP URL as a Claude.ai custom connector, approve access with OAuth, and drive Windows browser profiles from the web.
Open →IntegrationChatGPTAdd AliasMode to ChatGPT as a custom MCP connector with OAuth or a bearer connector and run browser profiles plus Playwright actions from chat.
Open →Migration
Bring existing profiles into AliasMode.
AliasMode Local API: AdsPower-compatible subset
Keep supported profile, group, browser-control, cookie, cache, and CDP workflows while moving them to a loopback AliasMode endpoint.
Playwright over CDP
Start a selected AliasMode profile through the Local API and connect Playwright to response.data.ws.puppeteer. The automation works in the same persistent session an operator can open manually.
Bulk profile import
Moving from AdsPower, GoLogin, Multilogin, or Dolphin Anty? Export the profiles to a text file and import them all into AliasMode in one step.
Local by default
The API listens on 127.0.0.1:50400 by default. Keep it on loopback and treat CDP endpoints as operational access to the active profile.