A side-by-side look at the Riffle 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 Riffle for browser automation work; 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.
navigate_to_url, go_back, click.Rows where the two servers differ are marked.
| Spec | R Riffle | |
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 37/100 · Fair | 56/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 10 |
| Full listing | View Riffle | View Vibe MCP — Real Chrome, Remotely |
No tool names declared yet. Check the project README from the listing page.
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 webPaste 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.
No confirmed install command for Riffle yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"vibe-mcp-real-chrome-remotely": {
"command": "npx",
"args": [
"-y",
"@vibebrowser/cli@latest"
]
}
}
}