github / github/github-mcp-server

Document Kubernetes installation with the HelmForge Helm chart

Offen Anfängerfreundlich
#2,803 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Go
Sterne
33k
Forks
5k
Ø Merge
2 T. 1 Std.
Gemergte PRs (30 T.)
52

Beschreibung

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:

- Documentation: https://helmforge.dev/docs/charts/github-mcp-server
- Chart source: https://github.com/helmforgedev/charts/tree/main/charts/github-mcp-server

The basic installation flow is intentionally simple:

~~~bash
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.

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
helm, kubernetes
Bereich
devops, documentation
Issue-Typ
Dokumentation
Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Aktivitätsstatus
Aktiv
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
74/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.