Back to Home
sammcgeown icon

hashicorp-mcp-servers-helm

Verified Safe

by sammcgeown

Overview

Deploys HashiCorp Model Context Protocol (MCP) servers (Terraform and Vault) on Kubernetes, enabling AI assistants to interact with HashiCorp products via a unified ingress.

Installation

Run Command
helm repo add hashicorp-mcp https://sammcgeown.github.io/hashicorp-mcp-servers-helm/ && helm repo update && helm install hashicorp-mcp hashicorp-mcp/hashicorp-mcp -n mcp-servers --create-namespace

Environment Variables

  • TFE_ADDRESS
  • TFE_TOKEN
  • TFE_SKIP_TLS_VERIFY
  • VAULT_ADDR
  • VAULT_TOKEN
  • VAULT_SKIP_VERIFY
  • TRANSPORT_MODE
  • TRANSPORT_HOST
  • TRANSPORT_PORT
  • MCP_ENDPOINT
  • MCP_SESSION_MODE
  • MCP_ALLOWED_ORIGINS
  • MCP_CORS_MODE
  • MCP_RATE_LIMIT_GLOBAL
  • MCP_RATE_LIMIT_SESSION
  • MCP_TLS_CERT_FILE
  • MCP_TLS_KEY_FILE
  • ENABLE_TF_OPERATIONS

Security Notes

The project uses standard and generally secure Kubernetes practices, including managing secrets via Kubernetes secrets and TLS certificates via cert-manager. The source code does not contain obvious malicious patterns or unsafe code execution (`eval`). However, the project's README explicitly states it's 'provided as-is' and 'not officially maintained by HashiCorp,' which implies potential long-term security maintenance risks. Crucially, the Vault MCP documentation warns that it is a beta feature and that the MCP server may expose Vault data/secrets to untrusted MCP clients and LLMs, advising against its use with untrusted parties. This highlights inherent risks in the application's use case, which users must mitigate.

Similar Servers

Stats

Interest Score26
Security Score7
Cost ClassLow
Stars1
Forks0
Last Update2025-11-20

Tags

HelmKubernetesHashiCorpMCPTerraformVaultAIMLIngresscert-manager