Google Calendar MCP: Support colorId on event create/update

Resolved 💬 2 comments Opened Feb 26, 2026 by jackkotev Closed Mar 27, 2026

Feature Request

The built-in Google Calendar MCP connector in Claude Cowork does not support the colorId field when creating or updating events. The field is silently ignored on both gcal_create_event and gcal_update_event calls.

Use Case

I set up a scheduled task that pulls Jira issues and creates time-blocking events on Google Calendar. I want these events to be visually distinct (e.g. Tomato / colorId: 11) so I can immediately tell them apart from meetings and other events.

Currently the only workaround is to manually change each event's color in the Google Calendar UI, which defeats the purpose of automation.

Expected Behavior

The colorId field (values 1–11) should be supported in:

  • gcal_create_event — set color at creation time
  • gcal_update_event — change color on existing events

Current Behavior

Passing "colorId": "11" in the event object is silently ignored. Events are created with the calendar's default color.

Additional Context

Community MCP servers (e.g. takumi0706/google-calendar-mcp) already support this field. It would be great to have parity in the official Cowork connector.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗