Skip to main content
Glama
Eswarr11
by Eswarr11

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
scan_pageA

Scan an open browser page and extract all element locators. Supports two connection modes: (1) cdpEndpoint — Chrome DevTools Protocol HTTP URL (e.g. http://localhost:9222). Requires Chrome launched with --remote-debugging-port=9222. Use this when @playwright/mcp is also connected to the same external Chrome. (2) wsEndpoint — Playwright WebSocket URL (e.g. ws://127.0.0.1:PORT/...). Use this if you have the browser WS endpoint from a Playwright browser server. Exactly one of cdpEndpoint or wsEndpoint must be provided. scanName determines the registry file: registry/{scanName}.json. scanMode: interactive (default), testId, or full.

get_registryA

Return the full contents of registry/{scanName}.json — the map of element keys to CSS, XPath, and template locators.

list_registriesB

List all available registry files in the registry/ directory.

get_registry_keysA

Return a lightweight list of element keys with tagName, testId, and confidence — much smaller than the full registry.

get_locatorB

Return a single element locator entry by key from a named registry.

search_registryA

Search a registry by tagName, testId, text, or confidence. Returns matching entries only.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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/Eswarr11/locator-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server