AWS Terraform vs TerraVision
AWS Terraform is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). TerraVision is an MCP server published by patrickchugh. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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 Terraform |   TerraVision |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:edb4d307924a Forks (GitHub): 1 806 Pulls (Docker Hub): 59 050 Stars (Docker Hub): 0 Stars (GitHub): 9 779 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.53.0 Downloads/month (PyPI): 5 066 Downloads/week (PyPI): 1 367 Forks (GitHub): 175 Stars (GitHub): 1 653 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 Terraform | TerraVision |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 9 779 (better) | 1 653 (worse) |
| Pulls (Docker Hub) (differs) | 59 050 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 806 (better) | 175 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-terraform) | On your machine (terravision) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 7 | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | Apache-2.0 | AGPL-3.0-only |
| Repository (differs) | github.com/awslabs/mcp | github.com/patrickchugh/terravision |
| Changes in the last 7 days (differs) | 0 | 2 |
| 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 Terraform
Terraform on AWS best practices, infrastructure as code patterns, and security compliance with Checkov.
TerraVision
Draw cloud architecture diagrams with official AWS, Azure and GCP icons from a prompt or Terraform.
How to run each
AWS Terraform As a local MCP server: Docker image
claude mcp add --transport stdio aws-terraform -- docker run -i --rm mcp/aws-terraformTerraVision As a local MCP server: PyPI package
claude mcp add --transport stdio terravision -- uvx --from "terravision[mcp]" terravision mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of TerraVision 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 Terraform · What it can do: TerraVision · 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.