AWS Cloud Control API vs cloud-tools
AWS Cloud Control API is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). cloud-tools is an MCP server published by munhq. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  AWS Cloud Control API |   cloud-tools |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:b53d235b43c4 Forks (GitHub): 1 805 Pulls (Docker Hub): 14 541 Stars (Docker Hub): 0 Stars (GitHub): 9 773 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Downloads/month (npm): 154 Downloads/week (npm): 25 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 | AWS Cloud Control API | cloud-tools |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 773 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 14 541 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 805 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/ccapi-mcp-server) | On your machine (@munhq/cloud-tools) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 14 | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 1 | 1, secrets among them: 0 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/munhq/cloud-tools |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
AWS Cloud Control API
Direct resource management with security scanning.
cloud-tools
Multi-cloud cost, inventory and waste analysis over MCP: AWS, GCP, Cloudflare and OVH.
How to run each
AWS Cloud Control API As a local MCP server: Docker image
claude mcp add --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --transport stdio awslabs-ccapi -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY mcp/ccapi-mcp-serverRequires: AWS_SECRET_ACCESS_KEY (secret)
cloud-tools As a local MCP server: npm package
claude mcp add --transport stdio cloud-tools -- npx -y @munhq/cloud-toolsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of cloud-tools publish no list of tools, so we do not compare tools.
Settings each asks for
Only AWS Cloud Control API asks for
AWS_ACCESS_KEY_IDAWS_PROFILEAWS_REGIONAWS_SECRET_ACCESS_KEY (secret)
Only cloud-tools asks for
CLOUD_TOOLS_MODE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: AWS Cloud Control API · What it can do: cloud-tools · 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.