AdsPower LocalAPI MCP Server
OfficialThe AdsPower LocalAPI MCP Server enables LLMs to interact with and manage AdsPower browser features through an API. Key capabilities include:
Browser Management: Open/close browsers using
userIdorserialNumber, create new browsers with custom configurations, update existing settings, and delete browsersGroup Operations: Create and update browser groups, move browsers between groups, and retrieve group lists
Configuration Control: Configure browser fingerprints, proxies, user agents, country settings, and other advanced parameters
Information Retrieval: Get lists of all browsers, currently opened browsers, groups, and available applications in the system
Allows creation and configuration of browser profiles with Android user agents
Supports configuration of Firefox browser profiles through the browser kernel configuration
Provides control over WebRTC settings in browser profiles, with options for disabling, forwarding, or using proxy/local connections
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AdsPower LocalAPI MCP Servercreate a browser with random fingerprint for testing"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AdsPower Skill & MCP & CLI
adspower-browser Skill
Claude Code/Codex/Cursor/OpenCode/Gemini GL
npx skills add https://github.com/adspower/adspower-browser --skill adspower-browserOpenClaw(小龙虾)
npx clawhub@latest install adspower-browser --forceHermes agent(爱马仕)
hermes skills install https://github.com/AdsPower/adspower-browser/blob/main/skills/adspower-browser --forceRelated MCP server: MCP Salesforce Connector
AdsPower CLI
The AdsPower CLI is completely isolated from the AdsPower client, runs independently, and does not share local caches/kernels, etc. However, the CLI also supports headless mode for operating the AdsPower client.
npm install -g adspower-browser # 安装
ads start -k <KEY> # 启动 adspower
ads stop # 停止 adspower
ads restart # 重启 adspower
ads status # 查询 adspower 运行状态
ads get-browser-list # 获取配置文件列表
... #查看 https://github.com/AdsPower/adspower-browser/blob/main/packages/adspower-browser/README.MDAdsPower client headless mode:
AdsPower Global:
Windows: "AdsPower Global.exe" --headless=true --api-key=your_api_key --api-port=50325
MacOS:"/Applications/AdsPower Global.app/Contents/MacOS/AdsPower Global" --args --headless=true --api-key=your_api_key --api-port=50325
Linux:adspower_global --headless=true --api-key=your_api_key --api-port=50325AdsPower MCP
Claude Code:
claude mcp add adspower-local-api -e PORT="50325" -e API_KEY="your_api_key" -- npx -y local-api-mcp-typescriptCodex:
codex mcp add --env PORT="50325" --env API_KEY="your_api_key" adspower-local-api -- npx -y local-api-mcp-typescriptCursor: Go to Cursor Settings -> MCP -> Add New MCP Server, and then paste the following content:
{
"mcpServers": {
"adspower-local-api": {
"command": "npx",
"args": ["-y", "local-api-mcp-typescript"],
"env": {
"PORT": "50325",
"API_KEY": "your_api_key"
}
}
}
}OpenCode: update ~/.config/opencode/opencode.json
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"adspower-local-api": {
"command": "npx",
"args": ["-y", "local-api-mcp-typescript"],
"env": {
"PORT": "50325",
"API_KEY": "your_api_key"
}
}
}
}How to use?
Requirements
Node version 18 or greater
Version Compatibility
Some APIs are introduced incrementally by AdsPower client version.
If the client has not been upgraded to a version that includes a specific API, requests may return Not found.
When this happens:
Upgrade AdsPower client to the latest patch version first.
Then retry the same command/API.
Port Configuration
The port parameter specifies the AdsPower Local API port. Default is 50325.
Priority order:
Command-line argument
--port(highest priority)Environment variable
PORT(medium priority)Default value
50325(lowest priority)
Examples:
Using command-line argument:
{
"mcpServers": {
"adspower-local-api": {
"command": "npx",
"args": ["-y", "local-api-mcp-typescript", "--port", "50325"]
}
}
}Using environment variable:
{
"mcpServers": {
"adspower-local-api": {
"command": "npx",
"args": ["-y", "local-api-mcp-typescript"],
"env": {
"PORT": "50325"
}
}
}
}Development
# clone
git clone https://github.com/AdsPower/adspower-browser.git
cd adspower-browser
# install (monorepo)
pnpm install
# build all packages
pnpm run buildFor local MCP development, point Claude Desktop to the MCP package:
"mcpServers": {
"adspower-local-api": {
"command": "node",
"args": ["<Replace Your Project Path>/adspower-browser/packages/local-api-mcp/build/index.js"]
}
}Use AdsPower Cli in Docker
copy the /packages/adspower-browser/docker-compose.yml
cd packages/adspower-browser
docker-compose -f ./docker-compose.yml up -d
docker-compose exec adspower-cli /bin/bashAppeared in Searches
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/AdsPower/adspower-browser'
If you have feedback or need assistance with the MCP directory API, please join our Discord server