Chrome MCP Docker
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHROME_HOST | No | The host where the Chrome browser is running | localhost |
| CHROME_PORT | No | The port where Chrome DevTools Protocol is exposed | 9222 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| navigateB | Navigates to a URL and waits for network idle. |
| screenshotA | Takes a screenshot of the viewport. Returns base64. |
| clickB | Clicks an element identified by CSS selector. |
| typeC | Types text into an input field. |
| scrollB | Scrolls the page. Use x,y coordinates OR selector to scroll into view. |
| wait_for_selectorC | Waits for an element to appear in the DOM. |
| get_computed_stylesB | Returns the computed CSS styles for an element (essential for UI debugging). |
| get_network_errorsB | Returns a list of failed network requests. |
| get_console_logsB | Returns captured console logs (errors, warnings, info). Useful for debugging JS issues. |
| mobile_modeB | Toggles mobile viewport (iPhone X dimensions). |
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 10 tools
Each tool has a clearly distinct purpose: click, type, scroll, navigate, screenshot, wait_for_selector are standard browser actions; get_computed_styles, get_console_logs, get_network_errors are debugging tools; mobile_mode is a viewport toggle. No overlap or ambiguity.
Most tools follow a verb_noun pattern (get_computed_styles, get_console_logs, wait_for_selector) or are single verbs (click, scroll). 'mobile_mode' is a noun phrase, but still clear. Inconsistent usage of underscores (some have, others don't), but pattern is mostly predictable.
10 tools is well-scoped for a browser automation server. Covers essential navigation, interaction, and debugging without redundancy. No unnecessary tools, and the count is within the ideal 3-15 range.
Core actions (navigate, click, type, scroll) and debugging (console logs, network errors, computed styles) are covered, but missing common operations like executing JavaScript, getting page source, handling alerts, managing cookies, or interacting with more complex form elements (select, checkbox). Agent may need workarounds.