Extension Version
v2.39.2
Problem Statement
My company does not permit many of our developers to install an OCI compatible runtime on their development workstations (Docker, Rancher, Podman, etc.). As a result, they are unable to take advantage of the extension's MCP integration.
Expected User Experience
New option in settings for "Terraform -> MCP -> Server: Runtime" with the options "binary" or "container" (default to container to prevent a regression issue)
Additionally, MCP server options should be added to the settings based on the options in the MCP server config like toolset & tools.
Proposal
The Terraform MCP server is published as both an OCI compatible container and as native Go binaries. It would be nice if instead of requiring a container runtime, the extension could download the platform/arch specific version of the MCP binary (like it already does for the language server). v0.5.2 of the binary supports loading TFC credentials directly from the credentials file while we don't have a comparable option for the container version.
New option in settings for "Terraform -> MCP -> Server: Runtime" with the options "binary" or "container" (default to container to prevent a regression issue)
If "binary" is selected, download the latest version (or allow version selection) from https://releases.hashicorp.com/terraform-mcp-server/ based on OS & architecture and store in the extension's bin folder (alongside the terraform-ls).
Update the mcp configuration with the appropriate template based on deployment type.
References
No response
Help Wanted
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Extension Version
v2.39.2
Problem Statement
My company does not permit many of our developers to install an OCI compatible runtime on their development workstations (Docker, Rancher, Podman, etc.). As a result, they are unable to take advantage of the extension's MCP integration.
Expected User Experience
New option in settings for "Terraform -> MCP -> Server: Runtime" with the options "binary" or "container" (default to container to prevent a regression issue)
Additionally, MCP server options should be added to the settings based on the options in the MCP server config like toolset & tools.
Proposal
The Terraform MCP server is published as both an OCI compatible container and as native Go binaries. It would be nice if instead of requiring a container runtime, the extension could download the platform/arch specific version of the MCP binary (like it already does for the language server). v0.5.2 of the binary supports loading TFC credentials directly from the credentials file while we don't have a comparable option for the container version.
New option in settings for "Terraform -> MCP -> Server: Runtime" with the options "binary" or "container" (default to container to prevent a regression issue)
If "binary" is selected, download the latest version (or allow version selection) from https://releases.hashicorp.com/terraform-mcp-server/ based on OS & architecture and store in the extension's bin folder (alongside the terraform-ls).
Update the mcp configuration with the appropriate template based on deployment type.
References
No response
Help Wanted
Community Note