tfmcp is a command-line tool that helps you interact with Terraform via the Model Context Protocol (MCP). It allows LLMs to manage and operate your
Most cloud and infrastructure work still happens through a UI a human drives. Tfmcp MCP server moves it into the conversation instead. tfmcp is a command-line tool that helps you interact with Terraform via the Model Context Protocol (MCP). It allows LLMs to manage and operate your Terraform environments, including:.
The server publishes 3 tools. What each one is for:
Registry — The Registry tool exposed by this serverCompleted — The Completed tool exposed by this serverPlanned — The Planned tool exposed by this serverConfiguration is passed through the environment: TERRAFORM_DIR, TFMCP_ALLOW_DANGEROUS_OPS, TFMCP_ALLOW_AUTO_APPROVE, TFMCP_MAX_RESOURCES, TFMCP_AUDIT_ENABLED, TFMCP_AUDIT_LOG_SENSITIVE, TRANSPORT_HOST. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
PATH - Claude Desktop (for AI assistant integration) - Docker (optional, for containerized deployment)Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Tfmcp's toolset — Registry, Completed, Planned — is a fair guide to whether it matches your workflow. It is maintained by nwiizo; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Registry | The Registry tool exposed by this server. |
| Completed | The Completed tool exposed by this server. |
| Planned | The Planned tool exposed by this server. |
PATH - Claude Desktop (for AI assistant integration) - Docker (optional, for containerized deployment)| Variable | Description | Required |
|---|---|---|
| TERRAFORM_DIR | Filesystem location the server is allowed to use. | Optional |
| TFMCP_ALLOW_DANGEROUS_OPS | Configuration value read at startup. | Optional |
| TFMCP_ALLOW_AUTO_APPROVE | Configuration value read at startup. | Optional |
| TFMCP_MAX_RESOURCES | Configuration value read at startup. | Optional |
| TFMCP_AUDIT_ENABLED | Configuration value read at startup. | Optional |
| TFMCP_AUDIT_LOG_SENSITIVE | Configuration value read at startup. | Optional |
| TRANSPORT_HOST | Endpoint or connection string the server talks to. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.