Ext Ops Panel
Open dashboard
Comparison

Archprint vs Terraform

Archprint is an MCP server published by Tommkruix. 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-28. 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
MarketplaceArchprintTerraform
Official MCP Registry Listed
Version: 0.14.0
Downloads/month (npm): 3 478
Downloads/week (npm): 197
Forks (GitHub): 2
Stars (GitHub): 7
Not marked · First seen
Listed
Version: 1.4.1
Forks (GitHub): 199
Stars (GitHub): 1 554
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: not stated
Forks (GitHub): 4 698
Stars (GitHub): 45 000
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:11dd418bba60
Forks (GitHub): 199
Stars (GitHub): 1 554
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

Archprint vs Terraform
FactArchprintTerraform
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)7 (worse)45 000 (better)
Forks (GitHub) (differs)2 (worse)4 698 (better)
Last release (differs)2026-10-20 (worse)2026-10-24 (better)
Where it runs (differs)On your machine (archprint)On your machine (docker.io/hashicorp/terraform-mcp-server:1.4.1)
Transportstdiostdio
Tools it declares (differs)Not published9
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle1
Licence (differs)Not statedMPL-2.0
Repository (differs)github.com/tommkruix/archprintgithub.com/hashicorp/terraform-mcp-server
Changes in the last 7 days (differs)03
First seen2026-10-112026-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

Archprint

In its own words, on Official MCP Registry:

Mine the architecture rules your TypeScript repo already enforces, with the evidence attached.

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

Archprint As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio archprint -- npx -y archprint mcp

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.4.1

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

Tools each declares

The marketplaces of Archprint 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: Archprint · 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.

Where the data comes from: how the catalog is built