Google Calendar MCP: Support `colorId` on event create/update

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

The official Google Calendar MCP connector no longer supports colorId on event create/update. The field is ignored and events are created with the calendar's default color.

This is a regression: colorId previously worked, and the color-coding system was proposed by Claude itself as part of a logging workflow. The regression directly breaks a feature Claude recommended and relied on.

Proposed Solution

Add colorId support (values 1–11) to both create_event and update_event in the official Google Calendar MCP connector, so colors can be set at creation time and updated on existing events.

Alternative Solutions

The only workaround is a Google Apps Script that applies colors retroactively using event.setColor(), but it fails if the Google Calendar MCP connector has been used recently in the same session due to rate limiting conflicts.

This issue was previously reported in #28919. It is closed as inactive but still unresolved.

Priority

High - Significant impact on productivity

Feature Category

MCP server integration

Use Case Example

I use Claude to log categorized daily activities to Google Calendar (e.g. Work, Rest, Creative Output), each mapped to a specific color. This color-coding system was designed and recommended by Claude itself. Every session now requires a manual Apps Script run to fix missing colors, but even that workaround is unreliable due to timeouts, so I have to plan these extra, unnecessary steps. colorId support at creation time would eliminate the problem entirely.

Additional Context

Community MCP servers already support colorId (e.g. takumi0706/google-calendar-mcp), demonstrating that implementation is straightforward. Parity with community servers in the official connector would be a low-lift, high-impact fix.