Yab, Yet Another Browser vs Vibe MCP — Real Chrome, Remotely
A side-by-side look at the Yab, Yet Another Browser and Vibe MCP — Real Chrome, Remotely MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Yab, Yet Another Browser for browser automation work as a local process; choose Vibe MCP — Real Chrome, Remotely for browser automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Yab, Yet Another Browser when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
devtools_comments, devtools_console, devtools_network.
Choose Vibe MCP — Real Chrome, Remotely when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
navigate_to_url, go_back, click.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 56/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 3 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 69 | 10 |
| Full listing | View Yab, Yet Another Browser | View Vibe MCP — Real Chrome, Remotely |
Tools & capabilities
Yab, Yet Another Browser tools 69
devtools_commentsRead user-authored comments on elements of an already inspected, non-private tab.devtools_consoleRead recorded Console messages from an already inspected, non-private tab.devtools_networkRead sanitized request metadata recorded by the tab's Developer Tools.devtools_traceRead the WebKit Performance recording's event names, durations and nesting.devtools_stylesRead the currently selected element's matched and computed styles from Developer Tools.native_contextRead Yab's own current settings, spaces, tabs, mail accounts, permissions and this task's native operations.native_actionsList native Yab actions with their strict argument schemas, targetKind, undo support and permission requirements.native_applyPerform a native Yab action explicitly requested by the user: settings, spaces, tabs, page fonts or connecting Gmail.native_operationRead this task's native operation by operationId, or wait for a change up to seconds (0 to 10).native_undoUndo a native change of this task by its changeId (or the last undoable change).tabsList the tabs open in Yab, the user's web browser: the user's and the agents'.openOpen a web page (URL) in a new agent tab in Yab, the user's browser, signed in to their sites, beside the user's tabs.- +57 more on the listing page
Vibe MCP — Real Chrome, Remotely tools 10
navigate_to_urlNavigate to any URLgo_backBrowser history navigationclickClick elements on the pagetypeEnter text into inputsscrollScroll the pagetake_screenshotCapture screenshotsget_page_contentExtract page text/HTMLget_tabsTab managementkeyboard_shortcutPress keyboard combinationsweb_searchSearch the web
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Yab, Yet Another Browser
{
"mcpServers": {
"yab-yet-another-browser": {
"command": "npx",
"args": [
"-y",
"yab-mcp"
]
}
}
}
Vibe MCP — Real Chrome, Remotely
{
"mcpServers": {
"vibe-mcp-real-chrome-remotely": {
"command": "npx",
"args": [
"-y",
"@vibebrowser/cli@latest"
]
}
}
}
Frequently asked questions
Yab, Yet Another Browser is categorized under Browser Automation and uses a local stdio subprocess. Vibe MCP — Real Chrome, Remotely belongs to Browser Automation and uses a local stdio subprocess. Pick Yab, Yet Another Browser for browser automation work and Vibe MCP — Real Chrome, Remotely for browser automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Yab, Yet Another Browser has no declared pricing — check the project's own site. Vibe MCP — Real Chrome, Remotely has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add yab-yet-another-browser and vibe-mcp-real-chrome-remotely as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Yab, Yet Another Browser has a quality signal of 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Vibe MCP — Real Chrome, Remotely has 56/100 (Good) with 0 views, 0 installs and 3 GitHub stars.