# Product Context
## Why This Exists
Developers need GitHub MCP tools in their IDEs (Kiro, VS Code, Cursor) but running individual local MCP servers per developer is unmanageable. This project centralizes the GitHub MCP Server as a shared service behind corporate auth.
## Problems Solved
- No need for each developer to manage their own GitHub MCP Server instance
- Centralized GitHub PAT management (one PAT in Secrets Manager vs distributed tokens)
- Corporate auth via Okta instead of individual token management
- VPN-only access ensures the service isn't exposed to the internet
## How It Works (User Perspective)
1. Connect to AWS Client VPN
2. Add MCP config to IDE (one-time setup with `mcp-remote`)
3. On first use, browser opens for Okta login
4. After login, GitHub tools are available in the IDE
5. Tokens auto-refresh; reconnect if session expires
## User Experience Goals
- Minimal setup: one JSON config block + VPN connection
- Transparent auth: browser-based Okta login, auto-refresh
- Multi-developer: no conflicts, each developer gets their own session
