gdrive-mcp-server

The primary security concern is the critical discrepancy in authentication methods. The README and `docker run` command instruct users to configure a Google Service Account via `GOOGLE_APPLICATION_CREDENTIALS`, which is suitable for automated server deployments. However, the Go source code (specifically in `pkg/driveapi/client.go`) implements an interactive OAuth 2.0 flow, requiring an `Oauth.json` client secret and manual user input for an authorization code. This mismatch means the server, as currently coded, will not utilize the provided service account credentials and will likely hang awaiting manual user authorization, making it unsuitable for automated server operation. Hardcoded paths for OAuth client secrets (`/app/secrets/Oauth.json`) and tokens (`/app/data/token.json`) are used internally, requiring careful management of Docker volume mounts. No direct 'eval' or malicious code patterns were found.