Terraform MCP Server for Windsurf: Setup & Config

What you can do with Terraform in Windsurf

Choose it for Terraform Registry research and platform workspace operations through one MCP integration.

• Access private registry information for an existing organization.
• Expose selected Terraform capabilities to a shared HTTP MCP client.

Before you start: Terraform in Windsurf

• Docker installed and running
• An MCP-compatible assistant

This command is the README's local Claude Code Docker launch. HCP Terraform or Enterprise access additionally uses TFE_ADDRESS and TFE_TOKEN, which must be forwarded into the container as shown in the README's client-specific examples. Public Registry use and platform access are distinct configurations.

Terraform Windsurf configuration

1. Choose Windsurf configuration scope

   For Terraform MCP Server, open macOS/Linux: ~/.codeium/windsurf/mcp_config.json Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json. Merge into mcpServers; remote endpoints use serverUrl.

2. Add Terraform MCP Server to Windsurf

   Use the terraform-mcp-server entry below in mcpServers. Keep Terraform MCP Server's documented stdio connection fields and your other Windsurf entries.

3. Check Terraform MCP Server in Windsurf

   Terraform MCP Server: Refresh MCP in Windsurf settings and inspect Cascade’s tools.

{
  "mcpServers": {
    "terraform-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "hashicorp/terraform-mcp-server"
      ],
      "env": {}
    }
  }
}

Terraform tools available to Windsurf

Terraform's stored tool list documents 2 tools; compare it with Windsurf's connected tool list, because the stored list is not a live check.

search_providers

After refreshing Terraform in Windsurf settings, check Cascade's tool list for search_providers.

get_provider_details

After refreshing Terraform in Windsurf settings, check Cascade's tool list for get_provider_details.

Retrieve provider details; named in the README's tool-filtering example.

Terraform: full stored tool descriptions

Troubleshooting Terraform in Windsurf

• Check docker and a running Docker engine on the machine running Windsurf's MCP integration for Terraform MCP Server; refresh MCP and inspect Cascade's tools.
• Terraform MCP Server uses stdio here: Windsurf must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Connected clients and models may receive sensitive Terraform data.
• Known limitation: Write-capable platform operations need deliberate permission and tool configuration.
• Known limitation: The complete tool catalog is linked externally rather than included in the supplied README.
• General Windsurf troubleshooting lives in the /clients/windsurf guide.

Frequently asked questions