M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionTerraform MCP ServerGenerate more accurate Terraform and automate workflows for HCP Terraform and Terraform Enterprise.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS65 / 100 · C79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions14 / 2018 / 20
Maintenance14 / 2016 / 20
Documentation16 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Teams using HCP Terraform or Terraform Enterprise
  • Developers integrating Terraform into IDEs like VS Code and Cursor
  • DevOps engineers automating IaC workflows
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Not suitable for local-only Terraform use without HCP Terraform/Terraform Enterprise
  • Not for environments requiring complex custom instructions or high security without careful review
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Requires Terraform API token (TFE_TOKEN) to access HCP Terraform or Terraform Enterprise
  • Runs in a Docker container, requiring network access
  • If ENABLE_TF_OPERATIONS is enabled, can execute Terraform operations, requiring explicit approval
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • Server may expose Terraform data to MCP client and LLM; avoid untrusted clients
  • Outputs are generated dynamically; review to align with security and cost policies
  • In streamable-http mode, TFE_ADDRESS cannot be set by clients to prevent redirect attacks
  • Shared secret (TF_MCP_SHARED_SECRET) should only be used over TLS
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00