connect_to_browserLABSCO SUMMARY
Console logs and page text, not screenshots.
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.
What it is
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.
What you get
- 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,typewith a per-character delay,hover,key_presswith Control/Shift/Alt/Meta modifiers, andfill_formkeyed 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, andget_page_inforeturning 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_elementwith timeout and visibility,screenshotfull-page or by selector, andevaluateto run JavaScript in the tab
Requirements
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.
Setup effort
Build from source — git clone https://github.com/T1Trit/yandex-browser-mcp
USE CASES
Finding out why a page is broken
Attach to the tab, pull the console logs filtered to errors, and read the surrounding HTML for the element involved.
Filling in a long form
Pass a map of selector to value in one call rather than clicking and typing field by field.
Reading content off a page you are already signed into
Get the text of an element or the whole page from the tab that already has your session.
Waiting for something slow to appear
Wait on the selector with a timeout and a visibility requirement before the next step runs.
18 tools
Listed in project docs. Your client may show a different list.
list_tabsnavigateclicktypehoverkey_pressscrollget_textget_htmlget_attributesget_page_infoget_console_logsfill_formwait_for_elementscreenshotevaluateexecute_testBEFORE YOU INSTALL
What to know first
Tools you get
18 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
git clone https://github.com/T1Trit/yandex-browser-mcp
cd yandex-browser-mcp
npm install
npm run buildMCP Clients
Claude Desktop
{
"mcpServers": {
"yandex-browser": {
"command": "node",
"args": [
"C:\\Users\\<YOUR_USERNAME>\\<YOUR_PATH_TO_YANDEX_BROWSER_MCP>\\build\\index.js"
]
}
}
}