Cloudinary Environment Config vs io.github.AceDataCloud/mcp-acedatacloud
Cloudinary Environment Config is an MCP server published by cloudinary.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). io.github.AceDataCloud/mcp-acedatacloud is an MCP server published by AceDataCloud. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-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
| Marketplace |  Cloudinary Environment Config |  io.github.AceDataCloud/mcp-acedatacloud |
|---|---|---|
| Official MCP Registry | Listed Version: 0.6.4 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2026.11.14.0 Downloads/month (PyPI): 6 042 Downloads/week (PyPI): 693 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.6.4 Downloads/month (npm): 1 093 Downloads/week (npm): 421 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| PyPI (MCP servers) | Not listed | Listed Version: 2026.11.12.0 Downloads/month (PyPI): 6 042 Downloads/week (PyPI): 693 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
| Fact | Cloudinary Environment Config | io.github.AceDataCloud/mcp-acedatacloud |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | 2026-11-13 (worse) | 2026-11-14 (better) |
| Where it runs | Remote server or your machine | Remote server or your machine |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/cloudinary/environment-config-mcp | github.com/acedatacloud/acedatacloudmcp |
| Changes in the last 7 days (differs) | 4 | 5 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 13 h ago | Responded 19 h ago, requires authentication |
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 Environment Config
Manage Cloudinary upload presets, named transformations, mappings, triggers, and streaming profiles.
io.github.AceDataCloud/mcp-acedatacloud
Manage your AceData Cloud account: services, pricing, APIs, docs, balance, usage, keys & orders
How to run each
Cloudinary Environment Config As a remote MCP server
claude mcp add --transport http environment-config-mcp https://environment-config.mcp.cloudinary.com/mcp --header "cloudinary-api-secret: <YOUR_CLOUDINARY_API_SECRET>"Requires: CLOUDINARY_API_KEY, CLOUDINARY_API_SECRET (secret), CLOUDINARY_CLOUD_NAME, cloudinary-api-secret header
io.github.AceDataCloud/mcp-acedatacloud As a remote MCP server
claude mcp add --transport http mcp-acedatacloud https://mcp.acedata.cloud/mcpRequires: ACEDATACLOUD_PLATFORM_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily 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
Only Cloudinary Environment Config asks for
CLOUDINARY_API_KEYCLOUDINARY_API_SECRET (secret)CLOUDINARY_CLOUD_NAME
Only io.github.AceDataCloud/mcp-acedatacloud asks for
ACEDATACLOUD_PLATFORM_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Cloudinary Environment Config · What it can do: io.github.AceDataCloud/mcp-acedatacloud · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.