Skip to main content
Glama
shayanhoshyari

Google MCP

by shayanhoshyari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Google MCP

No user-submitted related servers found.

    Related Servers

    • gmail-mcp-server

      fbassas
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and reading Gmail messages, listing labels, and creating email drafts without sending or deleting emails.
      62 npm
      MIT

    • gsuite-mcp

      pranavgade20
      A
      license
      B
      quality
      C
      maintenance
      Enables multi-account access to Gmail, Google Calendar, Docs, Sheets, and Drive over local stdio or authenticated HTTPS, including read operations and explicitly gated write operations for email, calendar, documents, and spreadsheets.
      24
      5 npm
      MIT

    • email-mcp

      pavankrishna813
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables searching contacts, drafting, and sending emails via the Gmail API with explicit user approval required before sending.
      11 npm
      ISC

    • copilot-google-connector

      torosent
      F
      license
      A
      quality
      C
      maintenance
      Enables GitHub Copilot to read and search multiple Google accounts, create unsent Gmail drafts, and manage Google Calendar events with explicit account selection and authenticator-backed approvals for risky writes.
      18
      -

    • mcp-gsuite

      khokan
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Gmail (list, search, send, label emails) and Google Calendar (list, create, update, delete events) via OAuth 2.0.
      7 npm
      -
    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

    A3.6/5.0

    Scored across 20 tools

    Disambiguation4/5

    The tools are mostly cleanly separated by service and action: Gmail read/list/draft tools, Calendar event tools, and Drive file tools each have distinct targets. Minor overlap exists between read_email and read_draft because read_email also works on a draft message_id, and download_attachment vs download_file could be briefly confused, but descriptions clarify the boundaries.

    Naming Consistency5/5

    All tools use clear snake_case with a verb_noun pattern: list_emails, read_thread, create_draft, update_event, search_files, download_file, etc. The single phrase-style name respond_to_event is still readable and consistent with the overall convention.

    Tool Count4/5

    Twenty tools is reasonable for a server spanning Gmail, Calendar, and Drive, where each service needs multiple read/write operations. It is slightly heavy compared with a single-domain server, but the count is justified by the three distinct Google Workspace areas.

    Completeness4/5

    Calendar coverage is strong, and Gmail/Drive cover the core read, draft/upload, update, and download workflows. There are some notable gaps such as no Gmail draft deletion, no Drive deletion or move/rename, and limited listing outside search, but agents can work around most of these for the stated draft-and-file-transfer focus.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources