Skip to main content
Glama
guinacio

mcp-google-workspace

by guinacio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-google-workspace

No user-submitted related servers found.

    Related Servers

    • 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.
      79
      5,250 npm
      1
      MIT

    • gworkspace-mcp

      LeooNic
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for automating Google Workspace applications including Sheets, Apps Script, Drive, Docs, and Gmail. It enables users to manipulate spreadsheets, edit scripts, manage files, and send emails directly from conversational AI interfaces.
      31
      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.
      -

    • Google Workspace MCP Server

      ghratika
      F
      license
      Not graded
      quality
      D
      maintenance
      A complete MCP server integrating Gmail and Google Docs, enabling email management (list, send, search, reply) and document operations (create, edit, search, share) through natural language.
      -
    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 15 tools

    Disambiguation3/5

    Most tools have distinct purposes, but the file tools overlap: files_list_files and files_list_files_page both list files, and files_file_manager is a catch-all that could confuse selection. The meta-tools call_tool and search_tools also add ambiguity about when to use direct vs meta tools.

    Naming Consistency3/5

    Naming is mostly verb_noun with underscores, but there are inconsistencies: some tools use google_workspace, others just workspace, and the files_ prefix is applied inconsistently (files_file_manager is a noun phrase, not a verb). The files_list_files_page variant deviates from the simple verb_noun pattern.

    Tool Count4/5

    15 tools is within the expected range, but the set includes redundant file listing tools and generic meta-tools (call_tool, search_tools) that could be considered unnecessary. Still, the count is reasonable for the scope.

    Completeness2/5

    The tool surface lacks common Google Workspace operations like sending email, creating events, or reading contacts beyond search. It focuses on connection management, search, and a generic action mechanism, leaving significant gaps for an agent trying to perform typical Workspace tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources