chrome-mcp vs BrowserMesh
chrome-mcp is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
chrome-mcp is an MCP server published by Mehmoodqureshi. No marketplace we read lists it any more. BrowserMesh is an MCP server published by scrollDynasty. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  BrowserMesh | |
|---|---|---|
| Official MCP Registry | Removed on 2026-10-16 Version: 0.9.25 Downloads/month (npm): 4 390 Downloads/week (npm): 1 498 Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
Listed Version: 0.2.1 Downloads/month (npm): 224 Downloads/week (npm): 28 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | chrome-mcpno longer listed · | BrowserMesh |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 6 | 3 |
| Forks (GitHub) (differs) | 0 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@mehmoodqureshi/chrome-mcp) | On your machine (browsermesh) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mehmoodqureshi/chrome-mcp | github.com/scrolldynasty/multi-agent-browser-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of chrome-mcp
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Drive your real Chrome over MCP: real logins and cookies, multi-tab automation, deny-all by default.
-
agent-webbridge io.github.jeet-dhandha/agent-webbridge
Drive your real, logged-in Chrome (many profiles, parallel tabs) from any MCP client. Local only.
-
browser io.github.cherchyk/browser
MCP server for loading authenticated web pages using Chrome DevTools Protocol
-
browser-mcp io.github.Shreyas-Profile/browser-mcp
Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
-
weboperator io.github.KazKozDev/weboperator
Hands your live Chrome tab to any MCP client — snapshot, navigate, click, type, extract.
-
real-browser io.github.ofershap/real-browser
MCP server + Chrome extension for AI browser control with real sessions.
What each says it does
chrome-mcp
Drive your real Chrome over MCP: real logins and cookies, multi-tab automation, deny-all by default.
BrowserMesh
Isolated multi-session Chromium runtime for external MCP clients over stdio.
How to run each
chrome-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
BrowserMesh As a local MCP server: npm package
claude mcp add --transport stdio browsermesh -- npx -y browsermeshCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: chrome-mcp · What it can do: BrowserMesh · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.