chrome-devtools-mcp wait_for accepts any-match text arrays
Introduced 2026-02-25 · score 0.98
HOW TO USE IT
When a page flow can end with any of several text outcomes, call `wait_for` with `text` set to a non-empty list of candidate strings; it resolves when any listed text appears.
{"name":"wait_for","arguments":{"pageId":<page_id>,"text":["Complete","Error"],"timeout":<milliseconds>}}WHY THIS HELPS
When a page flow may end with any of several text outcomes, wait for the first matching text.
BEFORE THIS CHANGE
Call `wait_for` with one expected string, so a flow that ends in a different text outcome can keep waiting until timeout.
REQUIREMENTS AND LIMITATIONS
- Version: 0.18.0
- pageId (required): Targets a specific page by ID.
- text (required): Non-empty list of texts; resolves when any value appears on the page.
- timeout: Maximum wait time in milliseconds; 0 uses the default timeout.
- The text list must be non-empty.
- `timeout` is an optional integer in milliseconds; 0 keeps default behavior.
FIRST-PARTY EVIDENCE
- https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v0.18.0
- https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/1011
- https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/496ab1b45f7a283a1432643777e0795a17f33667/docs/tool-reference.md
Check the installed version and the source before using it. Entry JSON