mcp-chrome-launcher
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| port | No | Remote debugging port. Chrome/browser DevTools endpoint is exposed on 127.0.0.1:<port>. | 9223 |
| chromePath | No | Path to Chrome executable (default: auto-detected on Windows, macOS, and Linux). | |
| userDataDir | No | Chrome user data directory. | ~/.chrome-dev-profile |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| clickC | Clicks on the provided element |
| close_pageB | Closes the page by its index. The last open page cannot be closed. |
| dragC | Drag an element onto another element |
| emulateA | Emulates various features on the target page. Each call replaces all emulation settings (except extraHttpHeaders), so pass all desired settings in a single call. |
| evaluate_scriptB | Evaluate JavaScript inside the target page. The source can be provided inline or loaded from a local file. Returns the response as JSON, so returned values have to be JSON-serializable. |
| fillB | Type text into an input, text area or select an option from a element. |
| fill_formA | Fill out multiple form elements (inputs, selects, checkboxes, radios) at once. ALWAYS prefer this tool over multiple individual 'fill' or 'click' calls when interacting with forms. It is significantly faster, more reliable, and reduces turn count. Example: Fill username, password, and check "Remember Me" in one call. |
| get_console_messageA | Gets a console message by its ID. You can get all messages by calling list_console_messages. |
| get_css_stylesA | Retrieve matched CSS rules, inline styles (element.style), inherited styles, custom properties, and cascade wrappers (@layer, @media, @container, @scope) for an element identified by its UID. Rules are ordered from highest to lowest cascade precedence and include source line numbers (e.g. index:196). Active (winning) declarations have no prefix tag, while (losing) overridden declarations are prefixed with [overloaded]. Treat the output as authoritative and complete. Results are paginated (10 rules per page by default); use pageIdx to page through the remaining rules. Requires a UID from take_snapshot. |
| get_network_requestA | Gets a network request by an optional reqid, if omitted returns the currently selected request in the DevTools Network panel. Useful for inspecting request headers (including 'Cookie') and response headers (including 'Set-Cookie' and directives). |
| handle_dialogC | If a browser dialog was opened, use this command to handle it |
| hoverC | Hover over the provided element |
| lighthouse_auditA | Get Lighthouse scores, failing audits, and the DOM nodes they flag for accessibility, SEO, best practices, and agentic browsing. Full reports are saved to disk. This excludes performance. For performance audits, run performance_start_trace |
| list_console_messagesB | List all console messages for the target page since the last navigation. |
| list_network_requestsA | Lists the most recent requests for the target page since the last navigation. |
| list_pagesB | Get a list of pages open in the browser. |
| navigate_pageB | Go to a URL, or back, forward, or reload. Use project URL if not specified otherwise. |
| new_pageC | Open a new tab and load a URL. Use project URL if not specified otherwise. |
| performance_analyze_insightB | Provides more detailed information on a specific Performance Insight of an insight set that was highlighted in the results of a trace recording. |
| performance_start_traceA | Start a performance trace on the target webpage. Use to find frontend performance issues, Core Web Vitals (LCP, INP, CLS), and improve page load speed. |
| performance_stop_traceB | Stop the active performance trace recording on the target webpage. |
| press_keyA | Press a key or key combination. Use this when other input methods like fill() cannot be used (e.g., keyboard shortcuts, navigation keys, or special key combinations). Note: On macOS, native elements cannot be operated with ArrowDown/Enter via press_key; use fill() on the combobox or click() on the option instead. |
| resize_pageC | Resizes the page's window so that the page has specified dimension |
| screencast_startC | Starts recording a screencast (video) of the target page. |
| screencast_stopB | Stops the active screencast recording on the target page. |
| select_pageA | Select a page as a context for future tool calls. |
| set_logpointsA | Set the complete set of logpoints of the selected page: logpoints not in the list are removed, new ones are added, and an empty list removes all. A logpoint logs expressions to the console every time a line executes, without pausing or changing the source, like logpoints in the DevTools Sources panel. Locations are script URLs or original source files resolved through source maps (not available with --no-source-maps; scripts in workers and out-of-process iframes are not supported). A location in a generated script moves to its original source line when a source map covers it, and locations on the same line become one logpoint with the last expression. Output appears in list_console_messages; an expression that throws produces an error message without text. Logpoints survive reloads and navigations until removed or the page is closed. The response lists the resulting logpoints and where they are bound. |
| take_heapsnapshotA | Capture a heap snapshot of the target page. Use to analyze the memory distribution of JavaScript objects and debug memory leaks. |
| take_screenshotC | Take a screenshot of the page or element. |
| take_snapshotA | Take a text snapshot of the target page based on the a11y tree. The snapshot lists page elements along with a unique identifier (uid). Always use the latest snapshot. Prefer taking a snapshot over taking a screenshot. The snapshot indicates the element selected in the DevTools Elements panel (if any). |
| type_textA | Type text using keyboard into a previously focused input |
| upload_fileC | Upload a file through a provided element. |
| wait_forA | Wait for the specified text to appear on the selected page. By default, hidden text is also matched. Set visible to true to wait until the matched text is visible. |
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 33 tools
Most tools target clearly distinct resources or actions (navigation, page lifecycle, console, network, performance, memory). The main overlap is among input tools—type_text, fill, fill_form, and press_key—where an agent could misselect despite the descriptions clarifying intended use cases. Screenshot/snapshot/screencast tools are also somewhat adjacent but distinguishable.
The surface is overwhelmingly snake_case and readable, but conventions vary: most tools use verb_noun (list_pages, navigate_page), several domain tools use noun_verb (performance_start_trace, screencast_start), and some are bare verbs (click, drag, hover, fill). These deviations are minor and predictable within domains, but not fully uniform.
At 33 tools the surface is heavy, though the Chrome automation/DevTools domain is inherently broad. Many tools are specialized and earn their place (performance tracing, heap snapshot, logpoints, lighthouse, CSS inspection), but the overall count is on the high end and may overwhelm routine agent workflows.
Coverage is strong across page lifecycle, navigation, input, forms, dialogs, uploads, screenshots/snapshots, console, network, performance, memory, CSS, emulation, and logpoints. Minor gaps remain around browser storage/cookies, direct DOM/HTML retrieval, and network interception, but most core workflows are supported.