Ext Ops Panel
Open dashboard
Comparison

AWS Cloud Control API vs cloudcostwise

AWS Cloud Control API is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). cloudcostwise is an MCP server published by cloudwise-app. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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

Where each is published
MarketplaceAWS Cloud Control APIcloudcostwise
Docker MCP Catalog Listed
Version: sha256:b53d235b43c4
Forks (GitHub): 1 805
Pulls (Docker Hub): 14 541
Stars (Docker Hub): 0
Stars (GitHub): 9 776
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.8
Downloads/month (PyPI): 420
Downloads/week (PyPI): 597
Forks (GitHub): 1
Stars (GitHub): 1
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 Cloud Control API vs cloudcostwise
FactAWS Cloud Control APIcloudcostwise
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)9 776 (better)1 (worse)
Pulls (Docker Hub) (differs)14 541No figure on Docker Hub
Forks (GitHub) (differs)1 805 (better)1 (worse)
Last release (differs)Not published2026-10-13
Where it runs (differs)On your machine (mcp/ccapi-mcp-server)On your machine (cloudcostwise)
Transportstdiostdio
Tools it declares (differs)14Not published
Environment variables it asks for (differs)4, secrets among them: 11, secrets among them: 0
Parts of the bundle (differs)Not a bundle1
Licence (differs)Apache-2.0FSL-1.1-ALv2
Repository (differs)github.com/awslabs/mcpgithub.com/cloudwise-app/cloudcostwise
Changes in the last 7 days (differs)04
First seen2026-10-112026-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

In its own words, on Docker MCP Catalog:

Direct resource management with security scanning.

cloudcostwise

In its own words, on Official MCP Registry:

Find AWS waste with your own read-only credentials. Runs locally. Nothing is sent to CloudWise.

How to run each

AWS Cloud Control API As a local MCP server: Docker image

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

Requires: AWS_SECRET_ACCESS_KEY (secret)

cloudcostwise As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio cloudcostwise -- uvx cloudcostwise mcp

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

Tools each declares

The marketplaces of cloudcostwise 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_ID
  • AWS_REGION
  • AWS_SECRET_ACCESS_KEY (secret)

Only cloudcostwise asks for

None

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: cloudcostwise · 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. 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