chrome-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tabs_listA | List open browser tabs. |
| screenshotA | Capture a screenshot (page or element). Default is JPEG (quality 70) at CSS-pixel size, which is several times smaller than PNG and reads fine. Pass format:"png" for lossless, quality 1-100 for JPEG, scale 2 for device pixels on a Retina display or 0.5 to shrink. |
| get_textB | Get visible text of the page or an element. |
| get_htmlA | Get HTML of the page or an element. Output is capped (see maxBytes) and cut at a tag boundary; narrow it with |
| snapshotA | Accessibility snapshot: interactive elements with refs to target by |
| get_cookiesA | Read cookies visible to the tab's URL (or a given url). |
| storageC | Read/write localStorage (or sessionStorage). op: get|set|remove|clear. |
| wait_forB | Wait for a selector or text to appear/disappear. |
| extract_linksB | Extract anchors from the page or a subtree. dedupe=true collapses links sharing an href (nav/footer noise); limit caps the count. |
| read_as_markdownC | Read the page (or subtree) as readable markdown. |
| frames_listA | List the tab's frames (the top document plus every iframe the extension can reach), with each frame's id and URL. Use it when a selector that should match does not: the element is probably in one of these frames, and you can then pass frameId (or allFrames:true) to act inside it. |
| print_pdfA | Render the page to PDF through Chrome's own print pipeline and save it to the task's results/ dir. Returns the path and size, not the bytes - a PDF is not something to spend context on. |
| chrome_statusA | Report backend/session status: paired browser profiles and how each was named, and flags for switched-off capabilities. |
| auth_checkA | Is the tab sitting on a sign-in wall? Reads the page (URL, title, password fields, sign-in controls) and returns { authRequired, confidence, signals }. Use it after a navigate, or whenever a step fails unexpectedly, to tell "the session expired" apart from "the agent got lost". Pass failOnAuthWall:true to get an [AUTH_REQUIRED] error instead of a verdict, so a harness can bucket the run as an auth failure. |
| profile_useA | Switch the active browser profile (identity). Subsequent downloads, results, screenshots, and the action log are stored under profiles//. Resets the active task to "default" unless you then call task_new. |
| profile_renameA | Rename an automatically named browser profile (e.g. "profile-2" -> "work"). The name sticks across restarts; its saved artifacts move with it. |
| task_newA | Start a new task (run) under the active profile. Creates profiles//tasks// with downloads/, results/, screenshots/ and makes it the active task so all captured artifacts land there. |
| tasks_listA | List every task across all profiles under the data dir, with sizes and download counts. |
| task_statusA | Report the active profile/task and the folder paths where this run's artifacts are stored. |
| batchA | Run multiple tool calls in one request — parallel (default) or serial. Each op is { tool, args } and goes through the same policy gate, rate limit, and error handling as a direct call. In parallel mode, tab-scoped ops MUST pass an explicit tabId (the active-tab default is unsafe under concurrency). Use to drive several tabs at once (e.g. open tabs, then batch get_text across them). Cannot be nested. |
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 20 tools
Most tools map to a distinct resource/action, and prefixes like task_, profile_, and get_ reduce confusion. The page-reading tools (read_as_markdown, get_text, get_html, snapshot) are close but their output formats are clearly differentiated, so only minor ambiguity remains.
Names are uniformly snake_case and often resource-prefixed, but conventions vary: task_new uses an adjective, tasks_list puts the verb last, and standalone names like storage, screenshot, and batch break the pattern. The set is readable but does not follow one consistent verb_noun convention.
At 20 tools, the server is on the heavy end of the typical range. Each tool has a plausible purpose and browser automation is broad, but the count feels more like a full feature list than a tightly scoped set.
The toolset strongly covers observation and capture: text, HTML, screenshots, PDFs, cookies, frames, tabs, and task/profile state. However, it lacks fundamental browser-driving operations like navigation, tab creation/activation, and element interaction, which is a significant gap for an automation-oriented server.