AWS Documentation vs AWS Cloud Control API
AWS Documentation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). AWS Cloud Control API is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:07888232dde9 Forks (GitHub): 1 805 Pulls (Docker Hub): 118 690 Stars (Docker Hub): 2 Stars (GitHub): 9 773 Not marked · First seen |
Listed Version: sha256:b53d235b43c4 Forks (GitHub): 1 805 Pulls (Docker Hub): 14 515 Stars (Docker Hub): 0 Stars (GitHub): 9 773 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 Documentation | AWS Cloud Control API |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 9 773 | 9 773 |
| Pulls (Docker Hub) (differs) | 118 690 (better) | 14 515 (worse) |
| Forks (GitHub) | 1 805 | 1 805 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-documentation) | On your machine (mcp/ccapi-mcp-server) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 4 | 14 |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 1 |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository | github.com/awslabs/mcp | github.com/awslabs/mcp |
| 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 Documentation
Tools to access AWS documentation, search for content, and get recommendations.
AWS Cloud Control API
Direct resource management with security scanning.
How to run each
AWS Documentation As a local MCP server: Docker image
claude mcp add --transport stdio aws-documentation -- docker run -i --rm mcp/aws-documentationAWS 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)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Only AWS Documentation declares
read_documentationread_sectionsrecommendsearch_documentation
Only AWS Cloud Control API declares
check_environment_variablescreate_resourcecreate_templatedelete_resourceexplaingenerate_infrastructure_codeget_aws_account_infoget_aws_session_infoget_resourceget_resource_request_statusget_resource_schema_informationlist_resources
Show the remaining 2
run_checkovupdate_resource
Both declare
None
Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of AWS Documentation publish no settings it asks for, so we do not compare settings.
What it can do: AWS Documentation · What it can do: AWS Cloud Control API · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.