skyvern-browser-automation vs com.browser-use/browser-use
skyvern-browser-automation is a plugin bundle for AI coding tools published by mark1ian. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). com.browser-use/browser-use is an MCP server published by browser-use.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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 |  skyvern-browser-automation |  com.browser-use/browser-use |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.13.11 Downloads/month (PyPI): 8 061 974 Downloads/week (PyPI): 1 503 767 Forks (GitHub): 13 493 Stars (GitHub): 120 707 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 | skyvern-browser-automation | com.browser-use/browser-use |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 120 707 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 13 493 (better) |
| Last release (differs) | Not published | 2026-10-21 |
| Where it runs (differs) | Remote server (api.skyvern.com/mcp) | Remote server (api.browser-use.com/v3/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mark1ian/skyvern-skills | github.com/browser-use/browser-use |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 16 h ago, requires authentication | Responded 6 h ago |
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
skyvern-browser-automation
Skyvern browser automation skills for web scraping and interaction via remote MCP.
com.browser-use/browser-use
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
How to run each
skyvern-browser-automation As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install skyvern-browser-automation@claude-communitycom.browser-use/browser-use As a remote MCP server
claude mcp add --transport http browser-use https://api.browser-use.com/v3/mcp --header "X-Browser-Use-API-Key: <YOUR_X_BROWSER_USE_API_KEY>"Requires: X-Browser-Use-API-Key header
Commands 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: skyvern-browser-automation · What it can do: com.browser-use/browser-use · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.