Skip to main content
Glama
ZatesloFL

Google Workspace MCP Server

by ZatesloFL

Related Servers

Alternatives to Google Workspace MCP Server

No user-submitted related servers found.

    Related Servers

    TDQS

    B3.3/5.0

    Scored across 84 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific Google Workspace services (Docs, Gmail, Calendar, etc.), with clear boundaries. However, some overlap exists, such as get_doc_content and get_drive_file_content for document retrieval, and multiple comment tools (create_document_comment, read_document_comments, etc.) that could cause confusion if not carefully distinguished by context.

    Naming Consistency5/5

    Tool names follow a highly consistent snake_case pattern with clear verb_noun conventions (e.g., create_doc, modify_event, list_calendars). The naming is uniform across all 84 tools, making it predictable and easy to understand the action and target resource for each tool.

    Tool Count2/5

    With 84 tools, the set is excessively large for a single server, making it overwhelming and difficult for agents to navigate efficiently. While Google Workspace is broad, this count suggests poor scoping, as many tools could be consolidated or split into focused sub-servers (e.g., separate servers for Docs, Gmail, Calendar) to improve usability.

    Completeness5/5

    The tool set provides comprehensive coverage across Google Workspace services, including full CRUD operations for Docs, Sheets, Slides, Calendar, Gmail, Drive, Tasks, and Forms. It supports complex workflows (e.g., batch operations, document structure inspection) and integrates auxiliary functions like search and authentication, leaving no obvious gaps for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues