What does the draft tool do that send-email didn't?

send-email creates and sends a message in one step. The draft tool decouples those: create writes to your Drafts folder, send fires later (sharing the same rate limit), and delete tidies up. In between you can update the draft as many times as you like, or use reply / reply-all / forward to seed it from an existing message.

Will reply-all auto-populate everyone correctly?

Yes — it pulls the original recipients via Microsoft Graph's createReplyAll endpoint, so To/Cc are filled from the source message and threading headers are preserved. You can still override recipients via the to/cc/bcc params before sending.

Does the recipient allowlist apply to drafts?

It applies to anything that ends up addressing a recipient — create, update, forward. The send action shares send-email's rate limit, so you can't drain quota by sending hundreds of drafts at once.

Outlook Assistant v3.6.0 — Email Drafts via Conversation

Highlights

Full draft lifecycle

create, update, send, delete, reply, reply-all, and forward — all through one tool, all backed by Microsoft Graph drafts API.

Reply and forward, properly

auto-populates To/Cc/Bcc and threading headers from the source message. comment param prepends a note. reply-all defaults to the right recipients.

Dry-run + recipient checks

preview the draft before saving. check-recipients flag validates with mail tips before the create call, so out-of-office or full mailboxes surface upfront.

Safety belts on by default

destructiveHint + openWorldHint annotations on send/delete actions. Rate-limited via OUTLOOK_MAX_DRAFT_PER_SESSION. Recipient allowlist applies to create, update, and forward.

What’s new in v3.6.0

I shipped the draft tool. Email drafts have been the obvious gap in Outlook Assistant since v3.0 — read, search, send, but no clean way to compose iteratively. Now your AI agent can do what you’d actually do in Outlook: stage a draft, leave it for a bit, come back, polish, send.

create / update / send / delete

Four actions covering the whole lifecycle. create writes to your Drafts folder and supports dryRun (preview without saving) and checkRecipients (run mail tips before the create call). update patches subject, body, recipients, or importance on an existing draft — useful when the agent has another go after seeing the result. send shares the rate limit with send-email so you can’t accidentally fire a hundred drafts. delete tidies up.

reply / reply-all / forward

These three are where it gets useful. reply auto-populates the recipient and pulls threading headers from the source message — the resulting draft slots back into the conversation thread. reply-all does the same with the full recipient list. forward seeds a forward draft you can edit before sending, with a comment parameter for a prepended note.

Safety belts

The destructive actions (send, delete) carry destructiveHint: true and openWorldHint: true so MCP clients prompt before firing. Create and update share the recipient allowlist with send-email — if you’ve configured OUTLOOK_ALLOWED_RECIPIENTS, the agent can’t draft a message to anyone outside it. Per-session rate limit via OUTLOOK_MAX_DRAFT_PER_SESSION.

This is one I needed for my own workflow — drafting a reply through Claude, walking away to think, coming back, and sending. It feels right.