Skip to main content
Glama
Sign In
tfplan-mcp

tfplan-mcp

by 0xmortuex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to tfplan-mcp

No user-submitted related servers found.

    Related Servers

    • tfplan-mcp

      0xmortuex
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI to risk-review Terraform and OpenTofu plan files over MCP stdio by summarizing plans, ranking dangerous changes, diffing resources with secrets masked, and comparing two plans without running Terraform.
      MIT

    • terraform-mcp

      imashish-in
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables state-aware Terraform/OpenTofu plan evaluation against live AWS topology and CloudWatch telemetry, detecting reliability blast radius and FinOps waste before merge.
      Apache 2.0

    • InfraGuard

      hfmohammed
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only inspection of Kubernetes resources and Terraform plans, retrieval of policy findings, and schema and policy validation of manifests and patches without applying changes.
      MIT

    • opendrs

      error-path
      A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents to compute a 0-1 diff risk score for the current branch or any pull request, exposing the driving signals, evidence, tier and resulting auto-approve or human-review policy decision. Agents can use it to decide whether a low-blast-radius, AI-reviewed PR is safe to merge automatically while flagging risky changes for a human.
      6
      202 npm
      2
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool targets a distinct facet of plan analysis: overview, risk ranking, single-resource diff, filtered listing, replacement explanation, plan-to-plan comparison, and outputs/drift. The main potential confusion is between list_changes, compare_plans, and plan_summary, since all surface resource changes, but the descriptions draw clear boundaries (filter/cap vs two-plan comparison vs counts).

    Naming Consistency3/5

    Most names are verb_noun (diff_resource, list_changes, explain_replace, compare_plans), but plan_summary, risky_changes, and outputs_and_drift are noun-first, mixing conventions. Names remain readable and descriptive despite the inconsistency.

    Tool Count5/5

    Seven tools is well-scoped for a Terraform plan analysis server, with each tool covering a clearly separate analytical need. Nothing feels redundant or missing at the count level.

    Completeness4/5

    The surface covers the plan lifecycle well: summary, change listing, attribute diffs, replacement reasoning, risk assessment, plan comparison, and outputs/drift. Minor gaps exist, such as no way to dump a full resource's planned configuration beyond a diff or to query state/configuration outside the plan.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources