google_workspace_mcp

The server employs robust security practices, including a strong emphasis on loading sensitive credentials (Google OAuth Client ID and Secret, Custom Search API Key/Engine ID) from environment variables or Kubernetes secrets, explicitly discouraging hardcoding. It supports OAuth 2.1 for multi-user, bearer token authentication, with an `AuthInfoMiddleware` to process and validate tokens. A stateless mode (`WORKSPACE_MCP_STATELESS_MODE=true`) is available for containerized deployments to avoid file system writes. Attachment handling for Drive files uses temporary storage with expiration. The `create_drive_file` tool's support for fetching content from `file://`, `http://`, and `https://` URLs, while a powerful feature, could be a potential SSRF vector if the execution environment is not secured. Warnings regarding `OAUTHLIB_INSECURE_TRANSPORT=1` for development-only HTTP redirects are clearly stated, emphasizing HTTPS for production. The Helm chart sets good defaults for pod security contexts (non-root, dropped capabilities). Overall, the project demonstrates a high level of security awareness.