Yandex Browser tabs MCP server
Yandex Browser Tabs MCP Server v2.0
An MCP server for controlling Yandex Browser tabs over the Chrome DevTools debugging protocol
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- The server gets full access to browser tabs via the debug port, including form filling and key presses
Install
Manual install
npm install && npm run buildBuilding the server, from the README.
This is third-party code. Review the repository files before installing.
What it does
The TypeScript server connects to Yandex Browser launched with the remote-debugging-port flag, via the Chrome DevTools debugging protocol. Version 2.0 adds console log capture and history with type filtering, scrolling to an element with animation or in any direction, extracting text and HTML from a page or element, reading attributes and page metadata, hover effects, key presses and combinations, form filling, and waiting for elements to appear, on top of basic tab connection and listing.
Who it is for. For people automating or debugging web pages specifically in Yandex Browser through an agent.
Good fit when
- You want to automate actions in an already open Yandex Browser
- You want to read console logs or page text without screenshots
Not a fit when
- You need cross-browser automation: the server and batch scripts target Yandex Browser and Windows specifically
- You need a full replacement for testing tools like Playwright
Example request
List Yandex Browser tabs and show the text of the active tab's pageLimitations
The project is maintained by one author, with no pushes for over a year. The ready-made launch batch files target Windows. The browser has to run with an open debugging port, which reduces its isolation.
How to disable. Remove the server from your MCP client config and close the browser instance running with the debug port open.
MCP
- Transport
- stdio
- Authentication
- not required
Security check
- The server gets full access to browser tabs via the debug port, including form filling and key presses
README in short
The Russian README describes version 2.0's new features: browser console access, fast scrolling, text and HTML extraction without screenshots, extended interaction. It gives npm install commands, launching the browser with a debug port via batch files, a Claude Desktop config snippet, and a detailed function list with signatures.
FAQ
Do I need to change anything in the browser itself?
Yes, the browser must run with the --remote-debugging-port flag; the repository includes ready batch files for that.
Related
CLI, skill and Python library for browser control: the agent clicks, fills forms and reads pages over CDP
A skill that gathers the last 30 days of discussion on a topic from Reddit, X, YouTube, HN, Polymarket and GitHub into one brief
The Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces
A fast Rust CLI for agent browser automation: accessibility snapshots with element refs, an MCP server and skills