AWS Builder vs Terraform
AWS Builder is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). 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-24. 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 |  Terraform | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.4.1 Forks (GitHub): 200 Stars (GitHub): 1 553 Not marked · First seen |
| Claude Code: claude-plugins-official | Not listed | Listed Version: not stated Forks (GitHub): 4 643 Stars (GitHub): 44 178 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:11dd418bba60 Forks (GitHub): 200 Stars (GitHub): 1 553 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 Builder | Terraform |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 44 178 |
| Forks (GitHub) (differs) | No figure on GitHub | 4 643 |
| Last release (differs) | Not published | 2026-10-24 |
| Where it runs (differs) | Remote server (aws-builder-mcp.vercel.app/api/mcp) | On your machine (docker.io/hashicorp/terraform-mcp-server:1.4.1) |
| Transport (differs) | SSE | stdio |
| Tools it declares (differs) | Not published | 9 |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | Not stated | MPL-2.0 |
| Repository (differs) | Not stated | github.com/hashicorp/terraform-mcp-server |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 402 (3 days ago) | no remote endpoint we check |
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 Builder
AWS CloudFormation and Terraform infrastructure blueprint builder.
Terraform
Generate more accurate Terraform and automate workflows for HCP Terraform and Terraform Enterprise
How to run each
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
Terraform As a local MCP server: Docker image
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.4.1Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only AWS Builder has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of AWS Builder publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: AWS Builder · What it can do: Terraform · Compare two other plugins
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. 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.