Appreciate your patience, @Hessan Haiderzada !
Right now, this is supported for sequence follow-up email steps in API v3. You just need to send the variant with "subject": null (not an empty string). That's the intended way to create a threaded follow-up. The first email in the sequence still needs a subject, though.
For MCP, it depends on whether the underlying sequence tool has been updated to the same v3 contract. Since MCP uses the v3 service layer, it should support this as long as the tool passes null through. If it's still being rejected, that's likely a tool validation mismatch rather than a product limitation.
So the key distinction is: subject: null is valid for follow-up emails, but not for the first email in a sequence, since that one needs a subject to start the thread.