Google Workspace MCP connector
Related Servers
Alternatives to Google Workspace MCP connector
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceExposes 25 tools for Claude Code across Gmail, Calendar, Drive, Docs, Sheets, and Slides. Supports multi-account, local-first, encrypted OAuth tokens.102-
- AlicenseNot gradedqualityDmaintenanceGives Claude read/write access to your own Gmail, Google Docs, Google Sheets, and Google Tasks via a tiny always-on web service.ISC
- AlicenseNot gradedqualityCmaintenanceEnables Claude AI to directly interact with Gmail through natural language for comprehensive email management including sending, reading, searching, organizing, and managing drafts and labels. Uses secure OAuth authentication and runs locally without third-party servers.MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Google Workspace services (Gmail, Calendar, Drive, Docs, Sheets, Chat, Slides, People) through natural language using Claude Desktop, Claude Code CLI, and other MCP clients.491 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude and Gemini to access and manage multiple Google accounts simultaneously across services such as Gmail, Drive, Calendar, YouTube, Sheets, Analytics, AdSense, and Fitness, with create, read, update, and delete operations. It runs locally without external intermediaries to keep account access private.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to search, read, and draft email across multiple linked Gmail and Google Workspace mailboxes per user, with per-user isolation and Google sign-in. Self-hosted, drafts-only today, so users send from Gmail themselves.MIT
TDQS
Scored across 72 tools
Product-prefixed namespaces (gmail_, drive_, docs_, sheets_, slides_, ga_, ads_) plus action-specific suffixes make almost every tool clearly distinguishable, e.g. gmail_send vs gmail_send_draft vs gmail_reply. The only soft overlaps are the generic drive_read_file_text versus the per-product readers (sheets_read, docs_read, slides_read), and the three *_batch_update raw-API escape hatches which sit near their specific counterparts, but the descriptions explicitly frame these as advanced/generic alternatives.
The set follows a very predictable <product>_<verb>_<object> snake_case convention (drive_get_file, sheets_append_rows, slides_set_notes, ads_set_status). A few tools deviate by using noun-only or adjectival forms (ga_overview, drive_about, google_setup, ads_query), which breaks the pattern slightly without hurting readability.
72 tools is far beyond what an agent can hold in working context, and the surface is heavy even though it is justified by bundling seven distinct Google products. Each individual domain is reasonably scoped (5-17 tools), but the aggregate volume forces selection errors and bloats every prompt.
Per-product lifecycle coverage is strong: Gmail spans search/read/thread/send/reply/drafts/attachments/labels/modify, Drive covers the full file and sharing lifecycle, and Docs/Sheets/Slides each offer create, read, edit, formatting, and raw batchUpdate escape hatches. Gaps remain at the edges — no Google Calendar/Contacts/Tasks surface despite 'Workspace' branding, no label deletion, and Ads is read-plus-status/budget only with no campaign creation.