Ext Ops Panel
Open dashboard
Comparison

browserless vs oJo — HTML to image and PDF

browserless is a plugin bundle for AI coding tools published by browserless. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). oJo — HTML to image and PDF is an MCP server published by ojo.so. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplacebrowserlessoJo — HTML to image and PDF
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.7.0
Downloads/month (npm): 852
Downloads/week (npm): 468
Forks (GitHub): 0
Stars (GitHub): 0
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 oJo — HTML to image and PDF
FactbrowserlessoJo — HTML to image and PDF
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub) (differs)3 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.browserless.io/mcp)Remote server (mcp.ojo.so/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
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-plugingithub.com/ojodotso/mcp-server
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 400 (11 h ago)not 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.

oJo — HTML to image and PDF

In its own words, on Official MCP Registry:

Render HTML or templates to a hosted PNG or PDF, in one response. Free previews need no API key.

How to run each

browserless As a Claude Code plugin

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

oJo — HTML to image and PDF As a remote MCP server

Claude Code
claude mcp add --transport http ojo-html-to-image-and-pdf https://mcp.ojo.so/mcp

Requires: OJO_API_KEY (secret)

Commands 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: oJo — HTML to image and PDF · 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.

Where the data comes from: how the catalog is built