AdsPower LocalAPI

The AdsPower LocalAPI MCP Server lets you manage and automate AdsPower browser instances through a Model Context Protocol (MCP) client. It enables you to start browsers, create new profiles with fingerprint configurations, manage cookies, and organize browsers into groups for streamlined testing and automation.

How to use

Use an MCP client to interact with the AdsPower LocalAPI MCP server. You can issue commands to create browsers, open them, update fingerprint settings, manage groups, and retrieve lists of browsers. This enables you to automate browser provisioning and session management as part of your AI-assisted workflows.

How to install

Prerequisites include AdsPower and Node.js version 18 or greater.

Install for macOS/Linux with the following MCP server configuration snippet ready to place in your Claude Desktop config.

{
  "mcpServers": {
    "adspower_local_api": {
      "command": "npx",
      "args": ["-y", "local-api-mcp-typescript"]
    }
  }
}

Install for Windows with the following MCP server configuration snippet ready to place in your Claude Desktop config.

{
  "mcpServers": {
    "adspower_local_api": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "local-api-mcp-typescript"]
    }
  }
}

Alternatively, you can add the server to Claude Desktop's configuration from the development flow described here. The server can be started by running the built TypeScript project through Node.

Development

Clone the repository, install dependencies, and build the project to run a local MCP server.

# git clone 
git clone https://github.com/AdsPower/local-api-mcp-typescript.git

# install package
cd local-api-mcp-typescript && npx pnpm i

# build
npm run build

After building, add the server to your claude_desktop_config.json to run the local server via Node against the built index.

"mcpServers": {
  "adspower_local_api": {
        "command": "node",
        "args": [
            "<Replace Your Project Path>/local-api-mcp-typescript/build/index.js"
        ]
    }
}

Additional configuration and notes

The server exposes a set of tools to manage AdsPower browsers. You can open, close, create, update, delete browsers, and manage groups and applications through the MCP interface.

Tools

The MCP server supports a collection of actions that you can call to control browsers and groups.

Available tools

open_browser

Open the AdsPower browser instance. Inputs include serialNumber and userId to specify which browser to open.

close_browser

Close a running AdsPower browser. Input is the userId of the target browser.

create_browser

Create a new AdsPower browser with options for group, domain, open URLs, cookies, user credentials, system, name, country, fingerprint settings, and proxies.

update_browser

Update an existing AdsPower browser with the same options as create_browser, plus the userId to identify which browser to update.

delete_browser

Delete one or more browsers by providing an array of userIds.

get_browser_list

Retrieve a list of browsers with optional filters like groupId, size, id, serialNumber, and sorting preferences.

get-opened_browser

Get the list of currently opened browsers. No inputs are required.

move_browser

Move one or more browsers to a target group by supplying groupId and an array of userIds.

create_group

Create a new browser group with a name and optional remark.

update_group

Update an existing browser group by groupId with a new name and optional remark (null to clear).

get_group_list

Fetch the list of browser groups with optional name and page size filters.

get-application_list

Get the list of applications with optional page size.