MCP-Undetected-Chromedriver
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 |
|---|---|
| browser_navigateC | Navigate to a URL |
| browser_screenshotC | Take a screenshot of the current page or a specific element |
| browser_clickC | Click an element on the page |
| browser_iframe_clickB | Click an element inside an iframe on the page |
| browser_fillC | fill out an input field |
| browser_selectC | Select an element on the page with Select tag |
| browser_hoverC | Hover over an element on the page |
| browser_evaluteC | Evaluate a JavaScript expression in the browser console |
| browser_closeA | Close the browser and release all resources |
| browser_get_visible_textB | Get the visible text of the current page |
| browser_get_visible_htmlB | Get the HTML of the current page |
| browser_go_backA | Navigate back in browser history |
| browser_go_forwardB | Navigate forward in browser history |
| browser_dragC | Drag an element to another element |
| browser_press_keyB | Press a key on the keyboard |
| browser_save_as_pdfB | Save the current page as a PDF |
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 16 tools
Most tools have distinct purposes targeting specific browser automation tasks like navigation, interaction, and content extraction. However, some overlap exists between browser_click and browser_iframe_click, where the latter is essentially a specialized version of the former for iframes, which could cause minor confusion.
All tools follow a consistent snake_case naming pattern with a clear 'browser_' prefix followed by a verb_noun structure (e.g., browser_click, browser_navigate, browser_screenshot). This uniformity makes the tool set predictable and easy to understand.
With 16 tools, the count is slightly high but reasonable for a browser automation server, covering a wide range of common web interaction tasks. It might feel a bit heavy, but each tool appears to serve a specific function without obvious redundancy.
The tool set provides comprehensive coverage for core browser automation, including navigation, clicking, typing, hovering, and content extraction. Minor gaps exist, such as no explicit tool for handling cookies, managing tabs, or waiting for elements, but agents can likely work around these using existing tools like browser_evalute or timeouts.