Skip to main content
Glama
chrome-remote-debugging-mcp

chrome-remote-debugging-mcp

by danilin-em

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CDP_URLNoChrome remote-debugging originhttp://localhost:9222
SSH_PROXY_TONoSSH target, e.g. user@remote. Presence enables the tunnel.
SSH_PROXY_PORTNoFixed 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
pingA

Check connectivity to Chrome's DevTools endpoint (CDP_URL, or the autoConnect source with CHROME_AUTOCONNECT).

Returns {"connected": True, "cdp_url", "browser", "protocol"} when Chrome answers, or {"connected": False, "cdp_url", "error": ...} when it is unreachable.

list_tabsA

List open Chrome page tabs.

Returns {"tabs": [{id, title, url, type}, ...]} or {"error": ...} if Chrome is unreachable.

navigateA

Navigate a Chrome tab to url.

Opens a new tab when tab_id is omitted; pass the returned tab_id to later calls to keep working in it. Returns {"tab_id", "url", "frameId"} on success, {"error": ...} otherwise.

evaluateA

Evaluate a short JavaScript expression in a Chrome tab.

Only for small snippets (a few lines): for a longer script, write it to a file and run it with evaluate_file instead. Awaits promises and returns the value by value. Returns {"tab_id", "value", "type"} on success, or {"error": ...} on failure or an uncaught JS exception. A promise that does not settle within 30 s is reported as an error.

For a large value (e.g. a page's text) pass output_path: an absolute path (~ is expanded) on the machine running this server. The value is written there instead of returned — a string as is (UTF-8), anything else as indented JSON — overwriting any existing file, and the result is {"tab_id", "path", "type", "bytes"}. On an error the file is not written.

evaluate_fileA

Evaluate a JavaScript file in a Chrome tab — evaluate for big scripts.

path must be absolute (~ is expanded) and names a UTF-8 file on the machine running this server, not the one running Chrome. Its contents run exactly as an evaluate expression: the value of the last statement is returned, promises are awaited (30 s limit), and stack traces of a JS exception name the file. Returns {"tab_id", "value", "type"} or {"error": ...}. output_path saves the value to a file instead, exactly as in evaluate.

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. method is any CDP method (e.g. "Page.captureScreenshot", "DOM.getDocument", "Network.enable"); params are its parameters. Runs in the given tab's persistent session, so objectId/nodeId values and domain state (e.g. Network.enable) carry over between calls while the tab is open and the connection lives.

Events are not delivered. So Fetch.enable, Debugger.pause, Target.setAutoAttach {waitForDebuggerOnStart: true} and Page.setInterceptFileChooserDialog {enabled: true} hang the tab until undone (Fetch.disable, Debugger.resume, …{waitForDebuggerOnStart: false}, …{enabled: false}) or the tab is closed. Browser.* and Target.* are not supported; their results are undefined. Returns {"tab_id", "method", "result"} or {"error": ...}.

browseA

Open url and return a readable view of the page, with numbered refs.

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 #N ref usable with browse_act.

Opens a new tab when tab_id is omitted; pass the returned tab_id to browse_act / browse_view. Returns {"tab_id", "url", "view", "refs"} or {"error": ...}.

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 {"tab_id", "view", "refs"} or {"error": ...}.

browse_actA

Run several actions against the current view, then return one new view.

Each action is a dict with a do key:

  • {"do": "click", "ref": 3}

  • {"do": "type", "ref": 2, "text": "коты", "clear": false}

  • {"do": "press", "key": "Enter"}

  • {"do": "select", "ref": 5, "value": "два"}

  • {"do": "check", "ref": 9} / {"do": "uncheck", "ref": 9}

  • {"do": "scroll", "ref": 7} or {"do": "scroll", "to": "bottom"}

  • {"do": "hover", "ref": 4}

  • {"do": "wait_for", "text": "Результаты", "timeout": 5} or {"do": "wait_for", "ref_gone": 3}

Refs come from the most recent browse or browse_view on this tab and are invalid afterwards. The batch stops at the first failure; a view is returned either way so you can see where the page ended up.

Returns {"tab_id", "steps", "view", "refs"}, plus "error" when a step failed, or {"error": ...} when the tab could not be resolved.

close_tabA

Close a Chrome tab opened earlier (e.g. by browse / navigate).

Its refs are dropped along with it. Returns {"tab_id", "closed": True} or {"error": ...}.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 10 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityActive
ResponsivenessNo recent community issues