chrome-devtools-mcp-fork
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHROME_DEBUG_PORT | No | Chrome remote debugging port | 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_chromeC | Start Chrome with remote debugging enabled. |
| connect_to_browserC | Connect to a running Chrome instance. |
| get_connection_statusB | Get current connection status. |
| start_chrome_and_connectC | Start Chrome and connect in one operation. |
| navigate_to_urlC | Navigate to a specific URL. |
| get_console_logsB | Get console logs (placeholder implementation). |
| clear_consoleB | Clear console (placeholder implementation). |
| get_computed_stylesD | Get computed styles (placeholder implementation). |
| get_documentC | Get DOM document (placeholder implementation). |
| get_network_requestsC | Get network requests (placeholder implementation). |
| get_performance_metricsC | Get performance metrics (placeholder implementation). |
| get_all_cookiesC | Get all cookies (placeholder implementation). |
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 12 tools
Most tools have distinct purposes, but start_chrome, connect_to_browser, and start_chrome_and_connect overlap in domain, though descriptions clarify their roles.
All tools use consistent snake_case verb_noun pattern (e.g., clear_console, navigate_to_url), with no mixing of conventions.
12 tools is well-scoped for Chrome DevTools operations, covering essential actions without being overly numerous.
Many tools are placeholder implementations, and the set lacks fundamental interactions like executing JavaScript, modifying cookies, or element manipulation, leaving significant gaps.