google-services-mcp
Related Servers
Alternatives to google-services-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that connects Gmail and Google Calendar to AI assistants, enabling email search, reading, sending, and calendar management across multiple accounts with secure OAuth.1MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI assistants to manage Google Workspace (Gmail and Calendar) through natural language, including reading/sending emails, managing events, and checking availability.-
- AlicenseNot gradedqualityCmaintenanceLocal MCP server for reading/sending email via Gmail and managing Google Calendar events, enabling an AI agent to handle email and calendar operations through natural language.MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that exposes 17 Google Workspace APIs (e.g., Gmail, Drive, Calendar) as auto-generated tools for AI assistants, enabling natural language control of Google services.-
- FlicenseBqualityDmaintenanceMCP server providing full Google Workspace access (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts) using your own OAuth credentials, enabling natural language management of Google services.100-
- AlicenseAqualityBmaintenanceMCP server integrating multiple Google Workspace services including Gmail, Calendar, Drive, Sheets, Docs, Tasks, People, Forms, and Slides, enabling users to manage emails, events, files, documents, and more through natural language.15MIT
TDQS
Scored across 134 tools
Tools are strongly scoped by service and resource, so most are easy to distinguish (e.g., drive vs. docs vs. sheets prefixes). A few pairs overlap in intent—sheets_get vs. sheets_read, docs_get vs. docs_read, gmail_list vs. gmail_threads_list—but descriptions clarify the differences.
Names consistently use a google_<service>_ prefix and snake_case, making the surface predictable. There are minor ordering inconsistencies (e.g., gmail_threads_list vs. gmail_list, drive_create_folder vs. drive_upload), but overall the convention is readable.
With 134 tools, the surface is extremely large and unwieldy for an agent to navigate, even for a multi-service Google suite. Many niche and raw batch tools are included, pushing the count far beyond practical scoped-tool limits.
Coverage is broad across Drive, Gmail, Calendar, Docs, Sheets, Slides, YouTube, Forms, Tasks, Contacts, and account management, with most core CRUD/lifecycle operations present. Minor gaps exist, such as no YouTube video delete and limited Drive permission update/revision operations.