I didn't downvote you, but this thing is actually back to their MPL-2 roots (for now!) and I don't see any references to github.com/hashicorp/terraform in https

I didn't downvote you, but this thing is actually back to their MPL-2 roots (for now!) and I don't see any references to github.com/hashicorp/terraform in https://github.com/hashicorp/terraform-mcp-server/blob/v0.1.0/go.mod https://github.com/hashicorp/terraform-mcp-server/blob/v0.1.... and I would guess patching https://github.com/hashicorp/terraform-mcp-server/blob/v0.1.0/pkg/hashicorp/tfregistry/utils.go#L422 https://github.com/hashicorp/terraform-mcp-server/blob/v0.1.... to accept an env-var or config flag or whatever would decouple it from their centralization The back side of that coin is that it similarly just(?) seems to be a fancy way of feeding the terraform provider docs to the LLM, which was already available via `tofu provider schema -json` without all this http business. IMHO the fields in the provider binary that don't have populated "description" fields are a bug