Browser Automation vs Native DevTools
Browser Automation is an MCP server published by mindstone. Marketplaces we read that list it: 1 (Official MCP Registry). Native DevTools is an MCP server published by sh3ll3x3c. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  Browser Automation |  Native DevTools |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.2 Downloads/month (npm): 959 Downloads/week (npm): 56 Forks (GitHub): 4 Stars (GitHub): 13 Not marked · First seen |
Listed Version: 0.10.1 Downloads/month (npm): 478 Downloads/week (npm): 103 Forks (GitHub): 17 Stars (GitHub): 138 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 Automation | Native DevTools |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 13 (worse) | 138 (better) |
| Forks (GitHub) (differs) | 4 (worse) | 17 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@mindstone/mcp-server-browser-automation) | On your machine (native-devtools-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mindstone/mcp-servers | github.com/sh3ll3x3c/native-devtools-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. 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 Automation
Browser automation MCP server: navigate, fill forms, click, screenshot, and manage tabs
Native DevTools
MCP server for desktop, browser (CDP), and Android automation. Screenshot, OCR, click, type.
How to run each
Browser Automation As a local MCP server: npm package
claude mcp add --transport stdio mcp-server-browser-automation -- npx -y @mindstone/mcp-server-browser-automationNative DevTools As a local MCP server: npm package
claude mcp add --transport stdio native-devtools -- npx -y native-devtools-mcpCommands 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
The marketplaces of Native DevTools publish no settings it asks for, so we do not compare settings.
What it can do: Browser Automation · What it can do: Native DevTools · 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.