Skip to main content
Glama
AdsPower

AdsPower LocalAPI MCP Server

Official
by AdsPower

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
open-browserD

Open the browser, both environment and profile mean browser

close-browserC

Close the browser

create-browserD

Create a browser

update-browserD

Update the browser

delete-browserC

Delete the browser

get-browser-listC

Get the list of browsers

get-opened-browserB

Get the list of opened browsers

move-browserC

Move browsers to a group

create-groupC

Create a browser group

update-groupC

Update the browser group

get-group-listC

Get the list of groups

get-application-listC

Get the list of applications

connect-browser-with-wsC

Connect the browser with the ws url

open-new-pageC

Open a new page

navigateC

Navigate to the url

screenshotC

Get the screenshot of the page

get-page-visible-textB

Get the visible text content of the page

get-page-htmlB

Get the html content of the page

click-elementC

Click the element

fill-inputC

Fill the input

select-optionD

Select the option

hover-elementD

Hover the element

scroll-elementC

Scroll the element

press-keyD

Press the key

evaluate-scriptD

Evaluate the script

drag-elementD

Drag the element

iframe-click-elementC

Click the element in the iframe

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.8/5.0

Scored across 27 tools

Disambiguation4/5

Most tools have distinct purposes, such as create-browser vs. open-browser, but some overlap exists, like get-browser-list and get-opened-browser, which could cause confusion. The descriptions help clarify, but the boundaries between these list tools are not perfectly clear.

Naming Consistency5/5

All tool names follow a consistent verb-noun pattern with hyphens, such as create-browser, get-browser-list, and navigate. There are no deviations in style or convention, making the naming highly predictable and readable throughout the set.

Tool Count3/5

With 27 tools, the count is borderline high for a browser automation server, as it may feel heavy and complex for agents to navigate. However, given the domain's scope covering browser management, groups, and page interactions, it is not extreme but could benefit from consolidation.

Completeness5/5

The tool set provides comprehensive coverage for browser automation, including CRUD operations for browsers and groups, navigation, element interactions, and page content retrieval. There are no obvious gaps, and the surface supports full lifecycle management and interaction workflows.

Maintenance

ActivityStale
ResponsivenessSlow