git-mcp-server

The server demonstrates strong security awareness, implementing detailed path sanitization (`sanitizePath` to prevent directory traversal and enforce `GIT_BASE_DIR`), robust authentication via JWT/OAuth, and scope-based authorization. Critical secrets are loaded from environment variables. Direct execution of native Git CLI commands (via `CliGitProvider`) is a potential attack surface, but the codebase uses a command builder with argument validation and a `SAFE_GIT_OPTIONS` set, significantly mitigating risks. A 'development mode' bypass for authentication is present for convenience, but the `JwtStrategy` explicitly warns and enforces `MCP_AUTH_SECRET_KEY` in production, which is good practice. Proper configuration of `MCP_AUTH_MODE` and `GIT_BASE_DIR` is crucial for production deployments.