claude.ai Gmail MCP regression: create_draft missing threadId parameter

Also experiencing this. Used to work fine.

I'm using the Claude Code official Gmail connector (v1.0.0: https://gmailmcp.googleapis.com/mcp/v1) which is apparently published by Google but has no online docs. Unclear if the connector is actually maintained by Anthropic vs. Google.

This makes basic gmail automation useless since one of the core email automation use-cases is preparing a threaded draft reply.

Understood that this is considered outside Claude Code's scope since the Gmail connector appears to be Google-maintained (gmailmcp.googleapis.com). That said, a few things would be helpful:

1. Where should this be reported? There are no public docs or issue tracker for the Gmail MCP connector. If Anthropic has a relationship with Google on this integration, can you help route this or confirm the right place to file?

1. Is there a known workaround? Without threadId, every draft lands as a standalone new email rather than a threaded reply — which breaks the primary use case for Gmail MCP in daily email workflows. If there's a way to achieve threading with the current tool schema, I'd love to know.

Thanks for the context.

I am having the same error. Any workaround???

Same issue, this completely broke our CX automation. SOS

I just found this issue while searching for solutions. It's also impacting our built integrations, any suggestions?

Hitting this same issue. Running an automated inbox responder (scheduled task) that drafts replies to customer emails — worked fine until around April 9-10, then all drafts started landing as standalone emails instead of threaded replies. Confirmed the threadId parameter is gone from the current create_draft schema. The workaround of matching on Re: [subject] does not fix it — drafts still appear outside the thread in Gmail UI. Please escalate to Google.

I just found this issue while searching for solutions. It's also impacting our built integrations, any suggestions?

Have you find any workaround for this?

Any news from this????? This has literally broke my day-to-day operations...

Any help would be greatly appreciated.

+1 for having the same problem.

+1 for having this same problem too. This glitch added 3+ hours of manual work each week to my plate (pissed!) starting April 9th 2026. So frustrating. Please let me know if anyone finds a workaround or knows of a way to facilitate a faster push to get this fixed.

+1 Is there a google forum for their MCP if this isn't the right place?

+1 ... are we going to need to self-host a Gmail MCP?

Looks like we're gonna have to start hosting our own Gmail MCP. I assume this was strategic by Google to limit the functionality here into their own AI suite. GREAT!

Same here - this is holding us back from nicely automting our workflows in Apache Airflow. It would be great if it is fixed.

+1 Broke my entire reason for running Claude, haha. CX and sales scheduled email replies are a total mess now, not threaded. Does anyone offer a hosted GMAIL MCP option? I dont have the experience to roll my own.

We now have documentation from Google on this MCP here:
https://developers.google.com/workspace/gmail/api/reference/mcp/tools_list/create_draft#input-schema

I've opened an issue with Google here. ⚠️ Please +1 at this link. ⚠️

We now have documentation from Google on this MCP here: https://developers.google.com/workspace/gmail/api/reference/mcp/tools_list/create_draft#input-schema I've opened an issue with Google here. Please +1 at this link.

Thank you! Just +1'd

Changed to codex + gpt 5.5 - Not having the problem anymore, replying now in every single thread.

I switched to a hosted MCP solution, everything is working again by using this service and removing the built in Gmail connector: https://workspacemcp.com/workspace-mcp-cloud You can also deploy it yourself, but I don't have that skill set, so I'm happy to pay for the hosted version.

Has there been any update on this since?

Has there been any update on this since?

I've been researching this extensively. The user above (ck-54388) is right that Workspace MCP (https://workspacemcp.com/) is a viable workaround. I've confirmed it also likely fixes the thread truncation issue where Anthropic's built-in connector drops 30-60% of messages on longer threads.

However, there's one gap that matters for my workflow: their draft_gmail_message tool does NOT support thread_id, so drafts still land as standalone emails. Their send_gmail_message tool does support thread_id, so if you're sending directly without a review step, you're fine. But if you push to drafts for review before sending (which I do dozens of times a day), the threading problem persists.

The fix should be small since the threading logic already exists in their send tool. I've already opened an issue on their repo (https://github.com/taylorwilsdon/google_workspace_mcp) requesting thread_id be added to draft_gmail_message. If anyone else needs this, piling on that issue would help.

Planning to set up the Workspace MCP cloud plan this weekend. Happy to report back on whether it resolves both the threading and truncation issues once I'm up and running.

As a quick note, I am having no problem with Claude threading my drafts now with that cloud service despite them not having threadID. That was my one and only issue and this solved it.

> Has there been any update on this since? I've been researching this extensively. The user above (ck-54388) is right that Workspace MCP (https://workspacemcp.com/) is a viable workaround. I've confirmed it also likely fixes the thread truncation issue where Anthropic's built-in connector drops 30-60% of messages on longer threads. However, there's one gap that matters for my workflow: their draft_gmail_message tool does NOT support thread_id, so drafts still land as standalone emails. Their send_gmail_message tool does support thread_id, so if you're sending directly without a review step, you're fine. But if you push to drafts for review before sending (which I do dozens of times a day), the threading problem persists. The fix should be small since the threading logic already exists in their send tool. I've already opened an issue on their repo (https://github.com/taylorwilsdon/google_workspace_mcp) requesting thread_id be added to draft_gmail_message. If anyone else needs this, piling on that issue would help. Planning to set up the Workspace MCP cloud plan this weekend. Happy to report back on whether it resolves both the threading and truncation issues once I'm up and running.

As a quick note, I am having no problem with Claude threading my drafts now with that cloud service despite them not having threadID. That was my one and only issue and this solved it. > > Has there been any update on this since? > > > I've been researching this extensively. The user above (ck-54388) is right that Workspace MCP (https://workspacemcp.com/) is a viable workaround. I've confirmed it also likely fixes the thread truncation issue where Anthropic's built-in connector drops 30-60% of messages on longer threads. > However, there's one gap that matters for my workflow: their draft_gmail_message tool does NOT support thread_id, so drafts still land as standalone emails. Their send_gmail_message tool does support thread_id, so if you're sending directly without a review step, you're fine. But if you push to drafts for review before sending (which I do dozens of times a day), the threading problem persists. > The fix should be small since the threading logic already exists in their send tool. I've already opened an issue on their repo (https://github.com/taylorwilsdon/google_workspace_mcp) requesting thread_id be added to draft_gmail_message. If anyone else needs this, piling on that issue would help. > Planning to set up the Workspace MCP cloud plan this weekend. Happy to report back on whether it resolves both the threading and truncation issues once I'm up and running.

Really appreciate you helping find a workaround. Curious if you ran into the same issue I had on top of the threading problem. The old connector was also capping thread history at about 5 emails, so Claude had no idea there were more messages to read and reference. Based on my research, the hosted solution should fix that too.

But back to the original issue. You're saying for $10/month you can have Claude compose a draft, tie it to the correct thread, and have it land in your Gmail drafts folder ready to review and send?

The workaround I am using now for Apache Airfow tooling we recently published (and will soon be likely something we officialy relase in ASF) which uses Google API / oauth to post Drafts:

https://github.com/apache/airflow-steward/blob/main/tools/gmail/draft-backends.md

It's been entirely created by Claude when I asked it - including the onboarding/configuration steps.

Also having this problem! Just sent an email from the Drafts folder to someone thinking it would auto append to the existing email thread, after drafting in Claude and sending to GMail via the connector -_-

Also having this problem! Just sent an email from the Drafts folder to someone thinking it would auto append to the existing email thread, after drafting in Claude and sending to GMail via the connector -_-

Pony up $10 p/month for the solutions mentioned above, and you'll be back on track. Took 2 minutes to implement and has been working as it used to like a charm.

I think even if the Gmail MPC connector comes back online, there will be other issues such as I've mentioned where the API for some reason can't pull back 100% of longer email threads where as this hosted solution I think is built in a way that also solves that problem. I'm likely to be a long-term subscriber as this hosted version has a level of depth that the other connectors into G-Suite don't offer.

I think this is fixed, the MCP now supports replyToMessageId @potiuk @kirkdebaets

<img width="942" height="374" alt="Image" src="https://github.com/user-attachments/assets/e509822f-38bd-4427-8d92-4148ed2df5b9" />

OOOOO coooll ! will try it :)

works! Thank you @johngroves !