browserless vs Screaming Frog SEO Spider MCP Server (headless)
browserless is a plugin bundle for AI coding tools published by browserless. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Screaming Frog SEO Spider MCP Server (headless) is an MCP server published by bzsasson. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  browserless |  Screaming Frog SEO Spider MCP Server (headless) |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 3 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.3 Downloads/month (PyPI): 447 Downloads/week (PyPI): 129 Forks (GitHub): 17 Stars (GitHub): 93 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 | browserless | Screaming Frog SEO Spider MCP Server (headless) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 93 (better) |
| Forks (GitHub) (differs) | 3 (worse) | 17 (better) |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | Remote server (mcp.browserless.io/mcp) | On your machine (screaming-frog-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 11 | Not a bundle |
| Licence (differs) | SSPL-1.0 | Not stated |
| Repository (differs) | github.com/browserless/claude-plugin | github.com/bzsasson/screaming-frog-mcp |
| Changes in the last 7 days (differs) | 4 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 400 (3 days ago) | no remote endpoint we check |
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
browserless
A Claude Code plugin that gives Claude direct access to the Browserless.io REST APIs: scrape webpages, take screenshots, generate PDFs, search the web, map site structures, and run custom browser automation, all from natural language.
Screaming Frog SEO Spider MCP Server (headless)
Headless Screaming Frog SEO Spider via its CLI: run crawls, export and filter data, no GUI needed.
How to run each
browserless As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install browserless@claude-communityScreaming Frog SEO Spider MCP Server (headless) As a local MCP server: PyPI package
claude mcp add --transport stdio screaming-frog-mcp -- uvx screaming-frog-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only browserless has a remote endpoint we 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
The marketplaces of browserless publish no settings it asks for, so we do not compare settings.
What it can do: browserless · What it can do: Screaming Frog SEO Spider MCP Server (headless) · 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 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.