Skip to main content
Glama
Sign In
copilot-google-connector

copilot-google-connector

by torosent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to copilot-google-connector

No user-submitted related servers found.

    Related Servers

    • gmail-mcp

      DavidVinu
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read and draft emails across multiple Gmail accounts at once, with strict safeguards that prevent sending, deleting, or modifying mailbox settings.
      295 npm
      AGPL 3.0

    • gws-mcp

      borabicaco
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to read and, when explicitly enabled, modify Gmail, Google Calendar, and Google Drive across multiple Google Workspace accounts while defaulting to read-only access.
      1
      MIT

    • Google MCP Hub

      rescueahero4
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to work across several Google accounts at once, searching every Gmail inbox, reading and drafting email, browsing Drive, and checking or scheduling across multiple Calendars in a single conversation. It supports tags for grouping accounts and cross-account tasks, and only creates drafts, files, and events rather than sending anything without you.
      MIT

    • Google MCP

      shayanhoshyari
      A
      license
      A
      quality
      C
      maintenance
      Enables reading Gmail messages and managing drafts without sending, managing Calendar events, and searching, downloading, uploading, or updating Drive files for a personal account through local OAuth-backed tools.
      20
      MIT
    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.9/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair: accounts, Gmail operations (search, read thread, read message, read attachment, create draft), Calendar operations (list, get, create, update, delete, list events, list instances, free/busy, find availability, rsvp), and operation management. No two tools have overlapping responsibilities; even similar actions like read_thread vs read_message are clearly separated by scope. Descriptions reinforce these boundaries with explicit account/calendar requirements and behavioral constraints.

    Naming Consistency5/5

    All tool names follow a consistent pattern: <domain>_<action>_<noun>, with domains being accounts, gmail, calendar, or operation. Actions are consistent verbs like list, read, get, create, update, delete, cancel, and status. Even compound verbs like find_availability and free_busy maintain readability and align with the pattern.

    Tool Count4/5

    18 tools is slightly above the ideal range (3-15) but justified by covering two distinct Google services (Gmail and Calendar) plus operation management. The count is not excessive given the breadth of features, and each tool earns its place with no redundancy. It feels well-scoped for a connector that handles multiple domains.

    Completeness4/5

    The tool surface covers core workflows for Gmail (search, read, draft creation) and Calendar (full CRUD, free/busy, availability, RSVP). Notable gaps include no Gmail send tool and no ability to modify existing drafts, but these are likely intentional safety restrictions. Operation status and cancellation complete the lifecycle, leaving few dead ends for agents.

    Resources