A1 Google Calendar MCP
Related Servers
Alternatives to A1 Google Calendar MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to securely manage Google Calendar events using natural language, including scheduling, rescheduling, deleting, and searching events.1-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage Google Calendar events, check availability, handle recurring events, and coordinate across multiple accounts and calendars through natural language.7,967 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to read, create, update, delete, and search Google Calendar events across multiple accounts, check availability, and handle recurring events and invitations through natural language.66 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Google Calendar through natural language interactions with features like creating, updating, and deleting events, searching calendars, and supporting natural language date/time inputs.9 npm2MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI to create, read, update, and delete Google Calendar events and manage calendars through natural language.2-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Google Calendar events, including reading, searching, creating, updating, and deleting events, as well as checking availability and listing calendars.20 npmMIT
TDQS
Scored across 13 tools
Each tool targets a distinct resource and action: calendar listing/fetching, event CRUD, move, instance expansion, free/busy lookup, specialized event creation, and raw API access. The specialized create_out_of_office and create_focus_time are clearly differentiated from create_event by their purpose and constraints.
Most tools follow a consistent snake_case verb_noun pattern (list_events, get_event, create_event, update_event, delete_event, move_event), with create_out_of_office and create_focus_time fitting the same style. raw_request is the only exception, but as an intentional escape hatch it is a minor deviation.
13 tools is well within the ideal 3-15 range and each tool earns its place for calendar management. The count covers core CRUD, recurrence handling, availability lookup, specialized event types, and a raw API escape hatch without feeling bloated.
The surface covers calendar listing/fetching, full event lifecycle including move and recurring-instance management, free/busy queries, and specialized OOO/focus events. raw_request fills any remaining gaps such as calendar creation, ACLs, colors, quickAdd, and conference cleanup, leaving no significant dead ends.