Comprehensive Google Workspace MCP server and CLI for Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Chat, Apps Script, Tasks, Contacts, and Custom Search workflows.
Google Workspace MCP can read, create, edit, send, share, delete, and manage data across Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Chat, Apps Script, Tasks, Contacts, and Search depending on configured scopes and tool tier., Start with the smallest useful tool tier and read-only or service-specific scopes where possible., Require human approval before sending email or chat messages, sharing Drive files, changing permissions, deleting content, editing business documents, or executing Apps Script workflows., Protect OAuth client secrets, refresh tokens, service account keys, and credential stores.
Privacy notes
Emails, attachments, Drive files, calendar events, documents, spreadsheets, presentations, form responses, chat messages, contacts, search queries, OAuth tokens, and tool logs may be exposed to the MCP client and model., The repository describes a self-hosted data path to Google APIs, but prompts and tool results still flow through the chosen AI client and model provider., Review organization data retention, Workspace admin policies, OAuth app verification, and model-provider retention before connecting production accounts.
Author
Taylor Wilsdon
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
4 safety and 3 privacy notes across 3 risk areas. Review closely: credentials & tokens, permissions & scopes, third-party handling.
3 areas
SafetyPermissions & scopesGoogle Workspace MCP can read, create, edit, send, share, delete, and manage data across Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Chat, Apps Script, Tasks, Contacts, and Search depending on configured scopes and tool tier.
SafetyPermissions & scopesStart with the smallest useful tool tier and read-only or service-specific scopes where possible.
SafetyPermissions & scopesRequire human approval before sending email or chat messages, sharing Drive files, changing permissions, deleting content, editing business documents, or executing Apps Script workflows.
SafetyCredentials & tokensProtect OAuth client secrets, refresh tokens, service account keys, and credential stores.
PrivacyCredentials & tokensEmails, attachments, Drive files, calendar events, documents, spreadsheets, presentations, form responses, chat messages, contacts, search queries, OAuth tokens, and tool logs may be exposed to the MCP client and model.
PrivacyThird-party handlingThe repository describes a self-hosted data path to Google APIs, but prompts and tool results still flow through the chosen AI client and model provider.
PrivacyCredentials & tokensReview organization data retention, Workspace admin policies, OAuth app verification, and model-provider retention before connecting production accounts.
Safety notes
Google Workspace MCP can read, create, edit, send, share, delete, and manage data across Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Chat, Apps Script, Tasks, Contacts, and Search depending on configured scopes and tool tier.
Start with the smallest useful tool tier and read-only or service-specific scopes where possible.
Require human approval before sending email or chat messages, sharing Drive files, changing permissions, deleting content, editing business documents, or executing Apps Script workflows.
Protect OAuth client secrets, refresh tokens, service account keys, and credential stores.
Privacy notes
Emails, attachments, Drive files, calendar events, documents, spreadsheets, presentations, form responses, chat messages, contacts, search queries, OAuth tokens, and tool logs may be exposed to the MCP client and model.
The repository describes a self-hosted data path to Google APIs, but prompts and tool results still flow through the chosen AI client and model provider.
Review organization data retention, Workspace admin policies, OAuth app verification, and model-provider retention before connecting production accounts.
Prerequisites
Python 3.10 or newer and uv or uvx.
Google Cloud project with OAuth credentials.
Required Google Workspace APIs enabled for the services you plan to use.
OAuth consent, scopes, and redirect settings reviewed for the target account or organization.
MCP client such as Claude, Codex, or another compatible host.
Google Workspace MCP Server, published as workspace-mcp, connects MCP clients
to Google Workspace services. It covers Gmail, Drive, Calendar, Docs, Sheets,
Slides, Forms, Chat, Apps Script, Tasks, Contacts, and Custom Search through a
single server and CLI.
The project supports local stdio-style usage, HTTP transport, OAuth 2.0 and
OAuth 2.1 patterns, multi-user bearer-token deployments, stateless operation,
tool tiers, service-specific tool selection, and CLI access to local or remote
instances.
These sources were reviewed on 2026-06-05. Prefer the live docs for current
OAuth setup, API enablement, service coverage, tool tiers, remote deployment
guidance, and security recommendations.
Features
Broad Google Workspace coverage across Gmail, Drive, Calendar, Docs, Sheets,
Slides, Forms, Chat, Apps Script, Tasks, Contacts, and Custom Search.
CLI plus MCP server usage.
Tool tiers such as core, extended, and complete.
Service-specific tool selection for narrowing the exposed surface.
OAuth 2.0 and OAuth 2.1 support, including multi-user deployment patterns.
Credential store options and stateless/container-friendly modes.
Read-only and permission-oriented configuration options documented by the
project.
Installation
Create a Google Cloud project, configure OAuth credentials, enable the required
Google APIs, and set the required environment variables. Then configure your MCP
client to launch the core tool tier:
Use the README and quick-start guide for OAuth consent setup, service-specific
API enablement, HTTP transport, multi-user OAuth, read-only mode, and narrower
tool selection.
Use Cases
Search and triage Gmail messages with assistant help.
Draft or update Docs, Sheets, and Slides after human review.
Summarize Drive files or calendar context for planning.
Manage tasks and contacts from an agent workflow.
Build controlled internal automations around Google Workspace APIs.
Safety and Privacy
This server can expose and modify high-value business data. Start with the
smallest useful scope, keep credentials out of shared configs, and require human
approval before sending messages, sharing files, deleting data, changing
permissions, editing critical documents, or running Apps Script actions.
Treat prompts, tool outputs, OAuth credentials, email contents, attachments,
Drive files, documents, spreadsheets, calendar events, and chat messages as
sensitive. Review both Google Workspace admin controls and AI provider retention
before connecting production accounts.
Duplicate Check
No taylorwilsdon/google_workspace_mcp entry or source URL was found in
content/mcp. This entry is separate from individual Google service or search
MCP entries because it covers the broad Google Workspace suite.
Show that Google Workspace MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/google-workspace-mcp-server)
How it compares
Google Workspace MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
Comprehensive Google Workspace MCP server and CLI for Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Chat, Apps Script, Tasks, Contacts, and Custom Search workflows.
Hosted Google Calendar MCP server that lets compatible AI clients read, create, update, delete, search, and batch-edit calendar events through an HTTP endpoint and API-key authentication.
MCP server for connecting Claude to AFFiNE Cloud or self-hosted AFFiNE workspaces, documents, databases, comments, collections, folders, tags, notifications, blobs, access tokens, semantic page composition, templates, edgeless canvas data, and workspace organization workflows over stdio or HTTP.
✓Google Workspace MCP can read, create, edit, send, share, delete, and manage data across Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Chat, Apps Script, Tasks, Contacts, and Search depending on configured scopes and tool tier.
Start with the smallest useful tool tier and read-only or service-specific scopes where possible.
Require human approval before sending email or chat messages, sharing Drive files, changing permissions, deleting content, editing business documents, or executing Apps Script workflows.
Protect OAuth client secrets, refresh tokens, service account keys, and credential stores.
✓Repository-specific endpoints reduce the chance of an agent querying the wrong project, while the dynamic endpoint relies on correct target selection.
Verify generated code against the upstream project documentation and changelog before applying it to production systems.
Use caution with private, unreleased, or embargoed repositories unless you self-host and have reviewed access controls.
✓CalendarMCP is a hosted remote MCP service at `https://calendarmcp.ai/api/mcp`; the public repository contains docs, manifests, and client examples, not the hosted backend source.
Calendar write tools can create, update, delete, quick-add, batch-update, and manage attendees for calendar events when the API key has write access.
Batch updates can affect up to 50 events in one call, so review target filters, recurrence handling, and proposed edits before allowing broad changes.
Use CalendarMCP's per-calendar read/write matrix to limit which calendars each assistant can access.
Run `find_free_time` or manually confirm availability before creating meetings that invite other people or reserve shared resources.
Keep destructive actions such as deleting events or changing recurring meetings behind explicit human confirmation.
✓The full tool surface can create, update, publish, revoke, move, replace, and delete AFFiNE workspaces, documents, folders, collections, comments, database rows, blobs, surface elements, tags, and access tokens.
Start with AFFINE_TOOL_PROFILE=read_only or disable groups such as destructive, admin, blobs, users, access_tokens, docs.database, or write when the assistant only needs discovery or reading.
HTTP mode exposes MCP endpoints and must be protected with bearer or OAuth authentication, HTTPS, allowed origins, and deployment-level access controls.
AFFiNE Cloud requires API tokens for MCP usage; avoid trying to automate email/password login against Cloud deployments.
Cookie and password-based auth can grant broad account access and should be avoided for unattended or shared deployments.
Privacy notes
✓Emails, attachments, Drive files, calendar events, documents, spreadsheets, presentations, form responses, chat messages, contacts, search queries, OAuth tokens, and tool logs may be exposed to the MCP client and model.
The repository describes a self-hosted data path to Google APIs, but prompts and tool results still flow through the chosen AI client and model provider.
Review organization data retention, Workspace admin policies, OAuth app verification, and model-provider retention before connecting production accounts.
✓GitMCP may receive repository choices, documentation queries, tool calls, and surrounding prompts through the MCP client.
The README states that the hosted service does not collect personal information or store queries, but teams should still review the current privacy posture before sending proprietary context.
Self-hosting may be preferable for private repositories, regulated work, or sensitive customer projects.
✓Calendar results can expose meeting titles, attendees, email addresses, locations, descriptions, links, reminders, recurrence patterns, availability, and private schedule context.
One CalendarMCP API key can cover multiple connected Google accounts; review which accounts and calendars are attached before sharing a config.
Google OAuth tokens and CalendarMCP API keys are sensitive credentials. Keep them out of prompts, issue comments, screenshots, shell history, logs, and repository files.
Hosted access means calendar data and tool calls pass through CalendarMCP and the connected MCP client; review retention and data-processing policies before connecting sensitive calendars.
Use synthetic calendars or narrow test calendars for demos, screenshots, and workflow testing.
✓Workspaces, document titles, document bodies, comments, tags, database schemas, database rows, edgeless canvas data, notifications, user profiles, access-token metadata, blobs, and exported markdown can be sent to the MCP client and model.
API tokens, cookies, passwords, bearer tokens, OAuth config, and saved config files should be treated as secrets and kept out of prompts, logs, screenshots, issues, and committed MCP config.
Generated or modified documents can persist in AFFiNE and may become visible to collaborators depending on workspace permissions and sharing state.
Blob upload, cleanup, export, and publish/revoke workflows can expose files, generated content, or collaboration state beyond the current prompt.
Prerequisites
Python 3.10 or newer and uv or uvx.
Google Cloud project with OAuth credentials.
Required Google Workspace APIs enabled for the services you plan to use.
OAuth consent, scopes, and redirect settings reviewed for the target account or organization.
MCP client that supports remote MCP servers or an mcp-remote bridge.
GitHub repository owner and repository name, GitHub Pages site, or the dynamic GitMCP docs endpoint.
Network access to GitMCP and GitHub.
Team agreement on which repositories can be queried through a hosted MCP service.
CalendarMCP account and dashboard access at `https://calendarmcp.ai`.
Google account or shared calendars that may be connected to CalendarMCP.
CalendarMCP API key stored outside prompts, screenshots, logs, and repository files.
MCP client that supports remote HTTP MCP servers and bearer-header authentication.
Node.js and npm for installing the affine-mcp-server package.
AFFiNE Cloud API token or approved self-hosted AFFiNE credentials.
AFFiNE base URL for the Cloud or self-hosted deployment.
Clear workspace scope and least-privilege tool profile before enabling write, admin, destructive, blob, or access-token tools.