claude-code - 💡(How to fix) Fix [FEATURE] Regression: built-in Google Calendar MCP lost colorId support in update_event (tool renamed from gcal_update_event) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48021Fetched 2026-04-15 06:35:36
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×2cross-referenced ×1

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).

Root Cause

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).

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • 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

extent analysis

TL;DR

The most likely fix is to restore support for the colorId parameter in the update_event tool.

Guidance

  • Verify that the colorId parameter is indeed being silently ignored by checking the event updates in Google Calendar after running the update_event tool.
  • Check the release notes for any documentation on the tool rename and potential changes to supported parameters.
  • Consider reaching out to the development team to request restoration of colorId support in update_event and addition of support in create_event.
  • In the meantime, explore alternative workflows that do not rely on automated color updates, such as manual color changes in the Google Calendar UI.

Example

No code snippet is provided as the issue does not include specific code examples.

Notes

The issue seems to be specific to the update_event tool and its lack of support for the colorId parameter after the tool rename. The proposed solution is to restore this support, but alternative solutions may be explored if this is not feasible.

Recommendation

Apply workaround: Until the colorId support is restored, consider using manual color changes in the Google Calendar UI or exploring alternative workflows that do not rely on automated color updates. This will allow users to continue using the content calendar with some manual intervention.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING