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.

DimensiontfmcpA local-first MCP server for Terraform.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS64 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions14 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers who need AI-assisted Terraform project and plan inspection.
  • Users managing local Terraform directories through Claude Desktop.
  • Teams needing plan-risk, state-drift, module-health, or security checks.
  • 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
  • Situations requiring infrastructure changes without human review.
  • Users without Terraform CLI or a usable Terraform project directory.
  • Production environments that cannot tolerate active-development software.
  • 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
  • Read and operate on the Terraform project directory specified by TERRAFORM_DIR.
  • Access the Terraform CLI available in PATH.
  • Use configured TFE_ADDRESS and TFE_TOKEN for HCP Terraform/Terraform Enterprise queries.
  • Use appropriate Terraform or HCP/TFE permissions when write operations are enabled.
  • 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
  • Apply and destroy are disabled by default but can change or destroy infrastructure when enabled.
  • Auto-approve is disabled by default; enabling it reduces manual confirmation.
  • Incorrect directories, credentials, permissions, or AI-generated plans can cause unintended changes.
  • Misconfigured Streamable HTTP can broaden network exposure; TFE_TOKEN and TLS private keys are sensitive.
  • The project is under active development, so review all operations before production use.
  • 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 DesktopClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools820