Ext Ops Panel
Open dashboard
Comparison

AWS CloudFormation vs CloudPloy

AWS CloudFormation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). CloudPloy is an MCP server published by cloudploy.com. 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
MarketplaceAWS CloudFormationCloudPloy
Docker MCP Catalog Listed
Version: sha256:d1c0846eb6e5
Forks (GitHub): 1 805
Pulls (Docker Hub): 17 654
Stars (Docker Hub): 0
Stars (GitHub): 9 773
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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 CloudFormation vs CloudPloy
FactAWS CloudFormationCloudPloy
Marketplaces that list it11
Stars (GitHub) (differs)9 773No figure on GitHub
Pulls (Docker Hub) (differs)17 654No figure on Docker Hub
Forks (GitHub) (differs)1 805No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/cfn-mcp-server)Remote server (app.cloudploy.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)8Not published
Environment variables it asks for (differs)5, secrets among them: 2Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/mcpNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 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 CloudFormation

In its own words, on Docker MCP Catalog:

CloudFormation resource management via Cloud Control API.

CloudPloy

In its own words, on Official MCP Registry:

Deploy an app onto a server in your own cloud account.

How to run each

AWS CloudFormation 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 awslabs-cfn -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN mcp/cfn-mcp-server

Requires: AWS_SECRET_ACCESS_KEY (secret), AWS_SESSION_TOKEN (secret)

CloudPloy As a remote MCP server

Claude Code
claude mcp add --transport http cloudploy https://app.cloudploy.com/mcp

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

Only CloudPloy has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of CloudPloy publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of CloudPloy publish no settings it asks for, so we do not compare settings.

What it can do: AWS CloudFormation · What it can do: CloudPloy · 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. 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