[FEATURE] Regression: built-in Google Calendar MCP lost colorId support in update_event (tool renamed from gcal_update_event)

Resolved 💬 2 comments Opened Apr 14, 2026 by wintvelt Closed Jun 25, 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

Summary

Between April 7 and April 14, 2026, the built-in Google Calendar MCP server (UUID 17b49cc7-1d4e-4f8f-98e5-562943944fda) had its event update tool renamed from gcal_update_event to update_event, and in the process lost support for the colorId parameter. Passing colorId now fails silently (event is updated, color is not).

Evidence

  • April 7, 2026 session: mcp__17b49cc7-...__gcal_update_event accepted colorId and correctly applied Sage/Peacock/Graphite colors to events on the user's content calendar.
  • April 14, 2026: same server UUID, tool is now mcp__17b49cc7-...__update_event, colorId parameter either rejected or silently ignored. Events stay on default color.
  • Related (stale/closed): #28919

Impact

Breaks automated content calendar color-coding workflows that rely on status-driven color updates (e.g. Airtable status → GCal color sync).

Proposed Solution

Request

  • Restore colorId support in update_event
  • Also support it in create_event for completeness
  • Document the tool rename in release notes

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

Use case example

I run a LinkedIn content calendar with Airtable as source of truth and Google Calendar as a visual overview. Each post has a status (Not started / In progress / Done), and the GCal event color should reflect that status:

  • Not started → Graphite (grey, colorId 8)
  • In progress → Peacock (blue, colorId 7)
  • Done → Sage (green, colorId 2)

My skill pipeline uses Claude to:

  1. Pull the next post from Airtable
  2. Flip status to "In progress" when I start drafting → update GCal event to Peacock via update_event with colorId: "7"
  3. Flip status to "Done" when the post is published → update GCal event to Sage via update_event with colorId: "2"

Until April 7 this worked end-to-end. After the tool rename to update_event, the color never changes and I have to set it by hand in the GCal UI every single time. The automation is effectively broken for any workflow that relies on visual status signaling in a shared calendar.

This pattern (status → color) is common

Additional Context

_No response_

View original on GitHub ↗

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