google-calendar

Scheduling conflict detection across multiple Google Calendar accounts is handled by merging events from a personal read-write account and a read-only school account, scanning time ranges for overlaps, and proposing solutions like rescheduling or cancelling to prevent double-booking.

You can create, update, and delete Google Calendar events using mcp__gws__ calendar APIs for the personal read-write account, while mcp__personal-tools__ handles read-only access for the school account, requiring explicit user confirmation before any write operation.

Merging calendars for a daily morning briefing involves reading events from both a personal read-write account and a read-only school account via MCP, combining the schedules, and presenting a unified view to show today's commitments.

Managing dual Google Calendar accounts requires default timezone handling set to America/New_York to ensure that event creation, conflict detection, and schedule merging are processed accurately across both accounts.

Finding free time slots for deep work across two Google accounts is done by querying merged schedules via MCP, detecting existing calendar events across both personal and school accounts, and proposing available time ranges that avoid conflicts.

Modifying a calendar event requires explicit user confirmation to prevent accidental creation, updates, or deletions on the personal Google account, ensuring safe event management when using the gws MCP interface for write operations.