google-workspace: get_events should expose colorId field when detailed=true

Status Open
Maintainer reply None cached
Activity 0 comments · opened Aug 2, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Problem
The mcp__plugin_google-workspace_google-workspace__get_events tool with detailed=true returns attendees, description, location, and other event details, but doesn't expose the colorId field that exists in the Google Calendar API response.

Use Case
Calendar color IDs are used to categorize events (personal vs work, different projects, etc.). For automated status updates and activity summaries, I need to filter events by color to exclude certain categories (e.g., personal events marked with a specific color).
Currently, the only workaround is text-pattern matching on event titles/descriptions, which is fragile and unreliable.

Current Behavior
get_events(calendar_id="primary", detailed=true, ...)

Returns:

  • "Event Title" (Starts: 2026-07-31T12:00:00-07:00, Ends: ...)

Description: ...
Location: ...
Creator: <email>
Organizer: <email>
Attendees: ...
// colorId missing

Proposed Solution

Expected Behavior

Should include:

  • "Event Title" (Starts: 2026-07-31T12:00:00-07:00, Ends: ...)

Description: ...
Location: ...
Color ID: 10
Creator: <email>
...

API Reference
The Google Calendar API already provides this field in the Events resource
(https://developers.google.com/calendar/api/v3/reference/events#resource):

  • colorId: string - The color of the event (as an opaque identifier)

Impact
Without this field, there's no reliable programmatic way to filter calendar events by color category, which is a common use case for automating personal status updates and activity tracking.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

MCP server integration

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗