grr
Related Servers
Alternatives to grr
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocal-first Microsoft Outlook MCP server: a single Go binary that manages calendar events and mail through the Microsoft Graph API over stdio, with tokens stored in the OS keychain and no Entra ID app registration required. Exposes four aggregate tools (calendar, mail, account, system) dispatched by an operation verb, with multi-account support and read-only and mail-gating modes.445MIT
- AlicenseNot gradedqualityAmaintenanceGmail, Google Calendar, Drive, Sheets, Tasks and Contacts for AI agents, using your own Google OAuth login. Runs locally over stdio with 23 tools: search and send mail, manage events, read and write Sheets, upload and share Drive files.465 PyPIMIT
- AlicenseAqualityCmaintenanceMost Google Workspace MCPs let you read. This one lets you write — 28 authoring tools on top of taylorwilsdon/google_workspace_mcp, including markdown-to-Docs, smart chips, and recursive Drive copy.1002MIT
- AlicenseBqualityDmaintenanceProduction-ready MCP server for Google Workspace providing broad coverage across Gmail, Drive, Calendar, Docs, Sheets, and more, with safe-by-default write operations and markdown-to-Google-Docs support.10050 PyPIMIT
- FlicenseNot gradedqualityBmaintenanceLightweight MCP server for Google Workspace (Calendar, Gmail, Drive) designed for Hermes Agent in Docker, enabling tools to list events, messages, and files via CLI.-
- 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.-
TDQS
Scored across 402 tools
Tools are generally distinguishable because names encode service, resource, and action (e.g. calendar.events.list vs gmail.users.messages.list). Overlap remains in a few places: deprecated drive.teamdrives.* duplicates drive.drives.*, conversionEvents mirrors keyEvents, and patch/update pairs require attention to descriptions.
The naming scheme is highly systematic: service.resource.action with dotted hierarchy and API-derived action names. Consistency is slightly weakened by mixed verb conventions across services (create vs insert vs add) and legacy aliases, but the pattern is still predictable.
402 tools is an extreme mismatch for an agent-facing MCP server; even a broad Google Workspace surface does not need every REST method exposed as a separate tool. The count is far beyond the 3-15 well-scoped range and creates a huge selection burden.
Coverage is very deep across Calendar, Drive, Gmail, Chat, Docs, Sheets, Slides, Forms, Tasks, People, Analytics, Search Console, and Apps Script, with full CRUD/lifecycle operations for many resources. Minor gaps remain for adjacent Workspace products such as Meet, Admin SDK, Keep, and Classroom, but core workflows are covered.