io.github.AINative-Studio/ainative-browser-mcp vs io.github.brightdata/brightdata-mcp
io.github.AINative-Studio/ainative-browser-mcp is an MCP server published by AINative-Studio. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.brightdata/brightdata-mcp is an MCP server published by brightdata. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |  io.github.AINative-Studio/ainative-browser-mcp |  io.github.brightdata/brightdata-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.2 Downloads/month (npm): 941 Downloads/week (npm): 171 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 3.1.0 Downloads/month (npm): 48 444 Downloads/week (npm): 16 203 Forks (GitHub): 332 Stars (GitHub): 2 677 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 | io.github.AINative-Studio/ainative-browser-mcp | io.github.brightdata/brightdata-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 2 677 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 332 (better) |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | On your machine (@ainative/browser-mcp) | On your machine (@brightdata/mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 8, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/ainative-studio/ainative-browser-mcp | github.com/brightdata/brightdata-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| 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
io.github.AINative-Studio/ainative-browser-mcp
AI-powered browser automation MCP — 6 tools for web interaction, extraction, and validation.
io.github.brightdata/brightdata-mcp
Bright Data's Web MCP server enabling AI agents to search, extract & navigate the web
How to run each
io.github.AINative-Studio/ainative-browser-mcp As a local MCP server: npm package
claude mcp add --transport stdio ainative-browser-mcp -- npx -y @ainative/browser-mcpio.github.brightdata/brightdata-mcp As a local MCP server: npm package
claude mcp add --env "API_TOKEN=<YOUR_API_TOKEN>" --transport stdio brightdata-mcp -- npx -y @brightdata/mcpRequires: API_TOKEN (secret)
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
The marketplaces of io.github.AINative-Studio/ainative-browser-mcp publish no settings it asks for, so we do not compare settings.
What it can do: io.github.AINative-Studio/ainative-browser-mcp · What it can do: io.github.brightdata/brightdata-mcp · 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.