atmos vs Terraform
atmos is a plugin bundle for AI coding tools published by Cloud Posse. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-21. 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 |  atmos |  Terraform |
|---|---|---|
| Community marketplace cloudposse/atmos | Listed Version: 1.233.0 Forks (GitHub): 193 Stars (GitHub): 1 405 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 200 Stars (GitHub): 1 551 Not marked · First seen |
| Claude Code: claude-plugins-official | Not listed | Listed Version: not stated Forks (GitHub): 4 598 Stars (GitHub): 43 563 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:423a6b8e2ee0 Forks (GitHub): 200 Stars (GitHub): 1 551 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 | atmos | Terraform |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 1 405 (worse) | 43 563 (better) |
| Forks (GitHub) (differs) | 193 (worse) | 4 598 (better) |
| Last release (differs) | 2026-10-21 | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (docker.io/hashicorp/terraform-mcp-server:1.0.0) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 9 |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 56 | 1 |
| Licence (differs) | Apache-2.0 | MPL-2.0 |
| Repository (differs) | github.com/cloudposse/atmos | github.com/hashicorp/terraform-mcp-server |
| Changes in the last 7 days (differs) | 5 | 0 |
| First seen (differs) | 2026-10-15 | 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
atmos
Atmos skills for AI coding assistants: Terraform/Helmfile/Packer/Ansible orchestration, stacks, remote imports, containers, emulators, Native CI, Atmos Pro, Auth, GitOps, secrets, cache, hooks, workflows, YAML functions, and modernization.
Terraform
Generate more accurate Terraform and automate workflows for HCP Terraform and Terraform Enterprise
How to run each
atmos As a Claude Code plugin
/plugin marketplace add cloudposse/atmos
/plugin install atmos@cloudposseTerraform 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.0.0Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of atmos 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: atmos · What it can do: Terraform · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.