Ext Ops Panel
Open dashboard
Comparison

cloudinary vs Giggy Speech MCP

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). Giggy Speech MCP is an MCP server published by giggy.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-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
MarketplacecloudinaryGiggy Speech MCP
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: 1.0.3
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 Giggy Speech MCP
FactcloudinaryGiggy Speech MCP
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 (giggy.ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)8Not a bundle
Licence (differs)MITISC
Repository (differs)github.com/cloudinary-devs/cloudinary-plugingithub.com/giggy-ai/giggy-mcp
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-10-13
Endpoint at the last check (differs)no remote endpoint we checkResponded 16 h ago

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.

Giggy Speech MCP

In its own words, on Official MCP Registry:

Giggy speech tools for AI agents: discover voices, generate speech and transcribe recordings.

How to run each

cloudinary As a Claude Code plugin

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

Giggy Speech MCP As a remote MCP server

Claude Code
claude mcp add --transport http speech https://giggy.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Giggy Speech MCP 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

Neither one's marketplaces publish the settings it asks for.

What it can do: cloudinary · What it can do: Giggy Speech MCP · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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