Document Kubernetes installation with the HelmForge Helm chart

Open Beginner friendly
#2,803 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
helm, kubernetes
Domain
devops, documentation

Research direction

Locate and read the existing installation documentation, then review the linked HelmForge chart documentation and its basic Helm commands. Done means adding a concise Kubernetes/Helm installation section that links to the community-maintained chart and clearly states the support boundary.

Written by the indexing model from the issue text.

Description

Hi maintainers,

I was looking through the project documentation and did not find a Kubernetes installation section using Helm. If I missed an existing official page, please point me to it and feel free to close this.

HelmForge now publishes a production-oriented Helm chart for GitHub MCP Server:

The basic installation flow is intentionally simple:

helm repo add helmforge https://repo.helmforge.dev
helm repo update
helm install github-mcp-server helmforge/github-mcp-server --namespace github-mcp-server --create-namespace

The chart is meant to provide a Kubernetes-native path for users who want to run GitHub MCP Server on their own clusters, with explicit values, pinned upstream images, and common production surfaces such as persistence, service exposure, probes, security contexts, and optional integrations where applicable.

Would you be open to adding a short Kubernetes / Helm installation section to the documentation that references this chart as a community-maintained deployment option?

If that direction makes sense, I would be happy to prepare a documentation PR with a concise install section, links to the HelmForge chart documentation, and any wording you prefer around support boundaries.

Dominant language
Go
Stars
33.1k
Forks
5k
Avg merge
2d 15h
Merged PRs (30d)
27

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/github-mcp-server

All issues in github/github-mcp-server

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.