terraform

This MCP server exposes a set of Terraform Registry related tools through the MCP interface. It includes core registry tools that let you fetch provider details, example usages, module metadata, and more, as well as data sources, resources, and module information from the Terraform Registry. When you enable this server (for example via Cursor or Claude Desktop), you can call tools like providerDetails, resourceUsage, moduleSearch, listDataSources, moduleDetails, and providerGuides to retrieve structured Terraform registry data. If you have a Terraform Cloud token (TFC_TOKEN) configured, you can also access Terraform Cloud tools to list organizations, workspaces, runs, and related resources such as private modules and workspace resources, enabling AI-assisted infrastructure planning across both public registry data and private Terraform Cloud resources.

Prerequisites:\n- Node.js and npm installed on your system.\n- Access to the internet to fetch the Terraform MCP server package.\n\nInstallation steps:\n1) Install dependencies and verify Node.js environment.\nbash\nnpm install\n\n2) Run the MCP server locally (uses npx with the terraform-mcp-server package).\nbash\nnpm start\n\n3) (Optional) Integrate with Cursor or Claude Desktop as described in the README:\n- Cursor: add a new MCP server with command npx -y terraform-mcp-server.\n- Claude Desktop: update claude_desktop_config.json to include the terraform-registry server entry.\njson\n{\n "mcpServers": {\n "terraform-registry": {\n "command": "npx",\n "args": ["-y", "terraform-mcp-server"]\n }\n }\n}\n

Tips and considerations:\n- The Terraform Cloud tools require a valid Terraform Cloud API token in the TFC_TOKEN environment variable to access private modules and runs.\n- You can configure several environment variables to tailor timeouts, logging, and rate limiting. Default values are provided in the README.\n- The server uses stdio MCP transport as shown in the Running the Server section, and can be started with npm start after npm install.\n- If you encounter connectivity issues with prompts (getPrompt) during usage, prefer listPrompts to discover available prompts and avoid direct getPrompt calls until the issue is resolved.