-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add multi-user HTTP mode: per-request GitHub token, docs, and tests #489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
- Replace per-request MCP server creation with token-aware client factories - Add proper HTTP timeouts and graceful shutdown - Enhance token validation with strict Bearer format checking - Add comprehensive tests for token extraction and context injection - Improve error handling and response formatting - Update documentation to reflect performance optimizations
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"? |
GitHub, I am an internal maintainer. |
Do you have any ballpark dates? please :) |
I cannot be exact, but its fairly imminent. |
@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. |
Update: we may reconsider to unblock GHES use-cases. |
related to #523 |
Hey @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. |
Closes: Issue #471