Comparison

Terraform vs Ecfr

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). Ecfr is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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	Terraform	Ecfr
Official MCP Registry	Listed Version: 1.4.1 Forks (GitHub): 203 Stars (GitHub): 1 557 Not marked · First seen 2026-10-11	Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen 2026-10-11
Claude Code: claude-plugins-official	Listed Version: not stated Forks (GitHub): 4 858 Stars (GitHub): 46 630 Not marked · First seen 2026-10-11	Not listed
Docker MCP Catalog	Listed Version: sha256:11dd418bba60 Forks (GitHub): 203 Stars (GitHub): 1 557 Not marked · First seen 2026-10-11	Not listed

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

Terraform vs Ecfr
Fact	Terraform	Ecfr
Marketplaces that list it (differs)	3 (better)	1 (worse)
Stars (GitHub) (differs)	46 630 (better)	0 (worse)
Forks (GitHub) (differs)	4 858 (better)	0 (worse)
Last release (differs)	2026-10-24 (worse)	2026-11-01 (better)
Where it runs (differs)	On your machine (docker.io/hashicorp/terraform-mcp-server:1.4.1)	Remote server (gateway.pipeworx.io/ecfr/mcp)
Transport (differs)	stdio	Streamable HTTP
Tools it declares (differs)	9	Not published
Environment variables it asks for (differs)	Not published	1, secrets among them: 1
Parts of the bundle (differs)	1	Not a bundle
Licence (differs)	MPL-2.0	Not stated
Repository (differs)	github.com/hashicorp/terraform-mcp-server	github.com/pipeworx-io/mcp-ecfr
Changes in the last 7 days	0	0
First seen	2026-10-11	2026-10-11
Endpoint at the last check (differs)	no remote endpoint we check	Responded 7 h ago

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

Terraform

In its own words, on Official MCP Registry:

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

Ecfr

In its own words, on Official MCP Registry:

eCFR (Electronic Code of Federal Regulations) MCP.

How to run each

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

Ecfr As a remote MCP server

Claude Code

claude mcp add --transport http ecfr https://gateway.pipeworx.io/ecfr/mcp

Requires: PIPEWORX_API_KEY (secret)

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

Only Ecfr has a remote endpoint we check. How we check endpoints

Tools each declares

Only Terraform has

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

Only Ecfr has

ai_visibility_check
archive_compare
archive_evidence
ask_pipeworx
ask_pipeworx_beta
ask_pipeworx_grounded
bet_research
classify_row
company_facts
company_register_search
compare_entities
deep_research

Show the remaining 33

discover_tools
entity_profile
forget
generate_llms_txt
get_section_text
kalshi_weather_edge
list_subscriptions
list_titles
pipeworx_feedback
pipeworx_trending
polymarket_arbitrage
polymarket_edge_tracker
polymarket_edges
polymarket_fill_risk
polymarket_kalshi_spread
recall
recent_alerts
recent_changes
release_calendar_markets
remember
research_row
resolution_audit
resolution_diff
resolve_entity
scan_competitor_ai_presence
scan_dependency
search_regulations
search_within
subscribe
suggest_questions
title_structure
unsubscribe
validate_claim

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Ecfr as of 2026-10-15). 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: Terraform · What it can do: Ecfr · 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 2026-11-10. We publish no contact details for plugin publishers.