Add multi-user HTTP mode: per-request GitHub token, docs, and tests

[thomcost]

 - Added multi-user HTTP mode with per-request GitHub token via Authorization header.
 - Updated documentation and added unit/e2e tests.
 - All tests passing.

Closes: Issue #471

[SamMorrowDrums]

Hi thank you for your contribution, we will be releasing a remote server soon, using this repo as a library. We won't be merging PRs adding this functionality for the foreseeable future.

[thomcost]

Hi thank you for your contribution, we will be releasing a remote server soon, using this repo as a library. We won't be merging PRs adding this functionality for the foreseeable future.

Who is "we"?

[SamMorrowDrums]

GitHub, I am an internal maintainer.

[tcostello-godaddy]

Hi thank you for your contribution, we will be releasing a remote server soon, using this repo as a library. We won't be merging PRs adding this functionality for the foreseeable future.

Do you have any ballpark dates? please :)

[SamMorrowDrums]

I cannot be exact, but its fairly imminent.

[tonytrg]

@tcostello-godaddy remote mcp is live :) https://github.com/github/github-mcp-server?tab=readme-ov-file#remote-github-mcp-server

@thomcost thank you for the contribution, since we offer remote mcp now, as @SamMorrowDrums mentioned for now this will not be added to the local version.
Still the contribution is really appreciated, cheers!

[SamMorrowDrums]

Update: we may reconsider to unblock GHES use-cases.

[tonytrg]

related to #523

[ransonjb]

Update: we may reconsider to unblock GHES use-cases.

Hey @SamMorrowDrums
I would add a "+1": we are working on an important project where support for GHES is required.
Would you have an ETA for this support?

[SamMorrowDrums]

Hard to say @ransonjb at this moment I am afraid. There are a lot of implementation details for anything beyond single server hosting of MCP too, and I am also cautious about hosting support burdon too. Things like concurrency, authentication etc.

On our remote server we have to do a lot to handle horizontal scaling, safe concurrency and we authorize users on the way in (before hitting the MCP server at all), and we have full oauth support. These sorts of considerations make it difficult for end users build and release it safely without customisation for their individual hosting scenarios.

Using a fork can unblock you if you need this right away. I expect at some point we will merge the streamable http transport, but I cannot say when.

[icep87]

Any progress on the unblocking of GHES or adding HTTP-stream support for this?

[rupinder2]

Just testing out this branch, and I can't seem to connect using MCP inspector.

[SamMorrowDrums]

Hi thank you, we finally merged an http entrypoint today: #1482 (comment)