chrome-wes

Generated by declick from mcp:npx chrome-devtools-mcp@latest --autoConnect. Deterministic, no screenshots, JSON by default when piped.

chrome-wes (mcp)  source: mcp:npx chrome-devtools-mcp@latest --autoConnect  server: npx chrome-devtools-mcp@latest --autoConnect
  click <page-id>                        Clicks on the provided element [mutating]
  close-page <page-id>                   Closes the page by its index. [mutating]
  drag <page-id>                         Drag an element onto another element [mutating]
  emulate <page-id>                      Emulates various features on the target page. [mutating]
  evaluate-script <page-id>              Evaluate a JavaScript function inside the target page. [mutating]
  fill <page-id>                         Type text into an input, text area or select an option from a <select> element. [mutating]
  fill-form <page-id>                    Fill out multiple form elements (inputs, selects, checkboxes, radios) at once. [mutating]
  get-console-message <page-id>          Gets a console message by its ID.
  get-network-request <page-id>          Gets a network request by an optional reqid, if omitted returns the currently se [mutating]
  handle-dialog <page-id>                If a browser dialog was opened, use this command to handle it [mutating]
  hover <page-id>                        Hover over the provided element [mutating]
  lighthouse-audit <page-id>             Get Lighthouse score and reports for accessibility, SEO, best practices, and age [mutating]
  list-console-messages <page-id>        List all console messages for the target page since the last navigation.
  list-network-requests <page-id>        Lists the most recent requests for the target page since the last navigation.
  ... 15 more verbs (29 total): declick describe chrome-wes --grep <text> | --offset N --limit N | --verb v
common: --json --fields --limit --rows --where --dry-run --full   exit: 0 ok 1 err 2 missing 3 blocked 4 auth

Examples (replace UPPERCASE tokens with real values; 'declick describe chrome-wes --verb <verb>' prints one verb's flags and what it returns):

chrome-wes click PAGE_ID --page-id PAGE_ID --uid UID --dry-run
chrome-wes close-page PAGE_ID --page-id PAGE_ID --dry-run
chrome-wes drag PAGE_ID --page-id PAGE_ID --from-uid FROM_UID --to-uid TO_UID --dry-run

If 'chrome-wes' is not on PATH, run every command as: declick run chrome-wes <verb> ... (same output, same exit codes). Every verb: --json (default when piped) --fields a,b --limit N; mutating verbs accept --dry-run. Success: {"ok":true,"data":...,"meta":{"count":N,"truncated":false}}. Failure: {"ok":false,"error":"...","exit":N}. Exit 2 means the verb is not in the server tools list, 3 blocked by governance. Every verb starts mcp:npx chrome-devtools-mcp@latest --autoConnect, calls one tool and exits, so the server does not have to be running first.