Enables AI agents to interact with the Terraform Registry API for provider, resource, and module information.
Most cloud and infrastructure work still happens through a UI a human drives. Terraform Registry MCP server moves it into the conversation instead. Enables AI agents to interact with the Terraform Registry API for provider, resource, and module information.
A Model Context Protocol (MCP) server that provides tools for interacting with the Terraform Registry API. This server enables AI agents to query provider information, resource details, and module metadata.
The server publishes 14 tools. What each one is for:
providerDetails — Gets detailed information about a Terraform providerresourceUsage — Gets example usage of a Terraform resource and related resourcesmoduleSearch — Searches for and recommends Terraform modules based on a querylistDataSources — Lists all available data sources for a provider and their basic detailsresourceArgumentDetails — Fetches comprehensive details about a resource type's argumentsmoduleDetails — Retrieves detailed metadata for a Terraform modulefunctionDetails — Gets details about a Terraform provider functionproviderGuides — Lists and views provider-specific guides and documentationpolicySearch — Searches for policy libraries in the Terraform RegistrypolicyDetails — Gets detailed information about a specific policy librarylistOrganizations — Lists all organizations the authenticated user has access toprivateModuleSearch — Searches for private modules in an organizationInstallation goes through your MCP client rather than a global install: point it at terraform-mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: LOG_LEVEL, REQUEST_TIMEOUT_MS, TFC_TOKEN, TERRAFORM_REGISTRY_URL. 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.
Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Terraform Registry's toolset — providerDetails, resourceUsage, moduleSearch and 11 more — is a fair guide to whether it matches your workflow. It is maintained by thrashr888; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Terraform Registry's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| providerDetails | Gets detailed information about a Terraform provider |
| resourceUsage | Gets example usage of a Terraform resource and related resources |
| moduleSearch | Searches for and recommends Terraform modules based on a query |
| listDataSources | Lists all available data sources for a provider and their basic details |
| resourceArgumentDetails | Fetches comprehensive details about a resource type's arguments |
| moduleDetails | Retrieves detailed metadata for a Terraform module |
| functionDetails | Gets details about a Terraform provider function |
| providerGuides | Lists and views provider-specific guides and documentation |
| policySearch | Searches for policy libraries in the Terraform Registry |
| policyDetails | Gets detailed information about a specific policy library |
| listOrganizations | Lists all organizations the authenticated user has access to |
| privateModuleSearch | Searches for private modules in an organization |
| privateModuleDetails | Gets detailed information about a private module |
| explorerQuery | Queries the Terraform Cloud Explorer API to analyze data |
{
"mcpServers": {
"terraform-registry": {
"command": "npx",
"args": ["-y", "terraform-mcp-server"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LOG_LEVEL | Configuration value read at startup. | Optional |
| REQUEST_TIMEOUT_MS | Configuration value read at startup. | Optional |
| TFC_TOKEN | Credential the server authenticates with. | Yes |
| TERRAFORM_REGISTRY_URL | Endpoint or connection string the server talks to. | Yes |
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.