Comparison

AWS Cloud Control API vs Terraform

AWS Cloud Control API is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Terraform is an MCP server published by hashicorp. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-official, Docker MCP Catalog). As of our marketplace pass on 2026-10-18. 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
Marketplace	AWS Cloud Control API	Terraform
Docker MCP Catalog	Listed Version: sha256:b53d235b43c4 Forks (GitHub): 1 815 Pulls (Docker Hub): 14 644 Stars (Docker Hub): 0 Stars (GitHub): 9 788 Not marked · First seen 2026-10-11	Listed Version: sha256:423a6b8e2ee0 Forks (GitHub): 199 Stars (GitHub): 1 550 Not marked · First seen 2026-10-11
Official MCP Registry	Not listed	Listed Version: 1.0.0 Forks (GitHub): 199 Stars (GitHub): 1 550 Not marked · First seen 2026-10-11
Claude Code: claude-plugins-official	Not listed	Listed Version: not stated Forks (GitHub): 4 462 Stars (GitHub): 41 694 Not marked · First seen 2026-10-11

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 Terraform
Fact	AWS Cloud Control API	Terraform
Marketplaces that list it (differs)	1 (worse)	3 (better)
Stars (GitHub) (differs)	9 788 (worse)	41 694 (better)
Pulls (Docker Hub) (differs)	14 644	No figure on Docker Hub
Forks (GitHub) (differs)	1 815 (worse)	4 462 (better)
Last release	Not published	Not published
Where it runs (differs)	On your machine (mcp/ccapi-mcp-server)	On your machine (docker.io/hashicorp/terraform-mcp-server:1.0.0)
Transport	stdio	stdio
Tools it declares (differs)	14	9
Environment variables it asks for (differs)	4, secrets among them: 1	Not published
Parts of the bundle (differs)	Not a bundle	1
Licence (differs)	Apache-2.0	MPL-2.0
Repository (differs)	github.com/awslabs/mcp	github.com/hashicorp/terraform-mcp-server
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

In its own words, on Docker MCP Catalog:

Direct resource management with security scanning.

Terraform

In its own words, on Official MCP Registry:

Generate more accurate Terraform and automate workflows for HCP Terraform and Terraform Enterprise

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)

Terraform As a local MCP server: Docker image

Claude Code

claude mcp add --transport stdio terraform-mcp-server -- docker run -i --rm -e "TFE_ADDRESS=<YOUR_ADDRESS>" -e "TFE_TOKEN=<YOUR_TOKEN>" -e "ENABLE_TF_OPERATIONS=<YOUR_ENABLED>" docker.io/hashicorp/terraform-mcp-server:1.0.0

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

Tools each declares

Only AWS Cloud Control API declares

check_environment_variables
create_resource
create_template
delete_resource
explain
generate_infrastructure_code
get_aws_account_info
get_aws_session_info
get_resource
get_resource_request_status
get_resource_schema_information
list_resources

Show the remaining 2

run_checkov
update_resource

Only Terraform declares

get_latest_module_version
get_latest_provider_version
get_module_details
get_policy_details
get_provider_capabilities
get_provider_details
search_modules
search_policies
search_providers

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 Terraform publish no settings it asks for, so we do not compare settings.

What it can do: AWS Cloud Control API · What it can do: Terraform · 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 the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on 2026-10-18. We publish no contact details for plugin publishers.