feat: http mode for github mcp server. #1860
Draft
+479
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds HTTP server mode enabling multi-tenant deployments where each client provides their own GitHub token via
Authorization: Bearer <token>header.Why
Enterprise scenarios require centralized MCP infrastructure serving multiple authenticated clients concurrently, which stdio mode's single-token-per-process model cannot support.
What changed
httpsubcommand with--portflag (default 8080)RunHTTPServer()using MCP SDK'sStreamableHTTPHandlerAuthorizationheaderHTTPServerConfigstruct for HTTP-specific configurationMCP impact
HTTP mode uses existing tools—only the transport and authentication model changed.
Prompts tested (tool changes only)
N/A
Security / limits
Tokens validated per-request, never stored. Each client's token creates isolated server instance with their permissions. Token scope filtering applied for PAT tokens.
Tool renaming
Lint & tests
./script/lint./script/testDocs
Added HTTP mode section to README with client configuration examples (VS Code, Claude Desktop), Docker deployment patterns (basic, production with docker-compose), and troubleshooting guide.