The MCP currently exposes calendar event search and creation via query_email_and_calendar and create_or_update_event, but there's no way to enumerate the distinct calendars connected to the account.
Use case: I have multiple calendars (work, family, personal). When asking the AI to plan my day or filter events by source, I need to be able to:
- See which calendars are connected (names + IDs + which account they belong to)
- Filter event queries to a specific calendar (e.g., "only show events on my work calendar")
- Specify which calendar to write a new event to (instead of always defaulting to primary)
Proposed tool:
list_calendars()
→ Returns: [
{ id, name, account_email, is_primary, is_writable, color, timezone },
...
]
Bonus additions that would unlock this further:
- Add a calendar_id filter parameter to event-query/list tools
- Add a calendar_id parameter to create_or_update_event
- Surface the calendar source in event-list responses (today, all events come back in one merged stream)
This would bring Superhuman MCP closer to feature parity with Google's native Calendar MCP, which already supports per-calendar enumeration and filtering
The MCP currently exposes calendar event search and creation via query_email_and_calendar and create_or_update_event, but there's no way to enumerate the distinct calendars connected to the account.
Use case: I have multiple calendars (work, family, personal). When asking the AI to plan my day or filter events by source, I need to be able to:
Proposed tool:
list_calendars()
→ Returns: [
{ id, name, account_email, is_primary, is_writable, color, timezone },
...
]
Bonus additions that would unlock this further:
This would bring Superhuman MCP closer to feature parity with Google's native Calendar MCP, which already supports per-calendar enumeration and filtering