gcal-mcp
Related Servers
Alternatives to gcal-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to list, create, update, and delete Google Calendar calendars and events, run quick-add and free/busy checks, and work with primary or specified calendars through Google Calendar API tools.MIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to manage Google Calendar events, including CRUD operations, recurring events, free/busy queries, and push notifications via webhooks.ISC
- AlicenseNot gradedqualityDmaintenanceEnables seamless Google Calendar integration with MCP-compatible clients, allowing creation, viewing, updating, and deletion of calendar events via OAuth 2.0 authentication.MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Google Calendar via MCP, allowing users to list, get, search, and create events as well as list accessible calendars.-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Google Calendar through a unified MCP API for managing events, calendars, and related tools.MIT
- AlicenseNot gradedqualityBmaintenanceProvides access to Google Calendar, enabling listing calendars and events, checking availability, creating and updating events, and managing sharing through MCP.Apache 2.0
TDQS
Scored across 6 tools
The core CRUD tools are clearly separated by action and resource. The only notable overlap is color_events versus update_event, since update_event also changes color; the bulk-versus-single distinction helps but is not explicit in the tool names.
All names use snake_case and a verb_noun pattern, with list_*, create_event, update_event, and delete_event forming a predictable set. Minor inconsistency: color_events uses a plural resource while the other event tools use singular, and 'color' as a verb is less standard.
Six tools is well scoped for a calendar event server, with each tool covering a distinct operation. There is no obvious bloat or missing basic operation at this size.
The surface covers listing calendars and events plus event create/update/delete and bulk color operations, so the core lifecycle is present. Gaps include no get_event, no calendar CRUD, and thin support for recurring-event creation details, though agents can partly work around these via list_events.