YX Bridge: an agent bridge to the browser
YX Bridge
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
- 0 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The agent can run arbitrary JavaScript and fill and submit forms in real tabs with the user's active login sessions
- Access extends to every open tab, including email, banking and other sensitive services if they are open
Install
- Works in
- Services
Manual install
cd server
npm install
claude mcp add yx-bridge -s user -- node "<full path>/server/src/server.js"The README's manual server registration for Claude Code.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent can run arbitrary JavaScript and fill and submit forms in real tabs with the user's active login sessions
- Access extends to every open tab, including email, banking and other sensitive services if they are open
This is third-party code. Review the repository files before installing.
What it does
The pair of a browser extension and a local MCP server gives an agent direct access to open tabs in Yandex Browser or any Chromium browser: reading the page, changing the DOM, clicking and typing, running arbitrary JavaScript, screenshots, raw DevTools Protocol commands, controlling Yandex Browser's auto-translation and the browser's own UI. Communication stays local over WebSocket between the extension and the server, with no accounts and no external servers. The extension icon has a pause toggle that stops data flowing to the agent, and an optional local password that locks the port to its own extension only. All 254 tools cover tabs, the DOM, input, JavaScript, screenshots, DevTools, browser memory and window control.
Who it is for. For people who want to give an agent direct control over their already-open browser: reading pages, form automation, DevTools-level debugging.
Good fit when
- You want the agent to read, click and fill forms in a real, already-logged-in browser
- You need DevTools Protocol access and arbitrary JavaScript on the page
- You work in Yandex Browser and want to control its auto-translation from the agent
Not a fit when
- You do not want to give the agent access to tabs with live logins to banking, email or other sensitive services
- You need headless automation without the user's real browser, such as Playwright
Example request
Read the open tab, remove the cookie banner, and take a full-page screenshotMCP
- Transport
- stdio
- Authentication
- not required
Limitations
It only works on Windows, macOS and Linux with Node.js 18 installed and a Chromium-compatible browser. Full UI Automation control is Windows-only. The extension must be loaded manually in developer mode on macOS and Linux. The tool's power is directly proportional to its risk: the agent gets access to every tab you have open, including logins to any service.
How to disable. Click pause on the extension icon to temporarily stop data flow, or run uninstall.cmd (Windows), or manually remove the extension from the browser and the server registration.
FAQ
Does data leave to an external server?
No, communication stays local between the extension and the server on your machine, with no accounts and no external servers.
How do I quickly stop the agent if it does something wrong?
Click the pause toggle on the extension icon; it instantly stops data flowing to the agent.
Discussion
No questions or reviews yet.
Related
MCP serversYandex 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
A Chrome extension with an MCP server: the agent drives your everyday browser with its sessions, tabs, bookmarks and history
An MCP bridge to control your browser from a coding agent: a Chrome extension and a set of tab and page automation tools
MCP connects an agent to an existing Chromium browser for reading, clicks, input, screenshots and JavaScript execution.
A CLI and MCP server that lets an agent drive your real Chrome with its logged-in sessions: 103 commands across 36 platforms plus browser automation
A plugin and MCP server letting an agent drive your open, already logged-in Chrome through an extension with no debugging port.
README in short
The bilingual README explains the local WebSocket architecture, three install paths, one-click on Windows, agent-driven install via AGENT-INSTALL.md, and manual, gives example agent phrases, describes the pause toggle and password on the extension icon, and tables of all 254 tools by category.