YetiBrowser MCP

by yetidevworks

Not rated
GitHub

About

YetiBrowser MCP is a fully open-source solution to allow AI assistants to easily interact with your existing browser

Details

Author
yetidevworks
Categories
Developer Tools

Setup

Install YetiBrowser MCP in your MCP client (Claude Desktop, Cursor, Windsurf, and others).

Repository: https://github.com/yetidevworks/yetibrowser-mcp

Follow the installation instructions in the repository README, then restart your MCP client.

YetiBrowser MCP is a fully open-source solution to allow AI assistants to easily interact with your existing browser

[!IMPORTANT] This project has been archived. It was built to address the lack of browser control in AI agents such as Claude and Codex, but the agents now have these functions built in without the need for a dedicated MCP based solution.

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.

- Transparent and hackable– no blob downloads. Inspect, fork, and extend every component.
- Local-first– the extension talks only to a localhost MCP server; browsing data never leaves your device.
- Cross-browser– shared logic powers both Chrome and Firefox packages (Firefox build is pending better Manifest V3 support, so connection UX may be limited until Mozilla ships full MV3 APIs).
- Developer-focused tooling– richer console capture, DOM diffing, page-state dumps, and full-page screenshots built for debugging and QA.
- Production-friendly– scripts and docs for packaging, publishing, and integrating with IDE workflows.

- packages/shared– shared TypeScript definitions for messages and tool schemas.
- packages/server– the MCP server that bridges MCP clients to a running browser tab.
- extensions/shared– shared extension source (background/popup) and assets.
- extensions/chrome/extensions/firefox– per-browser packaging layers.
- docs/– workspace commands, publishing checklists, and feature notes.
- scripts/– helper utilities such aspackage-extensions.shfor release zips.

- Install the latest Chrome Browser Extension here:https://chromewebstore.google.com/detail/hpedknkjljpopinabjjmljgckhlancni?utm_source=item-share-cb
- Leave it onAutomaticconnection mode unless you are running multiple instances of YetiBrowser MCP Server

Firefox Browser (not currently available)

- Due to the limited capabilities of Manifest v3 in Firefox stable release, the Firefox extension is on hold until full support is commonly avaialble (outside of Nightly builds).

- Edit your ~/.codex/config.toml and add the MCP entry:

[mcp_servers.yetibrowser-mcp] command = "npx" args = ["-y", "@yetidevworks/server"]

- Make sure the extension is installed and connected to a tab, then start the MCP server withnpx -y @yetidevworks/server(or run the locally built CLI).
- Add the server entry to~/Library/Application Support/Claude/claude_desktop_config.json(see the example indocs/publishing.md).
- Restartclaudeso it picks up the new MCP server; you should seeyetibrowser-mcplisted under the/mcptools menu once the extension connects.

- Any MCP client can connect by spawning the CLI (npx -y @yetidevworks/server) or optionally provide a specific port, e.g.npx -y @yetidevworks/server --ws-port 9010.
- The server exposes the standard MCP transport over stdio, so use whatever configuration mechanism your client supports to run the command above when a tab is connected.

- For testing and debugging outside a coding agent.
- npx @modelcontextprotocol/inspector npx -y @yetidevworks/server -- --ws-port 9010to run and inspect the MCP server in conjunction with the YetiBrowser MCP browser extension.

- The CLI walks ports9010-9020until it finds a free one, loggingswitched towhen it advances. Pass--ws-port <port>if you want to pin a specific port instead.
- The Browser extension popup mirrors that behaviour: leave it on “Automatic” to track the CLI’s port, or choose “Manual” and enter the port reported bybrowser_connection_info/ the CLI log to override it.
- Simply ask your AI tool about the connection port. For example:what is the yetibrowser mcp connction info?, then set the manual port the port reported.

- Workspace commands live indocs/workspace-commands.md.
- Publishing steps (npm + extension stores) are in
docs/publishing.md.
- Screenshot behaviour is documented in
docs/screenshot.md.
- Generate distributable Chrome/Firefox zips with./scripts/package-extensions.sh(outputs toartifacts/).
- A repository-level privacy policy is available in
PRIVACY.md.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Create crafted UI components inspired by the best 21st.dev design engineers.

Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server

An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .

MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent

ALAPI MCP Tools,Call hundreds of API interfaces via MCP

AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform

MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references.

APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.

One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.

Build and deploy full-stack Next.js apps with 98 tools for React, AWS, and MongoDB

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.