# Draft a reply in the thread for the person to send

> Draft a reply in the thread for the person to send: 7 companies fully do it, 3 with a limit, 32 carry the tag. Every listing in Mailbox access with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/mailbox-access.draft-reply/
- Markdown: https://www.anchorterminal.com/niches/mailbox-access.draft-reply/index.md (~1,250 tokens)
- Slim: https://www.anchorterminal.com/niches/mailbox-access.draft-reply/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/mailbox-access.draft-reply/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 7 | 3 | 32 | 10 | 3 |

## What counts as done

A draft exists in the person's Drafts folder, threaded under the original (same thread ID, In-Reply-To and References set), with quoted recipients right, and nothing is sent.

How agents ask for it: draft a reply to this; prepare answers to this morning's emails; write a response I can review

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Aurinko Email API (Yoxel, Inc.)**: POST /v1/email/drafts takes inReplyTo and references, and /messages/{id}/reply exists, so a draft stays threaded; sending a draft is a separate drafts/{id}/send call.
- **email-agent-mcp (UseJunior)**: reply_to_email in draft-only mode and create_draft write a threaded reply draft without sending, checked by the live smoke script against a real Outlook mailbox; send_draft is a separate tool.
- **EmailEngine (Postal Systems OÜ, Narva mnt 5, 10117 Tallinn, Estonia, registry code 14971894)**: create_draft stores a reply in Drafts with a reference block to the stored message, from which EmailEngine derives the reply headers, sends nothing, and returns an ID; send_draft is a separate tool.
- **Fastmail API (JMAP) (Fastmail Pty Ltd, ACN 142 646 580, PO Box 234, Collins Street West, VIC 8007, Australia)**: Email/set creates a message in the Drafts mailbox with the $draft keyword and the caller's In-Reply-To and References headers, which the server uses for threading, and without the jmap:submission scope nothing can be sent.
- **Nylas Email API (Nylas, Inc.)**: POST /drafts takes reply_to_message_id so the draft is threaded under the original in the provider's Drafts folder, and sending a saved draft is a separate POST /drafts/{draft_id}.
- **Outlook Mail (Microsoft Graph) (Microsoft Corporation)**: createReply makes a reply draft to an existing message, addressed per replyTo, under Mail.ReadWrite alone, and sending it is a separate operation that needs Mail.Send.
- **Unipile (UNIPILE SAS)**: Create a draft takes account_id and reply_to, the Unipile or provider ID of the email being answered, and stores the draft without sending.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Gmail API (Google LLC)**: drafts.create takes a message with threadId, and the sending guide says In-Reply-To and References must be set by the caller to stay threaded, but the gmail.compose scope needed for drafts also sends mail; acc-01 and acc-23 show wrappers losing threading.
- **Himalaya (No legal entity found. Copyright Clément DOUIN (soywod))**: message reply --save builds a reply and stores it without sending, but the README doesn't say it sets In-Reply-To and References or keeps the provider thread ID, and sending an existing draft was missing until issue 787 closed on 14 October.
- **Zoho Mail API (Zoho Corporation Private Limited)**: Save draft with mode=draft takes inReplyTo and refHeader to keep the thread, and nothing is sent, but the caller must supply every earlier Message-ID itself, and the needed CREATE scope also sends.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **CloudPost (CloudPost (James Brooks))**: No docs; no draft tool or threading parameter is described on the site.

## What stops agents finishing

- draft tool lacks a thread parameter, so replies start new conversations
- no way to send a saved draft without resubmitting it
- a draft scope that also allows sending

## Around it

Before: mailbox-access.find-and-read. After: mailbox-access.send-as-user.

## Where this comes from

Weight 10 of 100 in Mailbox access: 3 of 36 counted mentions (acc-01, 22, 23); the buyer checks lean on drafting but accounts mostly describe reading

As data: https://www.anchorterminal.com/api/v1/use-cases/mailbox-access.draft-reply.json, or the MCP tool get_use_case with id mailbox-access.draft-reply. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
