Skip to main content
Glama
GhazwaPasha

Google Workspace MCP Server

by GhazwaPasha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Google Workspace MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-google-workspace

      guinacio
      A
      license
      B
      quality
      A
      maintenance
      MCP 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.
      15
      MIT

    • google-services-mcp

      nabheet
      A
      license
      B
      quality
      A
      maintenance
      MCP server that gives AI agents direct access to Google services including Gmail, Calendar, Drive, and more, with multi-account OAuth support. Enables reading and sending email, managing calendar events, and interacting with Google files through natural language.
      60
      22 npm
      1
      MIT

    • gws_mcp

      praneshnikhar
      F
      license
      Not graded
      quality
      B
      maintenance
      An 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.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 157 tools

    Disambiguation4/5

    Each service has a clear prefix (gmail_, drive_, docs_), and most tools target a distinct resource+action. A few near-overlaps exist (docs_append_text vs docs_append_paragraph, slides_set_text vs slides_add_text) but descriptions differentiate them well. The sheer volume of tools introduces some selection risk, but the boundaries are generally clear.

    Naming Consistency5/5

    All 157 tools follow a consistent snake_case service_verb_noun pattern (e.g., gmail_send, drive_trash, sheets_append). No mixed conventions, no camelCase, no vague verbs like 'do' or 'handle'. This is a model of naming discipline.

    Tool Count1/5

    157 tools is an extreme count, far exceeding the '50+' threshold for a single server. While it covers multiple Google services, the set is a monolithic grab bag that would overwhelm any agent. It would be far better split into per-service servers (e.g., gmail-mcp, drive-mcp, docs-mcp).

    Completeness4/5

    Most service areas have strong CRUD coverage: Gmail, Drive, Docs, Sheets, Slides, and Contacts all offer create/read/update/delete or equivalent operations. Minor gaps exist (task lists lack delete/update, forms lack delete), but the workspace domain is broadly covered with no fatal dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources