Terraform Engine MCP Server
Related Servers
Alternatives to Terraform Engine MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityFmaintenanceEnables AI assistants to manage infrastructure using Ansible and Terraform with 58 tools for playbooks, provisioning, security scanning, and more.877MIT
- AlicenseNot gradedqualityCmaintenanceExposes any OpenAPI spec endpoints as AI agent tools via stdio, requiring no code generation or maintenance.18MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that exposes Terraform CLI operations as tools for Claude and other MCP-compatible AI assistants, enabling AI-driven infrastructure-as-code workflows including planning, applying, and validating Terraform configurations.125 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Argo CD applications through natural language, providing tools for cluster, project, application, and resource management via stdio and HTTP transports.Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI coding agents to plan, policy-check, and cost-estimate Terraform changes while requiring human approval through Slack or CLI before any terraform apply can execute.97 npmMIT
- AlicenseNot gradedqualityAmaintenance🌍 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
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing tasks, getting task schema, provisioning deployments, checking deployment status, and destroying deployments. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with underscores (e.g., list_tasks, provision_task, destroy_deployment), making them predictable and easy to understand.
Five tools is an appropriate scope for managing Terraform tasks and their deployments: sufficient to cover listing, schema retrieval, provisioning, status checking, and destruction without being overwhelming.
The set covers the main lifecycle (create, read, delete) but lacks a tool to list existing deployments, which is a notable gap for agents that need to manage multiple deployments. Additionally, there is no update or modification capability.