| FMRS | 61 / 100 · C | 61 / 100 · C |
|---|
| Reliability | 8 / 20 | 8 / 20 |
|---|
| Security and permissions | 13 / 20 | 13 / 20 |
|---|
| Maintenance | 13 / 20 | 10 / 20 |
|---|
| Documentation | 15 / 20 | 16 / 20 |
|---|
| Setup experience | 12 / 20 | 14 / 20 |
|---|
| Best for | - Individuals who want to manage Google Drive files from Claude Desktop or another local MCP client
- Teams or developers who want to self-host and retain control of their own Google credentials and tokens
- Multi-step Workspace automation spanning Docs, Sheets, Slides, and Calendar
| - Developers who want to integrate Microsoft 365 data into AI assistants or custom applications.
- Scenarios requiring unified access across multiple services (email, calendar, files, Teams, etc.).
- Lightweight solutions to interact with Graph API via MCP protocol.
|
|---|
| Not for | - Users who need an official Google-maintained MCP integration (this is a third-party project)
- Users who want zero-setup access without creating their own Google Cloud OAuth credentials
- Use cases needing coverage of the full Google Workspace API surface beyond Drive, Docs, Sheets, Slides, and Calendar
| - Highly secure enterprise production environments (requires careful scope management and deployment complexity).
- Admin tasks requiring Microsoft 365 admin permissions (like security alerts, audit logs) — consider companion project ms-365-admin-mcp-server.
- Environments without Node.js.
- Support for non-Microsoft clouds like GCC High (only Global and China 21Vianet currently).
|
|---|
| Required permissions | - Google OAuth 2.0 credentials (GOOGLE_DRIVE_OAUTH_CREDENTIALS, required and marked secret)
- API access scopes for Google Drive, Docs, Sheets, Slides, and Calendar (enabled and authorized by the user in a Google Cloud project)
- Locally stored OAuth token file (tokens.json), plus member refresh tokens in team-store.json under team mode
| - Requires Microsoft Graph API permissions, dynamically requested based on enabled tools. Examples: User.Read, Mail.Read, Files.Read.
- Organization mode (--org-mode) requires additional Graph permissions for Teams, SharePoint, etc. (e.g., Sites.Read.All).
- Shared mailbox access requires delegated Mail.Read.Shared or Mail.Send.Shared scopes.
- Use --allowed-scopes to restrict tool exposure; --extra-scopes to add extra scopes. Note: --allowed-scopes only narrows, never expands permissions.
|
|---|
| Risks and side effects | - Exposure of tokens.json or team-store.json could allow access to the associated Google account(s); both must be kept secret
- Running the HTTP transport without binding to 127.0.0.1 or without TLS and access control could allow unauthorized access
- Granting broader OAuth scopes than the tools actually used can expose more data than necessary
| - Token security: File-based token storage may be exposed; use OS credential storage or secure custom paths.
- Overly broad permissions: default requests all scopes implied by tools; use allowed-scopes or tool filtering to limit.
- Multi-tenant token risk: With default 'common' tenant, personal account refresh tokens may be rejected as of June 2026, causing session expiry.
- Third-party project risk: Not officially maintained, potentially less stable than official solutions.
- HTTP mode OAuth setup complexity: Requires correct Azure AD app registration and redirect URIs.
|
|---|
| Supported clients | Claude Desktop, Gemini CLI, claude.ai custom connectors | Claude Desktop, Open WebUI |
|---|
| Tools | 1 | 10 |
|---|