Detailed Analysis
Claude.ai's Gmail MCP (Model Context Protocol) connector has undergone a breaking change that stripped threaded draft functionality from its core toolset, leaving users unable to create contextually attached draft replies within existing Gmail conversations. The previous implementation featured a tool called `gmail_create_draft` with a `threadId` parameter that allowed Claude to generate draft replies directly inside the correct conversation thread, where they would appear ready for user review and sending. A recent update replaced this with a simpler `create_draft` tool that omits the `threadId` parameter entirely, causing every AI-generated draft to land as an orphaned, standalone message in the Drafts folder — disconnected from any conversation context. Multiple open GitHub issues in the `anthropics/claude-code` repository (including #45775, #50945, and #48681) confirm this is a widespread regression, not an isolated configuration problem, and none of these issues carry confirmed resolutions as of late April 2026.
The practical damage to email automation workflows is significant. The entire value proposition of integrating an AI assistant with Gmail via MCP rests on the ability to handle correspondence intelligently and in context — drafting replies that know which thread they belong to, which prior messages they're responding to, and which recipient they're addressing. Without `threadId` support, that context collapses. Users are left with the manual workaround of copying Claude-generated draft text and pasting it into a Gmail reply window themselves, a task that largely defeats the purpose of AI-assisted email management. Anthropic's own support documentation acknowledges that the Gmail connector is designed for drafting emails with context and managing threads, making the omission of `threadId` a direct contradiction of the connector's stated capabilities.
The regression also highlights a structural challenge in maintaining MCP connectors as living integrations rather than static tools. The Gmail API v1 has long supported `threadId` as a parameter for draft creation, meaning the capability exists at the API layer — its absence in the updated MCP tool reflects an oversight in the connector's implementation rather than a platform-level limitation. This kind of regression, where a capability silently disappears without announcement or deprecation notice, erodes trust in MCP as a reliable foundation for production workflows. Third-party providers such as MintMCP and Composio have stepped into the gap, offering alternative Gmail MCP servers with explicit `draft_reply` tooling and thread-aware operations, which suggests that the demand for this functionality is well understood across the ecosystem even if Anthropic's native connector has temporarily lost it.
Zooming out, this incident reflects a broader tension in the rapidly evolving MCP ecosystem: connectors are being iterated on quickly, and interface stability has not always kept pace with the speed of deployment. As organizations and power users build increasingly complex agentic workflows on top of tools like Claude's Gmail connector, even minor tool schema changes — dropping a single parameter — can cascade into broken automations, lost productivity, and eroded confidence in the underlying platform. The fact that the issue was noticed by the community within 48 hours and immediately generated multiple GitHub issue threads speaks to how deeply embedded these integrations have become in users' daily operations. Until Anthropic restores `threadId` support in its native Gmail MCP connector, affected users should treat third-party MCP alternatives or fully manual workarounds as the only reliable paths for threaded draft workflows.
Read original article →