Attaching to a browser you already have open means your logins are already there — no separate profile to authenticate. The reading tools are what make it cheap to use: text, HTML and console output are far smaller than an image, and `get_console_logs` filtered to errors answers the debugging question directly. `evaluate` runs arbitrary JavaScript in the page, so scope what you point it at.
An MCP server that attaches to an already-running Yandex Browser through its debugging port and controls open tabs. Its emphasis is getting information out without screenshots — page text, HTML, element attributes and console logs come back as data.
- Attach to a running browser and list open tabs — `connect_to_browser`, `list_tabs`; navigate a tab to a URL with an optional wait selector — `navigate`
- Interaction — `click`, `type` with a per-character delay, `hover`, `key_press` with Control/Shift/Alt/Meta modifiers, and `fill_form` keyed by selector
- Scrolling by direction and distance or to an element, with smooth or instant behaviour — `scroll`
- Reading without pixels — `get_text`, `get_html` (inner or outer), `get_attributes`, and `get_page_info` returning URL, title, description, viewport and meta tags
- Browser console logs captured and filtered by type — all, log, warn, error or info, with a limit — `get_console_logs`
- Utilities — `wait_for_element` with timeout and visibility, `screenshot` full-page or by selector, and `evaluate` to run JavaScript in the tab
Yandex Browser started in debugging mode — the repository ships a batch file, or launch `browser.exe` with `--remote-debugging-port=9222`. Clone, `npm install`, `npm run build`, then point your client's config at `build/index.js` with `node`. The package is `yandex-browser-tabs-mcp` 2.0.0 with the binary `yandex-tabs-mcp`. The README is written in Russian and the launch instructions are Windows paths.