browser-use vs Google Hotels Scraper
browser-use is a plugin bundle for AI coding tools published by browser-use. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Community GitHub marketplaces). Google Hotels Scraper is an MCP server published by RalfIJ. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 | ||
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 4749bcb Forks (GitHub): 9 Stars (GitHub): 24 Not marked · First seen |
Not listed |
| Claude: knowledge-work-plugins | Listed Version: a25f0a2 Forks (GitHub): 9 Stars (GitHub): 24 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | browser-use | Google Hotels Scraper |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 24 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 9 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (3-12) | Remote server (mcp.apify.com) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/browser-use/plugins | github.com/ralfij/google-hotels-api |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
browser-use
Give Claude a real browser — your Chrome or a Browser Use Cloud browser. Use it whenever a task involves a website or web app: browsing, scraping and data extraction, filling forms, testing sites, taking screenshots, automating web workflows.
Google Hotels Scraper
Google Hotels prices for any city and dates: nightly and total price with taxes, ratings, amenities.
How to run each
browser-use As a Claude Code plugin
/plugin install browser-use@claude-plugins-official
Google Hotels Scraper
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Commands 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: browser-use · What it can do: Google Hotels Scraper · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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.