Add YetiBrowser MCP to Community registry

[rhukster]

Adding YetiBrowser MCP to Community Registry

Description

Motivation and Context

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.

Other MCP options I tried didn't have the scope of browser tools I needed, were closed source, nor did they work well with multiple AI assistant instances. I needed something that was more powerful, and also let me configure which instance was pointing to the browser extensions

How Has This Been Tested?

This is a local MCP server and Chrome browser extension. I've been using this MCP exclusively for weeks, and it's been working great. It took a few iterations to get the auto-connecting port functionality to work as intended, but all good now.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Additional context

Originally I had planned for both Chrome and Firefox extensions, but due to limitations with the current state of Manifest v3, Firefox extension is on hold until better support is in the stable builds. Currently requires 'nightly' builds and explicit background processing enabled.