René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add Streamable HTTP Transport Support for Multi-User Mode","articleBody":"## Problem\n\nCurrently, the GitHub MCP Server only supports single-user mode, requiring a single GitHub token to be configured at startup. This limits its usage in multi-tenant environments, shared services, and enterprise scenarios where different users need to authenticate with their own GitHub tokens.\n\n## Current State\n\n- ✅ Single-user mode supports both stdio and streamable HTTP transports\n- ❌ No multi-user mode exists - server requires one GitHub token per instance\n- ❌ Cannot serve multiple users with different authentication contexts\n- ❌ Limited scalability for shared or enterprise deployments\n\n## Proposed Solution\n\nAdd a new multi-user mode with streamable HTTP transport support, enabling the server to:\n\n- Accept HTTP requests with per-request authentication tokens\n- Serve multiple users simultaneously with their own GitHub tokens\n- Run behind load balancers and reverse proxies\n- Integrate with web applications and cloud services\n- Support containerized deployments with proper port binding\n\n## Use Cases\n\n1. **Enterprise Shared Services**: One server instance serving multiple teams/users\n2. **Cloud Deployments**: Multi-tenant SaaS applications using GitHub integration\n3. **Web Integration**: Web applications where users authenticate with their own GitHub tokens\n4. **Load Balancing**: Distributing requests across multiple server instances\n5. **Kubernetes Deployments**: Enabling proper health checks and service discovery\n6. **API Gateway Integration**: Direct HTTP endpoints for API management platforms\n\n## Expected Implementation\n\n### Command Interface\n```bash\n# New multi-user mode with HTTP transport\n./github-mcp-server multi-user --port 8080\n\n# Existing single-user modes still work\n./github-mcp-server stdio                    # Single-user stdio\n./github-mcp-server streamable-http          # Single-user HTTP\n```\n\n### Configuration Options\n- Configurable port binding via `--port` flag\n- Per-request authentication token extraction from request headers/context\n- No global GitHub token required - tokens provided per request\n- Backward compatibility with existing single-user modes\n\n### Technical Details\n- Utilize existing `server.NewStreamableHTTPServer()` from mcp-go library\n- Implement per-request authentication model with auth tokens\n- Create new multi-user toolsets that extract tokens from request context\n- Proper error handling and logging for HTTP transport\n- Support for standard HTTP headers and content types\n\n## Benefits\n\n1. **🌐 Production Ready**: Enables production deployments in cloud environments\n2. **🔄 Scalable**: Works seamlessly with load balancers and auto-scaling\n3. **🔌 Integration Friendly**: Direct HTTP API for web applications and services\n4. **📦 Container Native**: Proper port binding for containerized deployments\n5. **👥 Multi-Tenant**: Support multiple users with their own GitHub authentication\n6. **⚡ Performance**: HTTP transport optimized for distributed scenarios\n\n## Acceptance Criteria\n\n- [ ] New `multi-user` command that starts HTTP server on configurable port\n- [ ] Per-request authentication tokens work correctly\n- [ ] Multiple users can use the server simultaneously with their own tokens\n- [ ] Backward compatibility with existing single-user modes\n- [ ] Proper error handling and logging for multi-user scenarios\n- [ ] Documentation for new multi-user mode\n- [ ] Docker support for multi-user HTTP deployments\n\n## Additional Context\n\nThis enhancement would introduce a completely new operational mode to the GitHub MCP Server, making it suitable for enterprise and multi-tenant deployments. Unlike the current single-user model where one GitHub token is configured globally, this multi-user mode would extract authentication tokens from each individual request.\n\nThe implementation should leverage the existing mcp-go library's streamable HTTP capabilities while introducing a new multi-user authentication approach that differentiates this mode from the existing single-user implementations. ","author":{"url":"https://github.com/devendershekhawat","@type":"Person","name":"devendershekhawat"},"datePublished":"2025-06-04T05:10:13.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":15},"url":"https://github.com/471/github-mcp-server/issues/471"}