MCP Server Terraform

What the code does

We read the source, 21 h ago · rules 3dff92dd89df

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

        try { unlinkSync(planFile); } catch { /* best-effort cleanup */ }

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    const result = spawnSync(cmd, args, { timeout: 5000, encoding: "utf8" });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp-server-terraform -- npx -y @rajsir/mcp-server-terraform

{
  "mcpServers": {
    "mcp-server-terraform": {
      "args": [
        "-y",
        "@rajsir/mcp-server-terraform"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.mcp-server-terraform]
command = "npx"
args = ["-y", "@rajsir/mcp-server-terraform"]

{
  "mcpServers": {
    "mcp-server-terraform": {
      "args": [
        "-y",
        "@rajsir/mcp-server-terraform"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "mcp-server-terraform": {
      "args": [
        "-y",
        "@rajsir/mcp-server-terraform"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: ALLOW_ONLY_READONLY_TOOLS (Set to 'true' to expose only validate/plan/output/preflight/drift tools), ALLOW_ONLY_NON_DESTRUCTIVE_TOOLS (Set to 'true' to block apply/destroy/state-mutation tools), AUDIT_LOG_PATH (File path for JSON-lines audit logging of all tool calls (var values redacted)). The author declared them in the registry entry; get the values from the project itself.