Yoke

Let MCP clients drive your signed in Chrome: tabs, page text, trusted input, screenshots, console, and network.

Yoke lets an AI agent or command line tool drive the Chrome you are already signed in to, through the Model Context Protocol. Unlike a headless browser, there is nothing to log into again. Your sessions, cookies, extensions and open tabs are already there, because it is your browser. WHAT IT DOES - Sees every tab in every window, not a managed subset - Reads page text, and describes interactive elements so a client can act on them by name rather than by guessing coordinates - Sends real clicks and keystrokes that pages cannot distinguish from yours - Screenshots any tab, including one in the background - Reports console messages and network requests for tabs it is driving - Puts every tab it touches into a visible tab group, so you can always see what is under automation HOW IT WORKS Yoke is two halves. This extension is one; the other is a local MCP server installed from npm: npm install -g yoke-mcp yoke install The extension talks to that server through a native messaging host on your own machine. Nothing leaves your computer by way of Yoke. The extension does nothing on its own. With no client connected it sits idle: there is no popup, no button, and no background activity. BEFORE YOU INSTALL This gives a local program broad control of a browser you are signed into. It can read page content, run JavaScript and send input on any site you point it at. Install it only for tools you would trust with that. A tab being driven shows Chrome's own "started debugging this browser" bar. That is Chrome telling you the truth and Yoke does not hide it. Open source, MIT licensed: https://github.com/hamzahamidi/yoke