DriftHound MCP Server
OfficialRelated Servers
Alternatives to DriftHound MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables Claude to interact with Infracost for Terraform cost estimation and cloud governance. Supports generating cost breakdowns, comparing configurations, creating tagging policies, setting up cost guardrails, and posting cost comments to PRs.162MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to connect to multi-cloud DevOps control planes for Terraform plan inspection, drift detection and remediation, cost estimation, incident triage, and cloud resource discovery across Azure, AWS, and GCP. It supports autonomous workflows for PR review, FinOps optimization, and self-healing operations through MCP tools.MIT
- AlicenseNot gradedqualityBmaintenance🌍 Terraform Model Context Protocol (MCP) Tool - An experimental CLI tool that enables AI assistants to manage and operate Terraform environments. Supports reading Terraform configurations, analyzing plans, applying configurations, and managing state with Claude Desktop integration. ⚡️371MIT
- FlicenseNot gradedqualityAmaintenanceExposes Terraform/Terragrunt tooling as Claude Code tools for generating variables.tf and mock outputs automatically from input files.-
- AlicenseNot gradedqualityCmaintenanceEnables any MCP client to detect Claude Code configuration that is silently ignored, such as agent files that fail to load, unknown frontmatter fields, parent-folder settings, conflicting MCP server entries and drift since a baseline. Exposes read-only tools that return findings with exact edits, the fix prompt, and explanations of each check, without modifying any files.Apache 2.0
- AlicenseNot gradedqualityFmaintenanceEnables management of Facets Control Plane projects, resources, environments, and deployments through Claude, offering secure infrastructure automation workflows.1MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing projects with drift, listing environments, getting drift details, and getting environment info. No ambiguity in their roles.
All tool names follow a consistent verb_noun pattern (list_projects_with_drift, list_environments, get_drift_details, get_environment_info). The naming is predictable and readable.
With 4 tools, the set is well-scoped for a drift monitoring server. Each tool covers a distinct aspect: discovery, details, and context. Not too few or too many for the domain.
The tools cover discovery and information retrieval for drift detection. However, there is no tool to trigger a drift check or perform remediation, which may be intentional but leaves a minor gap.