Ext Ops Panel
Open dashboard
Comparison

AWS AppSync vs Cloudinary Environment Config

AWS AppSync is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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)). 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

Where each is published
MarketplaceAWS AppSyncCloudinary Environment Config
Docker MCP Catalog Listed
Version: sha256:5fc57706f27b
Forks (GitHub): 1 870
Pulls (Docker Hub): 13 582
Stars (Docker Hub): 0
Stars (GitHub): 9 913
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.6.4
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.6.4
Downloads/month (npm): 1 093
Downloads/week (npm): 421
Forks (GitHub): 1
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

AWS AppSync vs Cloudinary Environment Config
FactAWS AppSyncCloudinary Environment Config
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)9 913 (better)0 (worse)
Pulls (Docker Hub) (differs)13 582No figure on Docker Hub
Forks (GitHub) (differs)1 870 (better)1 (worse)
Last release (differs)Not published2026-11-13
Where it runs (differs)On your machine (mcp/aws-appsync-mcp-server)Remote server or your machine
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)10Not published
Environment variables it asks for (differs)5, secrets among them: 23, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/mcpgithub.com/cloudinary/environment-config-mcp
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)no remote endpoint we checkResponded 13 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

AWS AppSync

In its own words, on Docker MCP Catalog:

Manage applications powered by AWS AppSync.

Cloudinary Environment Config

In its own words, on Official MCP Registry:

Manage Cloudinary upload presets, named transformations, mappings, triggers, and streaming profiles.

How to run each

AWS AppSync As a local MCP server: Docker image

Claude Code
claude mcp add --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --env "AWS_SESSION_TOKEN=<YOUR_AWS_SESSION_TOKEN>" --transport stdio aws-appsync -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN mcp/aws-appsync-mcp-server

Requires: AWS_SECRET_ACCESS_KEY (secret), AWS_SESSION_TOKEN (secret)

Cloudinary Environment Config As a remote MCP server

Claude Code
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

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

Only Cloudinary Environment Config has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Cloudinary Environment Config publish no list of tools, so we do not compare tools.

Settings each asks for

Only AWS AppSync asks for

  • AWS_ACCESS_KEY_ID
  • AWS_PROFILE
  • AWS_REGION
  • AWS_SECRET_ACCESS_KEY (secret)
  • AWS_SESSION_TOKEN (secret)

Only Cloudinary Environment Config asks for

  • CLOUDINARY_API_KEY
  • CLOUDINARY_API_SECRET (secret)
  • CLOUDINARY_CLOUD_NAME

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: AWS AppSync · What it can do: Cloudinary Environment Config · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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