Integrate Terraform Registry APIs and HCP Terraform with AI assistants for advanced IaC automation.
Visit WebsiteFreeVisit Website
TL;DR - Terraform MCP Server
- Integrates Terraform with AI assistants via Model Context Protocol (MCP).
- Enables AI-driven automation for Terraform Registry, HCP Terraform, and Terraform Enterprise.
- Supports workspace management, variable handling, and run operations through AI clients.
Pricing: Free forever
Best for: Individuals & startups
Pros & Cons
Pros
- Facilitates advanced automation of Terraform workflows using AI.
- Provides comprehensive integration with public and private Terraform registries.
- Supports both local and HTTP-based communication for flexibility.
- Offers granular control over security settings like CORS and origin restrictions.
- Enables AI assistants to manage Terraform Cloud/Enterprise workspaces and runs.
Cons
- Primarily intended for local use, requiring careful security configuration for broader deployment.
- Exposes Terraform data to MCP clients and LLMs, necessitating trusted AI tools.
- Outputs and recommendations from AI are dynamic and require user review for security and compliance.
Preview
Key Features
Dual Transport Support (Stdio and StreamableHTTP)Terraform Registry Integration (providers, modules, policies)HCP Terraform & Terraform Enterprise Support (workspace management, private registry access)Workspace Operations (create, update, delete workspaces, variables, tags, run management)Configurable environment variables for Terraform Enterprise address, token, and TLS verificationLogging level and format configurationHTTP server binding and endpoint configuration for StreamableHTTP modeCORS and origin restriction for StreamableHTTP transport
Pricing Plans
Open Source
Free
- Full source code access
- Community support
- Self-hosted
What is Terraform MCP Server?
The Terraform MCP Server is a Model Context Protocol (MCP) server designed to seamlessly integrate with the Terraform ecosystem. It enables advanced automation and interaction capabilities for Infrastructure as Code (IaC) development by providing direct access to Terraform Registry APIs and supporting HCP Terraform and Terraform Enterprise.
This server is intended for developers and organizations leveraging AI assistants and large language models (LLMs) for IaC workflows. It allows these AI tools to perform operations like workspace management, variable manipulation, and run management within Terraform environments. The server supports both Stdio and StreamableHTTP transports, offering flexibility in deployment and interaction.
By connecting AI clients to Terraform, the MCP Server enhances productivity and consistency in IaC practices, allowing for dynamic generation of outputs and recommendations. It is crucial to use this server with trusted MCP clients and LLMs due to its potential to expose Terraform data.
Reviews
Be the first to review Terraform MCP Server
Your take helps the next buyer. Verified LinkedIn reviewers get a badge.
Write a reviewBest Terraform MCP Server Alternatives
Top alternatives based on features, pricing, and user needs.
Exa MCP ServerFreemium
Powering AI agents with fast, high-quality web search and structured data extraction.
Redis MCP ServerFree
MCP server for Redis, inspect keys, manage caches, and monitor performance
Supabase MCPFreemium
Connect AI tools to your Supabase projects for natural language interaction.
Docker MCP ServerFree
Standardize AI application connections to external data sources and tools with secure gateways.
GitHub MCP ServerFree
Official MCP server for GitHub, manage repos, PRs, issues, and code search from your AI assistant
Playwright MCPFree
Browser automation MCP server, navigate, click, fill forms, screenshot, and run E2E tests
Explore More
Terraform MCP Server FAQ
What specific Terraform operations can an AI assistant perform through the MCP Server?
Through the MCP Server, an AI assistant can perform a range of Terraform operations including creating, updating, and deleting workspaces, managing workspace variables and tags, and initiating or managing Terraform runs within HCP Terraform or Terraform Enterprise.
How does the MCP Server ensure secure communication when using the StreamableHTTP transport?
When utilizing the StreamableHTTP transport, the MCP Server enhances security by allowing configuration of the
MCP_ALLOWED_ORIGINS environment variable. This restricts access to trusted origins, mitigating risks like DNS rebinding attacks and cross-origin vulnerabilities. Additionally, it supports TLS certificate and key files for secure, non-localhost deployments.What are the implications of the 'Security Note' regarding untrusted MCP clients or LLMs?
The security note highlights that the MCP Server may expose sensitive Terraform data to the connected MCP client and LLM, depending on the query. Therefore, it is critical to only use the MCP Server with trusted MCP clients and LLMs to prevent unauthorized access or misuse of your Infrastructure as Code information.
Can the Terraform MCP Server be used with any AI assistant that supports the Model Context Protocol?
Yes, the Terraform MCP Server is designed to integrate with any AI assistant that supports the Model Context Protocol (MCP). Users are required to install an AI assistant that adheres to this protocol to leverage the server's capabilities for advanced automation and interaction with Terraform.
What is the primary difference between the 'stdio' and 'streamable-http' transport modes?
The 'stdio' transport mode operates via standard input/output, typically for local or direct process communication. The 'streamable-http' mode, conversely, enables communication over HTTP, allowing the MCP Server to function as a web service with configurable host, port, and endpoint, and supporting features like CORS and TLS for network-based interactions.
Source: github.com