Public Browser vs Vibe MCP — Real Chrome, Remotely
A side-by-side look at the Public 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 Public 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 Public Browser when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
PUBLIC_BROWSER_SCRIPT_TOKEN.
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 | 57/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 | 18 | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 1 | 10 |
| Full listing | View Public Browser | View Vibe MCP — Real Chrome, Remotely |
Tools & capabilities
Public Browser tools 1
PUBLIC_BROWSER_SCRIPT_TOKEN
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.
Public Browser
{
"mcpServers": {
"public-browser": {
"command": "npx",
"args": [
"-y",
"public-browser@latest"
]
}
}
}
Vibe MCP — Real Chrome, Remotely
{
"mcpServers": {
"vibe-mcp-real-chrome-remotely": {
"command": "npx",
"args": [
"-y",
"@vibebrowser/cli@latest"
]
}
}
}
Frequently asked questions
Public 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 Public 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.
Public 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 public-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, Public Browser has a quality signal of 57/100 (Good) with 0 views, 0 installs and 18 GitHub stars. Vibe MCP — Real Chrome, Remotely has 56/100 (Good) with 0 views, 0 installs and 3 GitHub stars.
