gws-mcp
Related Servers
Alternatives to gws-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceA multi-account Google Workspace MCP server that drives Gmail, Google Calendar, and Google Drive across any number of Google accounts in parallel from one server.422MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for multiple Google accounts, providing tools for Gmail, Drive, Calendar, Tasks, and Contacts with multi-account support and cross-MCP file handoff.MIT

exfu-multiaccountofficial
FlicenseNot gradedqualityBmaintenanceA local MCP server that lets AI assistants access Gmail, Drive, Docs, and Calendar across multiple Google accounts, routing each request by a human-readable account alias. It supports reading, searching, and writing with per-account tagging while keeping OAuth credentials secure and separate.-- AlicenseAqualityAmaintenanceMulti-account Google Workspace MCP server — Gmail, Calendar, and Drive with smart routing.491MIT
- FlicenseBqualityDmaintenanceMCP server providing full access to Google Workspace services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts) using OAuth authentication.1001-
- AlicenseNot gradedqualityAmaintenanceA multi-account, token-efficient MCP server for Google Workspace services including Gmail, Calendar, Drive, Docs, and Sheets. It enables secure management of multiple accounts with compact data retrieval and keychain-backed authentication for efficient workflow automation.3MIT
TDQS
Scored across 10 tools
Each tool maps to a distinct resource/action combination: accounts, Gmail messages/labels, calendar availability, and Drive files/search. There is no meaningful overlap between search, read, and list operations.
All tool names follow a consistent snake_case resource_action pattern (accounts_list, gmail_search, calendar_list_events, drive_read_file). Verb placement and object nouns are uniform across the set.
Ten tools cover four Google Workspace areas without bloat. Each tool serves a non-redundant purpose, and the count is within the ideal 3-15 range for an MCP server.
The read/query workflows for Gmail, Calendar, and Drive are well represented, and account lifecycle is complete. Gaps such as sending email, creating calendar events, or writing Drive files appear intentional given the read-only consent, but would limit broader workspace management.