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

  • 9 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • The server gets full access to browser tabs via the debug port, including form filling and key presses
All reasons and checks
Russian stack

t1trit/yandex-browser-mcp

Install

Manual install

npm install && npm run build

Building the server, from the README.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The server gets full access to browser tabs via the debug port, including form filling and key presses

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 page

MCP

Transport
stdio
Authentication
not required

Limitations

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.

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.

Discussion

No questions or reviews yet.

Russian stack

A browser extension and local MCP server with 254 tools: the agent reads and changes the DOM, clicks and runs JS in Yandex Browser and Chromium tabs

MCP serverBroad access
Russian stack

An unofficial Playwright-based MCP server that searches Yandex through a browser with authenticated cookies, extracting and ranking page content for an agent

MCP serverBroad access4Repository stars

A Chrome extension with an MCP server: the agent drives your everyday browser with its sessions, tabs, bookmarks and history

MCP serverBroad access12.5KRepository stars
Russian stack

A search MCP server on the Yandex Cloud Search API with a monitoring dashboard, Brave fallback and an offline bundle for air-gapped networks

MCP serverExtended access
Russian stack

An MCP web-search and content-extraction server via Yandex and Google on top of SerpAPI, geared toward RU/CIS results

MCP serverExtended access1Repository stars

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.

README badge

Report a problem