Browse Bridge vs Agent Chrome
Browse Bridge is an MCP server published by browsebridge.com. Marketplaces we read that list it: 1 (Official MCP Registry). Agent Chrome is an MCP server published by agentchrome.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Browse Bridge |  Agent Chrome |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 1 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 | Browse Bridge | Agent Chrome |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.browsebridge.com/mcp) | Remote server (agentchrome.dev/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| 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/bryanhamilton/browsebridge-cursor-plugin | github.com/shadowwalker2014/agentchrome |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-27 | 2026-11-04 |
| Endpoint at the last check (differs) | Status out of date: last check 2 days ago returned HTTP 405 | Status out of date: last check 43 h ago returned HTTP 401 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Browse Bridge
Let AI agents observe and control Chrome tabs you explicitly share via Browse Bridge.
Agent Chrome
Let AI agents use your real, signed-in Chrome: tabs, clicks, forms, screenshots and video.
How to run each
Browse Bridge As a remote MCP server
claude mcp add --transport http browse-bridge https://mcp.browsebridge.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"Requires: Authorization header
Agent Chrome As a remote MCP server
claude mcp add --transport http agentchrome https://agentchrome.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
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: Browse Bridge · What it can do: Agent Chrome · 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.