From v1.10.0, the GitHub MCP server rejects an http:// GitHub Enterprise Server host in --gh-host or GITHUB_HOST; only https (or loopback http) is accepted
Took effect · Server configuration --gh-host / GITHUB_HOST — http:// GitHub Enterprise Server hosts
Reviewed against the vendor source on Sep 24, 2026 (AI-assisted review). Key facts are re-checked against the source daily.
What changes
Before v1.10.0 an http:// GHES host was accepted and used for every derived URL, so authenticated requests could carry the token over cleartext. HTTPS is now enforced centrally; http is permitted only for loopback hosts (localhost, 127.0.0.1, ::1). A configuration that sets an http:// GHES host now fails with the error "host must use https to avoid sending credentials over cleartext".
Breaking: Calls fail after this date.
What to do
Set --gh-host / GITHUB_HOST to the https:// URL of your GHES instance (make sure it serves valid TLS) before upgrading to v1.10.0.
Strings to search for
GITHUB_HOST--gh-host
Not affected (matches inside these are ignored): GITHUB_HOST=https://, GITHUB_HOST="https://, GITHUB_HOST: https://, GITHUB_HOST: "https://, "GITHUB_HOST": "https://, "GITHUB_HOST":"https://, --gh-host=https://, --gh-host https://, "--gh-host", "https://, --gh-host="https://, GITHUB_HOST: 'https://, GITHUB_HOST='https://, GITHUB_HOST=http://localhost, GITHUB_HOST=http://127.0.0.1
Counts only in files that mention github-mcp-server or GITHUB_PERSONAL_ACCESS_TOKEN.