chrome-remote-debugging-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CDP_URL | No | Chrome remote-debugging origin | http://localhost:9222 |
| SSH_PROXY_TO | No | SSH target, e.g. user@remote. Presence enables the tunnel. | |
| SSH_PROXY_PORT | No | Fixed local port for tunnel. Auto-assigned when unset. |
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 |
|---|---|
| pingA | Check connectivity to Chrome's DevTools endpoint ( Returns |
| list_tabsA | List open Chrome page tabs. Returns |
| navigateA | Navigate a Chrome tab to Opens a new tab when |
| evaluateA | Evaluate a short JavaScript Only for small snippets (a few lines): for a longer script, write it to a
file and run it with For a large value (e.g. a page's text) pass |
| evaluate_fileA | Evaluate a JavaScript file in a Chrome tab —
|
| cdp_commandA | Send a raw CDP command and return its raw result — escape hatch. Use when the higher-level tools don't cover what you need. Events are not delivered. So |
| browseA | Open The view is built from Chrome's accessibility tree — what a screen reader
would announce — not from HTML, so it is compact enough to act on. Every
interactive element gets a Opens a new tab when |
| browse_viewA | Re-read the current page and return a fresh view with fresh refs. Refs from an earlier view stop being valid once this returns. Returns
|
| browse_actA | Run several actions against the current view, then return one new view. Each action is a dict with a
Refs come from the most recent Returns |
| close_tabA | Close a Chrome tab opened earlier (e.g. by Its refs are dropped along with it. Returns |
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
Most tools serve clearly distinct purposes: tab lifecycle, JS evaluation, accessibility browsing, and raw CDP are separable. The main overlap is navigate versus browse, both of which can open/navigate a tab, and evaluate versus evaluate_file differ mainly by input size, though descriptions make those distinctions reasonably clear.
Names are consistently snake_case and mostly use recognizable verbs: list_tabs, navigate, evaluate, browse, close_tab, etc. The browse_* family is coherent, while cdp_command and ping are minor deviations from a strict verb_noun pattern but remain readable and conventional for this domain.
Ten tools is well-scoped for a Chrome DevTools MCP server. Each tool covers a meaningful capability area—connectivity, tab management, JS execution, raw CDP escape hatch, and structured browsing—without obvious redundancy.
The surface covers tab listing, opening/navigation, closing, JS evaluation, accessibility-tree browsing, page actions, and raw CDP commands, which is strong lifecycle coverage. Minor high-level gaps remain, such as screenshots or direct DOM queries without falling back to cdp_command, but these are workable via the escape hatch.