MCP服务器Helm Charts

用于在Kubernetes上部署和管理Model Context Protocol (MCP)服务器的生产级Helm Charts,支持stdio与原生HTTP模式,并提供安全加固、健康检查等标准化约定。

  • by HMetcalfeW
  • Shell
  • 本地部署
  • 3 星标
  • 更新于
在 GitHub 查看 HMetcalfeW/mcp-helm-charts

使用说明

MCP Helm Charts

Production-ready Helm charts for deploying Model Context Protocol (MCP) servers on Kubernetes.

Available Charts

Chart Description Mode
mcp-server Generic chart for any MCP server Supergateway (stdio) or Native (HTTP)
atlassian Jira, Confluence, and Teamwork Graph Native

See ROADMAP.md for upcoming charts.

Quick Start

helm repo add mcp-helm-charts https://hmetcalfew.github.io/mcp-helm-charts
helm repo update

Deploy a stdio MCP server (supergateway mode)

Wraps any stdio-based MCP server and exposes it over Streamable HTTP:

helm install aws-docs mcp-helm-charts/mcp-server \
  --set command="uvx awslabs.aws-documentation-mcp-server@latest"

Deploy a native HTTP MCP server

For servers that speak HTTP directly (FastMCP, Go SDK, etc.):

helm install my-server mcp-helm-charts/mcp-server \
  --set mode=native \
  --set image.repository=my-org/my-mcp-server \
  --set image.tag=latest \
  --set nativeCommand[0]=mcp \
  --set nativeArgs[0]=run \
  --set nativeArgs[1]=--port \
  --set nativeArgs[2]=8000

A native server that serves more than one MCP endpoint from one process, one per port, adds the extra ports with extraPorts. Each entry becomes a named container port and a Service port targeting it, so a gateway can register each endpoint as its own upstream. Probes stay on server.port.

extraPorts:
  - name: second
    containerPort: 8001

Deploy Atlassian MCP

helm install atlassian mcp-helm-charts/atlassian \
  --set secrets.atlassianApiKey=<your-key>

Chart Conventions

All charts in this repo follow a consistent structure:

  • Security first — non-root, drop all capabilities, read-only root filesystem
  • Read-only by default — write operations disabled unless explicitly enabled
  • Health probes — HTTP health checks on configurable endpoints
  • Secrets via k8s Secret — credentials are never baked into ConfigMaps
  • Configurable transport — Streamable HTTP or SSE where supported
  • Minimal footprint — single replica, ClusterIP service, no ingress by default

Contributing

See CONTRIBUTING.md for chart conventions, testing requirements, and how to add a new chart.

Check the ROADMAP.md for charts we're looking for.

Development

# Lint all charts
make lint

# Render templates for a chart
make template CHART=mcp-server

# Run integration tests (requires kind)
make kind-test CHART=atlassian

License

Apache 2.0