YetiBrowser MCP is a fully open-source solution to allow AI assistants to easily interact with your existing browser
YetiBrowser MCP is a fully open-source solution to allow AI assistants to easily interact with your existing browser. That is what the yetibrowser mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
YetiBrowser MCP is a fully open-source implementation of the Browser MCP workflow. It links a Node-based MCP server with Chrome/Firefox extensions so Model Context Protocol clients—Codex/Claude Code, Cursor, Windsurf, MCP Inspector, or your own tools—can automate a real browser tab while keeping every byte on your machine and auditable.
The server publishes 14 tools. What each one is for:
browser_snapshot — capture an accessibility-oriented snapshot of the current pagebrowser_snapshot_diff — compare the two most recent snapshots to highlight DOM/ARIA changesbrowser_navigate — load a new URL in the connected tab and return an updated snapshotbrowser_wait — pause automation for a set number of secondsbrowser_wait_for — block until a selector appears (optionally visible) before proceedingbrowser_press_key — simulate a keyboard key press on the focused elementbrowser_click — click the element identified by a CSS selectorbrowser_hover — hover the pointer over the targeted elementbrowser_drag — drag an element onto a drop target for sortable/drag-and-drop UIsbrowser_type — type text (optionally submitting with Enter) into an editable elementbrowser_fill_form — fill multiple inputs/selects/checkboxes/radios in a single callbrowser_select_option — choose one or more options in a elementInstallation goes through your MCP client rather than a global install: point it at @yetidevworks/server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. YetiBrowser MCP's toolset — browser_snapshot, browser_snapshot_diff, browser_navigate and 11 more — is a fair guide to whether it matches your workflow.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| browser_snapshot | capture an accessibility-oriented snapshot of the current page |
| browser_snapshot_diff | compare the two most recent snapshots to highlight DOM/ARIA changes |
| browser_navigate | load a new URL in the connected tab and return an updated snapshot |
| browser_wait | pause automation for a set number of seconds |
| browser_wait_for | block until a selector appears (optionally visible) before proceeding |
| browser_press_key | simulate a keyboard key press on the focused element |
| browser_click | click the element identified by a CSS selector |
| browser_hover | hover the pointer over the targeted element |
| browser_drag | drag an element onto a drop target for sortable/drag-and-drop UIs |
| browser_type | type text (optionally submitting with Enter) into an editable element |
| browser_fill_form | fill multiple inputs/selects/checkboxes/radios in a single call |
| browser_select_option | choose one or more options in a <select> element |
| browser_screenshot | capture a viewport or full-page screenshot via the DevTools protocol |
| browser_get_console_logs | return recent console output, including errors with stack traces |
{
"mcpServers": {
"github-com-yetidevworks-yetibrowser": {
"command": "npx",
"args": ["-y", "@yetidevworks/server"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.