LocatorLabs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Name | Description |
|---|---|
| get_locatorsB | Get all possible Playwright locators for a specific element on a webpage. Returns ranked locators with reliability scores. Use this when user asks for locators for a specific element. |
| analyze_pageB | Analyze an entire webpage and return all interactive elements with their best locators. Use this to understand page structure or get all elements at once. |
| generate_page_objectC | Generate a complete Page Object Model class for a webpage. Supports Playwright (TypeScript/JavaScript/Python) and Selenium (Java/Python/C#). |
| run_testB | Execute a Playwright test with given steps and return pass/fail results. Use this to actually run and verify tests in a real browser. |
| generate_testB | Generate a Playwright test script from test steps. Returns executable code that can be saved and run independently. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct, non-overlapping purpose: analyze_page for page-wide element analysis, generate_page_object for POM generation, generate_test for test script creation, get_locators for element-specific locator retrieval, and run_test for test execution. The descriptions clearly differentiate their scopes (e.g., get_locators is for specific elements vs. analyze_page for entire pages), eliminating ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., analyze_page, generate_page_object, run_test). The verbs are action-oriented and descriptive (analyze, generate, get, run), creating a predictable and readable naming convention throughout the set.
With 5 tools, the server is well-scoped for its purpose of web automation and testing support. Each tool serves a unique function in the workflow (analysis, POM generation, test creation, locator retrieval, test execution), and none feel redundant or missing, making the count appropriate for the domain.
The toolset covers core web automation workflows comprehensively: analysis, POM generation, test creation, locator retrieval, and test execution. A minor gap exists in lacking direct element interaction tools (e.g., click_element or fill_form), but agents can work around this by using generated tests or locators, and the overall surface supports end-to-end testing tasks effectively.