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,443 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.92 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.13 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.366 npmMIT
TDQS
Scored across 19 tools
Each tool has a clearly distinct purpose: auth lifecycle, calendar listing, event CRUD, instance expansion, free/busy lookup, and specialized event creation are all separated by explicit names and descriptions. Even similar tools like create_focus_time and create_out_of_office are differentiated by their event type and auto-decline semantics.
The dominant pattern is snake_case verb_noun (list_events, create_event, delete_event, query_free_busy), which is predictable and consistent. Minor deviations like auth_status, setup_instructions, and raw_request are still clear but don't follow the verb-first convention.
At 19 tools, the set is slightly larger than the typical 3-15 range, but the auth/setup tools and raw_request earn their place for a full Google Calendar integration. The count feels somewhat heavy but is justified by the combination of OAuth connection flow and calendar operations.
The set covers the full event lifecycle (create/read/update/delete/move/list), recurrence instances, free/busy lookup, special event types, and a complete OAuth flow. raw_request provides an explicit escape hatch to the entire Calendar v3 API, covering any long-tail gaps like calendar CRUD or ACL management.