Google Calendar MCP Server
Related Servers
Alternatives to Google Calendar MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables Claude to manage Google Calendar events, schedules, and meetings through natural conversation. It supports viewing calendars, creating Google Meet events, and searching for upcoming activities using Nango for authentication.6-
- AlicenseNot gradedqualityDmaintenanceEnables Claude to interact with Google Calendar through OAuth authentication, allowing users to list events, create and manage meetings, update or delete calendar entries, and find available time slots using natural language.72MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to interact with Google Calendar through natural language, providing the ability to view, create, update, and delete calendar events with persistent OAuth2 authentication.11 npmMIT
- AlicenseAqualityCmaintenanceEnables Claude to read, create, update, and delete Google Calendar events directly through natural language.675 npmMIT
- FlicenseNot gradedqualityDmaintenanceAllows interaction with Google Calendar through Claude Desktop using the Model Context Protocol, enabling calendar event management and schedule analysis.2-
- AlicenseAqualityDmaintenanceIntegrates Google Calendar and Notion to enable Claude to manage your schedule, plan tasks, detect conflicts, and keep appointments and tasks synchronized.17GPL 2.0
TDQS
Scored across 6 tools
Most tools have distinct purposes, but there is some overlap between get_calendar_events, get_today_events, and get_upcoming_events, which could cause confusion about which to use for specific date ranges. However, their descriptions clarify their scopes (specific time bounds, today-only, next N days), helping to mitigate misselection.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., cancel_calendar_event, create_meet_event, get_all_calendars). This predictability makes it easy for agents to understand and use the toolset without confusion from mixed naming conventions.
With 6 tools, the count is reasonable for a calendar server, covering core operations like listing, creating, and canceling events. However, it feels slightly thin as it lacks update or delete operations for events (beyond cancel) and calendar management, which might limit agent workflows in more complex scenarios.
The toolset covers basic CRUD for events (create and cancel) and reading calendars/events, but there are notable gaps: no update_event tool to modify existing events, no delete_calendar or manage_calendar tools, and limited event query flexibility. This could cause agent failures when full lifecycle management is needed.