Interest check: GHES Manage API toolset?

[djdefi]

Summary

Is there interest in a toolset that wraps the GHES Manage API (/manage/v1/) so MCP clients pointed at a GHES instance can interact with the appliance management plane in addition to the application API?

Filing this as a high-level interest check before any design work — happy to discuss whether this is a direction maintainers want to take, and what shape would fit the project.

Context

The server already supports targeting GHES via --gh-host / GITHUB_HOST (README "GitHub Enterprise Server and Enterprise Cloud with data residency (ghe.com)" section). Existing toolsets under pkg/github/ wrap the application REST API. None currently cover the appliance management plane that /manage/v1/ exposes (config, maintenance, replication, upgrade, license).

A quick scan of issues, PRs, and discussions for manage, ghes, appliance, /manage/v1, etc. didn't surface a prior proposal in this area — apologies if I missed one.

Open questions for maintainers

• Is appliance-management surface area in scope for this project, or intentionally out of scope?
• If in scope, what shape would you prefer — a separate toolset, a separate binary, or something else?
• Any concerns I should think through before sketching anything more concrete?

Happy to follow up with a more detailed proposal if there's interest, or close this if it's the wrong venue.

[SamMorrowDrums]

Hi @djdefi thanks for asking about this. So my gut check is that it's potentially dangerously powerful and I'd be a bit concerned about end users running with dangerously skip permissions set and harming their instance and this coming back on GitHub MCP Server as an enabler.

We don't have admin features for GitHub dotcom orgs/enterprises either.

So I'm happy to collect input and ideas here, but due to sensitivity of the possible tools, I'd expect it to be a whole conversation internally and not something we could just ship straight from a PR.