Ext Ops Panel
Open dashboard
Comparison

mcp-image-viewer vs cloudinary

mcp-image-viewer is a plugin bundle for AI coding tools published by androidZzT. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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). 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
Marketplacemcp-image-viewercloudinary
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.1.2
Forks (GitHub): 3
Stars (GitHub): 0
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 1.2.0
Forks (GitHub): 3
Stars (GitHub): 0
Not marked · First seen
Claude: knowledge-work-plugins Not listed Listed
Version: 1.2.0
Forks (GitHub): 3
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

mcp-image-viewer vs cloudinary
Factmcp-image-viewercloudinary
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub)00
Forks (GitHub) (differs)0 (worse)3 (better)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)18
LicenceMITMIT
Repository (differs)github.com/androidzzt/mcp-image-viewergithub.com/cloudinary-devs/cloudinary-plugin
Changes in the last 7 days00
First seen2026-10-112026-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

mcp-image-viewer

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

Claude Code plugin that automatically displays images returned by MCP tools. Fix Claude Code CLI shows an [Image] .

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.

How to run each

mcp-image-viewer

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

cloudinary As a Claude Code plugin

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

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: mcp-image-viewer · What it can do: cloudinary · 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 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. 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