Ext Ops Panel
Open dashboard
Comparison

browserless vs oassis — web scraping, crawling and browser control for AI agents

browserless is a plugin bundle for AI coding tools published by browserless. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). oassis — web scraping, crawling and browser control for AI agents is an MCP server published by oassis.dev. 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

Where each is published
Marketplacebrowserlessoassis — web scraping, crawling and browser control for AI agents
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: 1.0.1
No figure published
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

browserless vs oassis — web scraping, crawling and browser control for AI agents
Factbrowserlessoassis — web scraping, crawling and browser control for AI agents
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)3No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.browserless.io/mcp)Remote server (api.oassis.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)11Not a bundle
Licence (differs)SSPL-1.0Not stated
Repository (differs)github.com/browserless/claude-pluginNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last checknot checked yetnot 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

browserless

In its own words, on Claude Code: claude-plugins-community:

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.

oassis — web scraping, crawling and browser control for AI agents

In its own words, on Official MCP Registry:

Scrape to markdown, map and crawl sites, drive a real browser. Pay per call, no API key, no signup.

How to run each

browserless As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install browserless@claude-community

oassis — web scraping, crawling and browser control for AI agents As a remote MCP server

Claude Code
claude mcp add --transport http scraper-crawler https://api.oassis.dev/mcp

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: browserless · What it can do: oassis — web scraping, crawling and browser control for AI agents · 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.

Where the data comes from: how the catalog is built