⚠️ This project includes production-ready security features but is still under active development. While the security system provides robust protection, please review all operations carefully in production environments. ⚠️
🌍 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. ⚡️
स्टार
372
टूल
—
अपटाइम
—
tfmcp runs local Terraform workflows through the Model Context Protocol (MCP).
It helps AI assistants inspect a project, prepare execution, review a saved plan,
apply that same plan, and check the result. Registry and HCP/TFE tools support
these local workflows.
🎮 Demo
See tfmcp in action with Claude Desktop:
Reading Terraform configuration files
Analyzing Terraform plan outputs
Applying Terraform configurations
Managing Terraform state
Creating and modifying Terraform configurations
🎉 Current Release
tfmcp v0.2.4 is the current release:
cargo install tfmcp --version 0.2.4
What's new in v0.2.4
Reviewed destroy plans with the same saved-plan and permission checks as apply
Saved-plan listing and disposal to reclaim the 64-plan capacity
Retained apply results, failed/unknown outcomes, and recovery guidance
Sensitive output redaction for both full and named output queries
RMCP 3.5.0, updated dependencies and images, with the Rust 1.88 MSRV retained
Features
Area
Capabilities
Local Terraform
Validate, format, plan/apply workflows, import guidance, outputs, providers, dependency graphs, refresh-only flows, and guarded state operations
Repository intelligence
Entrypoint/project detection, configuration analysis, quality checks, security checks, module health, plan review, and drift/state-safety inspection
Registry
Public/private provider, module, and policy lookup with HashiCorp-compatible aliases
# Clone the repository
git clone https://github.com/nwiizo/tfmcp
cd tfmcp
# Build and install
cargo install --path .
From Crates.io
cargo install tfmcp
Using Docker
# Clone the repository
git clone https://github.com/nwiizo/tfmcp
cd tfmcp
# Build the Docker image
docker build -t tfmcp .
# Run the container
docker run -it tfmcp
Requirements
Rust 1.88.0+ (Rust Edition 2024)
Terraform CLI 1.15.8 installed and available in PATH
An MCP-compatible AI client (for example, Claude Desktop or Codex)
Docker (optional, for containerized deployment)
Usage
$ tfmcp --help
✨ A CLI tool to manage Terraform configurations and operate Terraform through the Model Context Protocol (MCP).
Usage: tfmcp [OPTIONS] [COMMAND]
Commands:
mcp Launch tfmcp as an MCP server
analyze Analyze Terraform configurations
help Print this message or the help of the given subcommand(s)
Options:
-c, --config <PATH> Path to the configuration file
-d, --dir <PATH> Terraform project directory
-V, --version Print version
-h, --help Print help
Using Docker
When using Docker, you can run tfmcp commands like this:
# Run as MCP server (default)
docker run -it tfmcp
# Run with specific command and options
docker run -it tfmcp analyze --dir /app/example
# Mount your Terraform project directory
docker run -it -v /path/to/your/terraform:/app/terraform tfmcp --dir /app/terraform
# Set environment variables
docker run -it -e TFMCP_LOG_LEVEL=debug tfmcp
Integrating with Claude Desktop
To use tfmcp with Claude Desktop:
If you haven't already, install tfmcp:
cargo install tfmcp
Alternatively, you can use Docker:
docker build -t tfmcp .
Find the path to your installed tfmcp executable:
which tfmcp
Add the following configuration to ~/Library/Application\ Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"tfmcp": {
"command": "/path/to/your/tfmcp", // Replace with the actual path from step 2
"args": ["mcp"],
"env": {
"HOME": "/Users/yourusername", // Replace with your username
"PATH": "/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin",
"TERRAFORM_DIR": "/path/to/your/terraform/project" // Optional: specify your Terraform project
}
}
}
}
If you're using Docker with Claude Desktop, you can set up the configuration like this:
tfmcp will automatically create a sample Terraform project in ~/terraform if one doesn't exist, ensuring Claude can start working with Terraform right away. The sample project is based on the examples included in the example/demo directory of this repository.
Local plan/apply workflow
Start with tfmcp --dir /path/to/project mcp --toolsets terraform.
The default toolset supports preparation and plan review; the terraform
toolset also exposes initialization and gated local writes.
Call prepare_terraform_change to inspect the selected directory, Terraform
version, workspace, backend, configuration validity, and state readability.
ready means the inspected prerequisites passed; input variables and provider
credentials are checked by the actual plan. Initialize with init_terraform
when required, then repeat preparation.
Call get_terraform_plan with {} or, for example,
{"var_files":["environment.tfvars"]}. The result includes a plan_id,
target, created_at, has_changes, and a redacted Terraform JSON plan string.
Use replace for resource replacement addresses or refresh_only:true to
preview drift without modifying state.
Pass the returned plan_id to analyze_plan, review_terraform_plan, and
summarize_plan_for_pr. These calls reuse the saved result. Omitting the ID
creates a new plan. A review decision is advisory and does not authorize apply.
After reviewing and approving the change, call apply_terraform with
{"plan_id":"<returned ID>","auto_approve":true}. Both
TFMCP_ALLOW_DANGEROUS_OPS=true and TFMCP_ALLOW_AUTO_APPROVE=true must already
be configured on the server. The saved plan determines the applied changes,
including when configuration files have subsequently been edited.
Check success, status, exit_code, diagnostics, state_verified, and
recovery.next_steps in the apply result. Retrieve the plan's final status and
retained apply_result with
get_terraform_plan({"plan_id":"<returned ID>"}). After failure or timeout,
inspect state and create a new plan; the attempted ID cannot be applied again.
Migration from v0.2.2:apply_terraform requires plan_id; calls that only
provide auto_approve now return an explanatory error. Approval happens in the
client before the call, because Terraform receives no interactive input.
For a reviewed teardown, create a plan with get_terraform_plan({"destroy":true}),
review its plan_id, then call destroy_terraform with that ID and
auto_approve:true. The server must also have TFMCP_DELETE_ENABLED=true, in
addition to both apply permissions. Passing a destroy plan to apply_terraform
enforces the same permissions. destroy cannot be combined with refresh_only
or replace. Migration from v0.2.3:destroy_terraform now requires a saved
destroy plan; it no longer creates an unreviewed plan or waits for a prompt.
Use list_terraform_plans to find retained IDs and their targets and statuses.
Use discard_terraform_plan({"plan_id":"<ID>"}) to delete an unneeded plan's
temporary files and free capacity. Discard does not change infrastructure,
cancel an operation, or roll back an apply; inspect failed or unknown outcomes
before removing their records. These tools are available in the default and
Terraform toolsets.
Saved plans use private temporary directories and are bound to the project,
workspace, initialized backend metadata, Terraform version, and provider
lockfile. Plan IDs remain valid only for the current server process, with a
maximum of 64 retained plans. Normal server shutdown removes the temporary
files. failed means Terraform returned a nonzero exit code and may have applied
some changes. outcome_unknown means no definitive exit result was obtained,
including timeout or cancellation. Both prevent reapplying the same plan and
include recovery guidance: confirm operations have stopped, inspect the recorded
target and actual resources, resolve the cause, then generate and review a new
plan. No rollback or automatic retry is performed. apply_result is null when a
request was cancelled before a result could be retained. State verification checks
resource addresses, not all attribute values or output values.
Status retrieval waits for an ongoing operation
to finish; live progress and restart recovery are not provided in this release.
MCP Tools
tfmcp provides the following MCP tools for AI assistants:
Core Terraform Operations
Tool
Description
init_terraform
Initialize Terraform working directory
get_terraform_plan
Generate a saved plan, or retrieve its redacted result and status by plan ID
list_terraform_plans
List saved plan IDs, targets, statuses, and destroy flags
discard_terraform_plan
Remove an unneeded saved plan and free retention capacity
analyze_plan
NEW Analyze plan with risk scoring and recommendations
apply_terraform
Apply the reviewed saved plan ID and verify state resource addresses
destroy_terraform
Apply a reviewed saved destroy plan with explicit deletion permissions
validate_terraform
Validate configuration syntax
validate_terraform_detailed
Detailed validation with guidelines
get_terraform_state
Show current state
analyze_state
NEW Analyze state with drift detection
review_terraform_plan
Review plan risk, blockers, destructive changes, and recommendations
summarize_plan_for_pr
Generate markdown plan summary for PR comments
run_terraform_quality_checks
Run CI-friendly validation, module health, guideline, and lockfile checks
inspect_state_safety
Inspect state readability, drift risk, lockfile status, and blockers
detect_drift_candidates
Detect drift candidates from readable state without modifying infrastructure
prepare_terraform_change
Generate blockers, warnings, and a recommended change sequence
list_terraform_resources
List all managed resources
set_terraform_directory
Change active project directory
Workspace & State (v0.1.9)
Tool
Description
terraform_workspace
NEW Manage workspaces (list, show, new, select, delete)
terraform_import
NEW Import existing resources
terraform_taint
NEW Taint/untaint resources
terraform_refresh
NEW Refresh state
Code & Output (v0.1.9)
Tool
Description
terraform_fmt
NEW Format code
terraform_graph
NEW Generate dependency graph
terraform_output
Get output values with sensitive values redacted, including named queries
terraform_providers
NEW Get provider info with lock file
check_provider_lockfile
Check .terraform.lock.hcl for reproducible provider selections
Analysis & Security
Tool
Description
analyze_terraform
Analyze configuration
inspect_terraform_project
Inspect local Terraform directories, modules, and likely entrypoints
detect_terraform_entrypoints
Detect likely root module entrypoints
analyze_module_health
Module health with cohesion/coupling metrics
get_resource_dependency_graph
Resource dependencies visualization
suggest_module_refactoring
Refactoring suggestions
get_security_status
Security scan with secret detection
Registry
Tool
Description
search_providers
Search providers (HashiCorp-compatible alias)
search_terraform_providers
Search providers
get_provider_details
Provider details (HashiCorp-compatible alias)
get_provider_info
Provider details
get_provider_docs
Provider documentation
get_provider_capabilities
Provider resources, data sources, functions, and guides
search_modules
Search modules (HashiCorp-compatible alias)
search_terraform_modules
Search modules
get_module_details
Module details
get_latest_module_version
Latest module version
get_latest_provider_version
Latest provider version
search_policies
Search Sentinel/OPA policy libraries
get_policy_details
Policy library details
HCP Terraform / Terraform Enterprise (Read-only)
Tool
Description
get_token_permissions
Inspect configured token account details without exposing the token
Claude can't connect to the server: Make sure the path to the tfmcp executable is correct in your configuration
Terraform project issues: tfmcp automatically creates a sample Terraform project if none is found
Method not found errors: tfmcp advertises and implements tools/list, resources/list, resources/templates/list, and resources/read
Docker issues: If using Docker, ensure your container has proper volume mounts and permissions
Environment Variables
Core Configuration
TERRAFORM_DIR: Set this to specify a custom Terraform project directory. If not set, tfmcp will use the directory provided by command line arguments, configuration files, or fall back to ~/terraform. You can also change the project directory at runtime using the set_terraform_directory tool.
TFMCP_LOG_LEVEL: Set to debug, info, warn, or error to control logging verbosity.
TFMCP_DEMO_MODE: Set to true to enable demo mode with additional safety features.
TFMCP_COMMAND_TIMEOUT_SECONDS: Positive timeout in seconds for init, plan, saved-plan apply, validation, and execution preparation (default: 900). Timed-out writes may have partially completed; inspect state before retrying.
Security Configuration
ENABLE_TF_OPERATIONS: Set to true to enable gated HCP Terraform / Terraform Enterprise write tools (default: false)
TFMCP_ALLOW_DANGEROUS_OPS: Set to true to enable apply/destroy operations (default: false)
TFMCP_DELETE_ENABLED: Set to true to apply saved destroy plans; both apply permissions are also required (default: false)
TFMCP_ALLOW_AUTO_APPROVE: Set to true to enable auto-approve for dangerous operations (default: false)
TFMCP_MAX_RESOURCES: Set maximum number of resources that can be managed (default: 50)
TFMCP_AUDIT_ENABLED: Set to false to disable audit logging (default: true)
TFMCP_AUDIT_LOG_FILE: Custom path for audit log file (default: ~/.tfmcp/audit.log)
TFMCP_AUDIT_LOG_SENSITIVE: Set to true to include sensitive information in audit logs (default: false)
HCP Terraform / Terraform Enterprise
TFE_ADDRESS: HCP Terraform or Terraform Enterprise base URL (default: https://app.terraform.io)
TFE_TOKEN: API token for HCP Terraform / Terraform Enterprise tools
TFE_SKIP_TLS_VERIFY: Set to true only for trusted private TFE installations with custom TLS
TFE_MAX_RESPONSE_BYTES: Maximum HCP/TFE response bytes returned to MCP clients before truncation (default: 65536)
HCP/TFE write tools are disabled by default and fail closed unless
ENABLE_TF_OPERATIONS=true is set. The default toolset keeps write tools
hidden; use --toolsets operations or --toolsets all to expose them.
MCP Transport
TRANSPORT_MODE: MCP transport mode. Use stdio (default) for local desktop clients or streamable-http for remote/CI clients.
TRANSPORT_HOST: HTTP bind host for streamable HTTP mode (default: 127.0.0.1).
TRANSPORT_PORT: HTTP bind port for streamable HTTP mode (default: 8080).
MCP_SESSION_MODE: stateful for normal MCP clients or stateless for CI-style JSON responses (default: stateful). Applies only to clients negotiating a protocol version before 2026-07-28; that spec removed sessions, so those requests are always served statelessly.
MCP_HEARTBEAT_INTERVAL: Streamable HTTP SSE keep-alive interval in seconds. Set to 0 to disable (default: 15).
MCP_CORS_MODE: Response CORS policy: strict, development, or disabled (default: strict). MCP request Origin validation remains enabled in all modes.
MCP_ALLOWED_ORIGINS: Comma-separated allowed browser origins. Loopback origins are used by default.
MCP_ALLOWED_HOSTS: Comma-separated HTTP Host / authority values accepted by Streamable HTTP. When unset, rmcp's loopback-only defaults apply.
MCP_ORGANIZATION_ALLOWLIST: Comma-separated HCP/TFE organization names that remote requests may access.
MCP_RATE_LIMIT_GLOBAL: Maximum HTTP requests per minute across the server (0 or unset disables).
MCP_RATE_LIMIT_SESSION: Maximum HTTP requests per minute per Mcp-Session-Id (0 or unset disables). Clients negotiating 2026-07-28 send no session header, so only MCP_RATE_LIMIT_GLOBAL bounds them.
MCP_TLS_CERT_FILE: PEM certificate file for HTTPS Streamable HTTP.
MCP_TLS_KEY_FILE: PEM private key file for HTTPS Streamable HTTP.
HCP/TFE credentials and addresses are server configuration. tfmcp intentionally
does not accept request-scoped TFE_TOKEN, Authorization, or TFE_ADDRESS
overrides for downstream passthrough. When an organization allowlist is active,
account-wide and ID-only HCP/TFE requests fail closed because their owning
organization cannot be verified locally.
The MCP endpoint is http://127.0.0.1:8080/mcp, the health endpoint is
http://127.0.0.1:8080/health, and the metrics endpoint is
http://127.0.0.1:8080/metrics.
Security Considerations
tfmcp includes comprehensive security features designed for production use:
🔒 Built-in Security Features
Access Controls: Automatic blocking of production/sensitive file patterns
Operation Restrictions: Dangerous operations (apply/destroy) disabled by default
Resource Limits: Configurable maximum resource count protection
Audit Logging: Complete operation tracking with timestamps and user identification
Directory Validation: Security policy enforcement for project directories
🛡️ Security Best Practices
Default Safety: Apply/destroy operations are disabled by default - explicitly enable only when needed
Review Plans: Always review Terraform plans before applying, especially AI-generated ones
IAM Boundaries: Use appropriate IAM permissions and role boundaries in cloud environments
Audit Monitoring: Regularly review audit logs at ~/.tfmcp/audit.log
File Patterns: Built-in protection against accessing prod*, production*, and secret* patterns
Docker Security: When using containers, carefully consider volume mounts and exposed data
Commit your changes (git commit -m 'Add some amazing feature')
Push to the branch (git push origin feature/amazing-feature)
Open a Pull Request
The pre-commit hook always checks staged whitespace and conditionally runs
cargo fmt, actionlint, Registry metadata validation, module coupling, and
duplicate-code checks for affected files. The optional architecture tools are
still mandatory in Release.sh; install cargo-coupling and similarity-rs
to run the same fast feedback while developing.
Release Process
Releases are done manually after the local release gate passes:
Confirm Cargo.toml, Cargo.lock, server.json, Dockerfile, README, and CHANGELOG.md use the target version.
Run the local release gate: ./Release.sh v0.2.4.
Review CHANGELOG.md and the generated package.
Commit and push main, then confirm CI passed for that exact commit.
From the clean commit, publish with ./Release.sh v0.2.4 --publish.
Roadmap
Here are some planned improvements and future features for tfmcp:
The local development requirements
compare the current implementation with Terraform documentation and the local
Terraform in Depth / Terraform at Scale source material, with prioritized jobs
and acceptance criteria for future work.
For a hands-on check with a real local Web app, see the
local application example. It verifies saved-plan
deployment, HTTP responses, actual Terraform arguments, audit records, and
teardown, and retains the report and logs.
Completed
Basic Terraform Integration
Core integration with Terraform CLI for analyzing and executing operations.
MCP Server Implementation
Initial implementation of the Model Context Protocol server for AI assistants.
Automatic Project Creation
Added functionality to automatically create sample Terraform projects when needed.
Claude Desktop Integration
Support for seamless integration with Claude Desktop.
Core MCP Methods
Implementation of essential MCP methods including tools/list, resources/list, resources/templates/list, and resources/read.
Error Handling Improvements
Better error handling and recovery mechanisms for robust operation.
Dynamic Project Directory Switching
Added ability to change the active Terraform project directory without restarting the service.
Crates.io Publication
Published the package to Crates.io for easy installation via Cargo.
Docker Support
Added containerization support for easier deployment and cross-platform compatibility.
Security Enhancements
Comprehensive security system with configurable policies, audit logging, access controls, and production-ready safety features.
Module Health Analysis (v0.1.6)
Whitebox approach to IaC with cohesion/coupling metrics, health scoring, and refactoring suggestions.
Resource Dependency Graph (v0.1.6)
Visualization of resource relationships including explicit and implicit dependencies.
Module Registry Integration (v0.1.6)
Search and explore Terraform modules from the registry.
Comprehensive Testing Framework
85+ tests including integration tests with real Terraform configurations.
RMCP SDK Migration (v0.1.8)
Migrated to official RMCP SDK with proper tool annotations for better MCP compliance.
Future Architect Guidelines (v0.1.8)
Terraform coding standards compliance checks with secret detection and variable quality validation.
In Progress
Multi-Environment Support
Add support for managing multiple Terraform environments, workspaces, and modules.
Planned
Expanded MCP Protocol Support
Implement additional MCP methods and capabilities for richer integration with AI assistants.
Performance Optimization
Optimize resource usage and response times for large Terraform projects.
Cost Estimation
Integrate with cloud provider pricing APIs to provide cost estimates for Terraform plans.
Interactive TUI
Develop a terminal-based user interface for easier local usage and debugging.
Integration with Other AI Platforms
Extend beyond Claude to support other AI assistants and platforms.
Plugin System
Develop a plugin architecture to allow extensions of core functionality.
License
This project is licensed under the MIT License - see the LICENSE file for details.
T
Tfmcp
nwiizo·372 स्टार·
🌍 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
🌍 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. ⚡️
टूल
टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
सवाल
Tfmcp कैसे इंस्टॉल करें?
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Tfmcp कौन सा ट्रांसपोर्ट इस्तेमाल करता है?
Tfmcp stdio पर लोकल चलता है।
Tfmcp की पिछली जाँच कब हुई थी?
पिछली जाँच 2026-10-26 को हुई। 🌍 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. ⚡️