google-workspace-mcp-server

The server relies on environment variables for Google OAuth credentials (client ID, client secret, refresh token), which is a good security practice. It interacts with Google APIs using the official `googleapis` library. Temporary files are created locally for handling attachments and exported Google Workspace documents, with unique filenames to mitigate simple overwrite risks. Input schemas are defined using Zod, offering validation. No 'eval' or obvious obfuscation found. The primary security consideration lies in the sensitive nature of the Google API access and the potential for an agent to misuse granted permissions if not carefully constrained by the orchestrating system.