官方说明10 个来源MCP 服务8 天前
hashicorp/terraform-mcp-server
🎖️ 🏎️ ☁️ - Terraform ecosystem integration: provider discovery, module analysis and Terraform Registry API…
在 GitHub 查看 ↗直链 · 无中转页
官方说明🎖️ 🏎️ ☁️ - Terraform ecosystem integration: provider discovery, module analysis and Terraform Registry API access for infrastructure-as-code workflows.
配置模板（请按你的客户端调整）
claude mcp add terraform-mcp-server -- npx -y terraform-mcp-server
这是根据仓库名生成的可粘贴骨架，命令行参数与包名请以该项目 README 为准。
- ★ 数取值
- 1,550 ★ · hashicorp/terraform-mcp-server · 取自该仓库的 GitHub 页面 · （2026-10-16 20:00:20 核对）
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-10-09 · 最近见到 2026-10-16 · 共见到 32 次 · 被 10 个来源列出
- 评分构成
- 综合分 1,003 · 1,550 ★ · 10 个来源 · mcp
常见问题（答案都来自我们的记录）
怎么安装？
我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。
它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
hashicorp/terraform-mcp-server；我们收录于 2026-10-09；最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。第三方质量标记
Terraform MCP Server
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
The Terraform MCP Server is a Model Context Protocol (MCP)
server that integrates seamlessly with Terraform Registry and HCP Terraform APIs, enabling advanced
automation and interaction capabilities for Infrastructure as Code (IaC) development.
Table of Contents
Get started
Client integrations
Build and run
Features
Prerequisites
Command Line Options
Instructions
Installation
Visual Studio Code
Cursor
Claude Desktop, Amazon Q Developer, and Kiro CLI
Claude Code
Codex CLI
Gemini extensions
Bob IDE and Shell
Install from source
Building the Docker Image locally
Transport Support
Stdio Transport
StreamableHTTP Transport
Server capabilities
Deployment and security
Help and contributing
Available Tools
Available Resources
Available Metrics
Tool Filtering
Session Modes
Token Passthrough for Centralized Deployments
Client IP Forwarding
Trust model
Trusted hops
Limitations
Migrating from earlier versions
Supported Headers
Security Considerations
Centralized Deployment Example
Troubleshooting
Corporate Proxy and TLS Inspection
Development
Contributing
License
Security
Support
Features
- **Dual Transport Support**: Both Stdio and StreamableHTTP transports with configurable endpoints
- **Terraform Registry Integration**: Direct integration with public Terraform Registry APIs for providers, modules, and policies
- **HCP Terraform & Terraform Enterprise Support**: Full workspace management, organization/project listing, and private registry access
- **Workspace Operations**: Create, update, delete workspaces with support for variables, tags, and run management
- **OTel metrics for monitoring tool usage**: Integration with open telemetry meters to track tool-call volume, latency and failures in Streamable HTTP mode. Also exposes default http server metrics when this feature is enabled
> **Security Note:** Depending on the query, the MCP server may expose certain Terraform data to the MCP client and LLM. Do not use the MCP server with untrusted MCP clients or LLMs.
> **Legal Note:** Your use of a third party MCP Client/LLM is subject solely to the terms of use for such MCP/LLM, and IBM is not responsible for the performance of such third party tools. IBM expressly disclaims any and all warranties and liability for third party MCP Clients/LLMs, and may not be able to provide support to resolve issues which are caused by the third party tools.
> **Caution:** The outputs and recommendations provided by the MCP server are generated dynamically and may vary based on the query, model, and the connected MCP client. Users should thoroughly review all outputs/recommendations to ensure they align with their organization’s security best practices, cost-efficiency goals, and compliance requirements before implementation.
Prerequisites
1. Ensure Docker is installed and running to use the server in a containerized environment.
1. Install an AI assistant that supports the Model Context Protocol (MCP).
Command Line Options
**Environment Variables:**
| Variable | Description | Default |
|----------|-------------|---------|
| TFE_ADDRESS | Sets the Terraform Enterprise/HCP Terraform address for API calls. Must include the protocol (e.g., https://app.terraform.io). In streamable-http mode this is the only way to set the address; it cannot be supplied by clients via header or query parameter. | Optional |
| TFE_TOKEN | Terraform Enterprise API token | "" (empty) |
| TF_MCP_SHARED_SECRET | Shared secret sent as the X-Tf-Mcp-Secret header on requests to HCP Terraform / TFE, used to identify requests originating from a hosted MCP deployment. Should only be used over TLS. | "" (empty) |
| TFE_SKIP_TLS_VERIFY | Skip HCP Terraform or Terraform Enterprise TLS verification | false |
| LOG_LEVEL | Logging level: trace, debug, info, warn, error, fatal, panic (overrides --log-level flag) | info |
| LOG_FORMAT | Logging format: text or json (overrides --log-format flag)| text |
| TRANSPORT_MODE | Set to streamable-http to enable HTTP transport (legacy http value still supported) | stdio |
| TRANSPORT_HOST | Host to bind the HTTP server | 127.0.0.1 |
| TRANSPORT_PORT | HTTP server port | 8080 |
| MCP_ENDPOINT | HTTP server endpoint path | /mcp |
| MCP_REDIRECT_ROOT_URL | URL to redirect requests to / to | "" |
| MCP_KEEP_ALIVE | Keep-alive interval for SSE connections (e.g., 30s, 1m). 0 to disable | 0 |
server that integrates seamlessly with Terraform Registry and HCP Terraform APIs, enabling advanced
automation and interaction capabilities for Infrastructure as Code (IaC) development.
Table of Contents
Get started
Client integrations
Build and run
Features
Prerequisites
Command Line Options
Instructions
Installation
Visual Studio Code
Cursor
Claude Desktop, Amazon Q Developer, and Kiro CLI
Claude Code
Codex CLI
Gemini extensions
Bob IDE and Shell
Install from source
Building the Docker Image locally
Transport Support
Stdio Transport
StreamableHTTP Transport
Server capabilities
Deployment and security
Help and contributing
Available Tools
Available Resources
Available Metrics
Tool Filtering
Session Modes
Token Passthrough for Centralized Deployments
Client IP Forwarding
Trust model
Trusted hops
Limitations
Migrating from earlier versions
Supported Headers
Security Considerations
Centralized Deployment Example
Troubleshooting
Corporate Proxy and TLS Inspection
Development
Contributing
License
Security
Support
Features
- **Dual Transport Support**: Both Stdio and StreamableHTTP transports with configurable endpoints
- **Terraform Registry Integration**: Direct integration with public Terraform Registry APIs for providers, modules, and policies
- **HCP Terraform & Terraform Enterprise Support**: Full workspace management, organization/project listing, and private registry access
- **Workspace Operations**: Create, update, delete workspaces with support for variables, tags, and run management
- **OTel metrics for monitoring tool usage**: Integration with open telemetry meters to track tool-call volume, latency and failures in Streamable HTTP mode. Also exposes default http server metrics when this feature is enabled
> **Security Note:** Depending on the query, the MCP server may expose certain Terraform data to the MCP client and LLM. Do not use the MCP server with untrusted MCP clients or LLMs.
> **Legal Note:** Your use of a third party MCP Client/LLM is subject solely to the terms of use for such MCP/LLM, and IBM is not responsible for the performance of such third party tools. IBM expressly disclaims any and all warranties and liability for third party MCP Clients/LLMs, and may not be able to provide support to resolve issues which are caused by the third party tools.
> **Caution:** The outputs and recommendations provided by the MCP server are generated dynamically and may vary based on the query, model, and the connected MCP client. Users should thoroughly review all outputs/recommendations to ensure they align with their organization’s security best practices, cost-efficiency goals, and compliance requirements before implementation.
Prerequisites
1. Ensure Docker is installed and running to use the server in a containerized environment.
1. Install an AI assistant that supports the Model Context Protocol (MCP).
Command Line Options
**Environment Variables:**
| Variable | Description | Default |
|----------|-------------|---------|
| TFE_ADDRESS | Sets the Terraform Enterprise/HCP Terraform address for API calls. Must include the protocol (e.g., https://app.terraform.io). In streamable-http mode this is the only way to set the address; it cannot be supplied by clients via header or query parameter. | Optional |
| TFE_TOKEN | Terraform Enterprise API token | "" (empty) |
| TF_MCP_SHARED_SECRET | Shared secret sent as the X-Tf-Mcp-Secret header on requests to HCP Terraform / TFE, used to identify requests originating from a hosted MCP deployment. Should only be used over TLS. | "" (empty) |
| TFE_SKIP_TLS_VERIFY | Skip HCP Terraform or Terraform Enterprise TLS verification | false |
| LOG_LEVEL | Logging level: trace, debug, info, warn, error, fatal, panic (overrides --log-level flag) | info |
| LOG_FORMAT | Logging format: text or json (overrides --log-format flag)| text |
| TRANSPORT_MODE | Set to streamable-http to enable HTTP transport (legacy http value still supported) | stdio |
| TRANSPORT_HOST | Host to bind the HTTP server | 127.0.0.1 |
| TRANSPORT_PORT | HTTP server port | 8080 |
| MCP_ENDPOINT | HTTP server endpoint path | /mcp |
| MCP_REDIRECT_ROOT_URL | URL to redirect requests to / to | "" |
| MCP_KEEP_ALIVE | Keep-alive interval for SSE connections (e.g., 30s, 1m). 0 to disable | 0 |
- 来源
- awesome · https://github.com/hashicorp/terraform-mcp-server
- 按领域浏览
- MCP 服务
- Traction
- 1,550 ★
- 收录于
- 昨天
更多MCP 服务
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。