Ext Ops Panel
Open dashboard
Comparison

cloudinary vs oJo — HTML to image and PDF

cloudinary is a plugin bundle for AI coding tools published by cloudinary-devs. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community). 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-12. 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
MarketplacecloudinaryoJo — HTML to image and PDF
Claude Code: claude-plugins-official Listed
Version: 1.2.0
Forks (GitHub): 3
Stars (GitHub): 0
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Listed
Version: 1.2.0
Forks (GitHub): 3
Stars (GitHub): 0
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 1.1.2
Forks (GitHub): 3
Stars (GitHub): 0
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

cloudinary vs oJo — HTML to image and PDF
FactcloudinaryoJo — HTML to image and PDF
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub)00
Forks (GitHub) (differs)3 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.ojo.so/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)8Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/cloudinary-devs/cloudinary-plugingithub.com/ojodotso/mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot 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

cloudinary

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

Use Cloudinary directly in Claude. Manage assets, apply transformations, optimize media, and more through natural conversation.

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

cloudinary As a Claude Code plugin

Claude Code
/plugin install cloudinary@claude-plugins-official

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.

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 cloudinary publish no settings it asks for, so we do not compare settings.

What it can do: cloudinary · 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-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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