A
licenseNot graded
qualityB
maintenanceEnables AI assistants to read and draft emails across multiple Gmail accounts at once, with strict safeguards that prevent sending, deleting, or modifying mailbox settings.
164 npm
AGPL 3.0
copilot-google-connector
by torosent
Related Servers
Alternatives to copilot-google-connector
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables Claude to access and manage multiple Google accounts at once across Gmail, Calendar, Drive, Contacts, and Tasks, with unified search and document text extraction.MIT
- AlicenseAqualityBmaintenanceEnables an AI assistant to connect to multiple Google accounts at once, searching and acting across Gmail, Drive, Calendar, and Contacts from a single interface.2927 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to access multiple Gmail/Google Workspace accounts for searching and reading mail, calendars, and attachments.-
- AlicenseNot gradedqualityBmaintenanceEnables interacting with Gmail and Google Calendar across multiple Google accounts, allowing email search, thread retrieval, draft creation, label management, and calendar event viewing, creation, and updating through natural language.MIT
- AlicenseAqualityFmaintenanceEnables Gmail, Google Calendar, and Google Drive access through the Model Context Protocol, supporting email management, event scheduling, and file operations.8528 npmMIT
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues