Streamable HTTP Server for GHES (oauth)

[SamMorrowDrums]

We'd love to hear from people who use the server with GHES, especially folks who have rolled their own fork and use the server on their own infra.

• What did you learn?
• Any friction (maintaining a fork counts here too)?
• Any GHES specific needs you would like us to consider?
• Anything not working for you?

---

📊 Interest Already Expressed in GHES/GHES-Specific Features

The community has filed several GHES-related issues showing significant demand:

Open Issues

• Support subdomain isolation for GHES hosts #500 - Support subdomain isolation for GHES hosts
• Add Streamable HTTP Transport Support for Multi-User Mode #471 - Add Streamable HTTP Transport Support for Multi-User Mode
• Network timeouts when interacting with GitHub Enterprise Server #299 - Network timeouts when interacting with GHES
• Better support custom TLS situations when using a Docker #157 - Better support custom TLS situations when using Docker

Notable Closed Issues

• support GitHub App installation‑token authentication (server‑to‑server) for MCP #311 - GitHub App installation-token authentication (30 👍)
• get_file_contents is not working properly (Path did not point to a file or directory, but resolved git ref) #864 - get_file_contents path resolution (14 👍)
• Multiple account support #623 - Multiple account support (4 👍)
• Custom GHES host names are not supported #662 - Custom GHES host names (fixed)
• Support the ability to have multiple instances running at the same time #206 - Support multiple instances (GHES + GHEC)

[bbartels]

We are looking into a centralised MCP to sit in front of GHES, is there any plans to still release support or merge the existing PR's to allow for multi tenancy? @SamMorrowDrums

For us it would be useful to have both PAT and OAUTH auth modes (PAT being higher priority for us)

[SamMorrowDrums]

We are actively working on it.