Yetibrowser Mcp

What is Yetibrowser Mcp?

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—such as Codex/Claude Code, Cursor, Windsurf, MCP Inspector, or custom tools—can automate a real browser tab while keeping every byte on the user’s machine and fully auditable.

How to use Yetibrowser Mcp?

Install the browser extension (Chrome from the Chrome Web Store; Firefox is not yet available). Then start the MCP server with npx yetibrowser-mcp (optionally with --ws-port <port> to pin a specific WebSocket port). Configure your MCP client to run that command. For Codex CLI, edit ~/.codex/config.toml with args = ["yetibrowser-mcp"]. For Claude Code, add the server entry to ~/Library/Application Support/Claude/claude_desktop_config.json. Once the extension connects to a tab, the tools become available.

Key features of Yetibrowser Mcp

• Transparent and hackable – no blob downloads; inspect, fork, and extend every component.
• Local-first – extension only talks to a localhost MCP server; browsing data never leaves your device.
• Cross-browser – shared logic powers both Chrome and Firefox packages (Firefox build pending fuller MV3 support).
• Developer-focused tooling – richer console capture, DOM diffing, page-state dumps, and full-page screenshots.
• Production-friendly – scripts and docs for packaging, publishing, and integrating with IDE workflows.

Use cases of Yetibrowser Mcp

• AI-assisted web automation for debugging and QA tasks.
• Automated form filling and navigation testing via MCP clients.
• Capturing accessibility-oriented snapshots and diffing DOM changes.
• Gathering page state (forms, storage, cookies) and console logs for troubleshooting.
• Integrating browser control into custom MCP-aware tools or IDEs.

FAQ from Yetibrowser Mcp

How do I install the Chrome extension?

Install the latest Chrome Browser Extension from the Chrome Web Store at the link provided in the README. Leave it on Automatic connection mode unless you are running multiple instances of the Yetibrowser Mcp Server.

Is Firefox supported?

The Firefox extension is not currently available due to limited capabilities of Manifest V3 in Firefox stable release. It is on hold until full MV3 support is commonly available (outside of Nightly builds).

How do I set a specific WebSocket port for the server?

Pass --ws-port <port> when running npx yetibrowser-mcp. For example: npx yetibrowser-mcp --ws-port 9010. If no port is provided, the CLI walks ports 9010–9020 until it finds a free one.

How can I check the connection status or port?

Use the browser_connection_info tool to report the bridge WebSocket port, connection status, and extension version. Alternatively, ask your AI tool about the connection (e.g., “what is the yetibrowser mcp connection info?”) and then set the manual port accordingly.

What transport does the MCP server use?

The server exposes the standard MCP transport over stdio. It also uses a WebSocket bridge to communicate with the browser extension on localhost.