AWS Cloud Control API vs AWS Builder
AWS Cloud Control API is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). AWS Builder is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-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 |  AWS Cloud Control API | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:b53d235b43c4 Forks (GitHub): 1 805 Pulls (Docker Hub): 14 552 Stars (Docker Hub): 0 Stars (GitHub): 9 776 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
| Fact | AWS Cloud Control API | AWS Builder |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 776 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 14 552 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 805 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/ccapi-mcp-server) | Remote server (aws-builder-mcp.vercel.app/api/mcp) |
| Transport (differs) | stdio | SSE |
| Tools it declares (differs) | 14 | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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.
AWS Builder
AWS CloudFormation and Terraform infrastructure blueprint builder.
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)
AWS Builder As a remote MCP server
claude mcp add --transport sse aws-builder https://aws-builder-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"Requires: payment-signature header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of AWS Builder publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of AWS Builder publish no settings it asks for, so we do not compare settings.
What it can do: AWS Cloud Control API · What it can do: AWS Builder · 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.