Can Claude send emails? Gmail, Outlook and MCP explained

01Choose the connection before writing the workflow

Start with the mailbox you already use and the action you need. The table reflects documentation checked on 2026-10-18, not a delivery benchmark or a test of your account's permissions.

Ask Claude which connection it will use before a consequential action. A clear request names the source account, the recipient and whether the result should remain a draft. This makes the task easier to inspect, but a sentence in a prompt does not remove a tool's server-side permissions.

02What Gmail approval does and does not tell you

Anthropic documents approval before sending, replying and forwarding in the native Gmail connector. On Team and Enterprise, owners decide whether members may allow those actions without a fresh prompt^[1]. For a managed account, establish that setting with the owner instead of assuming the default still applies to your workflow.

Team and Enterprise also require an Owner or Primary Owner to enable the connectors before members can connect. If Google Workspace policy blocks the application, a Google administrator may need to approve Claude separately^[1].

For example, a coordinator might ask: “Find Northbridge Supplies' message about Thursday's delivery. Prepare a reply, show me the sender account and recipients, and do not send.” Review the proposed text and the action Claude intends to call. If your requirement is that the connection must never send, use a connection whose permissions enforce that boundary as well.

Forwarding deserves its own check. Issue #100177 is an open request from a user whose forward tool sent immediately rather than preparing a forward draft. The reported environment was Claude Desktop's Code tab^[4]. It is a useful warning to inspect the operation, not evidence that every Claude forwarding workflow is defective. When no forward-draft action is available, build the forward in Gmail yourself, particularly when it must carry the original files.

The Gmail help page also says the connector accesses attachment metadata rather than attachment contents^[1]. Seeing “delivery-note.pdf” is not proof that Claude read the document. Keep any proposed answer dependent on that file pending until its contents have been checked through an appropriate route.

03Microsoft 365 needs administrator-enabled write tools

Claude's Microsoft 365 integration is for work accounts tied to a Microsoft Entra tenant. Personal addresses at Outlook.com, Hotmail and Live are not accepted. Anthropic lists the connector across Claude plans, but an administrator must complete the tenant setup, and write tools require additional consent and enablement^[2].

A working search connection therefore does not prove send access. If Claude can find a thread but cannot send a reply, ask your administrator about the write-tool setup. You can inspect individual tool switches under Customize → Connectors → Microsoft 365 → Tool permissions, according to Anthropic's instructions^[2]. Repeating the request in a more forceful prompt does not supply a missing permission.

Attachment-based work needs a separate route today: Anthropic says the Microsoft 365 write tools cannot draft, forward or send email with attachments^[2]. One practical approach is to have Claude prepare the body and finish the message in Outlook. Recheck the recipient list and final content there before sending, especially if you edited the draft outside the conversation.

04Google's Gmail MCP is a different service

Google publishes its own Gmail MCP as a Developer Preview. The reference retrieved for this page includes create_draft, list_drafts, get_message and search_threads, but no send tool^[3]. That does not contradict Anthropic's Gmail documentation: the two services expose different integrations.

For a self-configured MCP connection, inspect the offered tools before promising an end-to-end send workflow. OAuth permissions and available tool actions answer different questions. A broadly worded permission can authorize an operation that your current client has no tool to perform. Our email MCP comparison distinguishes the official preview from native connectors and other services.

05Investigate an uncertain send before trying again

A routine completing successfully is weaker evidence than the actual mailbox outcome. In issue #97895, a user reports a scheduled Claude Code Routine that showed success even though its Gmail send operation did nothing^[5]. The report remains open; we did not reproduce it and do not treat it as proof that scheduled sends always fail.

Use a sequence that separates the possible outcomes:

1. Identify the action. Ask whether Claude saved a draft, obtained approval or invoked a send operation. Have it report the tool result rather than infer success from the overall task status.
2. Check the sending mailbox. Look in Sent for the intended recipient, subject and time. A draft with the same subject is not a sent record.
3. Inspect service evidence where available. A message identifier or provider status can help trace the attempt. Acceptance by a mail service does not show that the recipient read it.
4. Confirm receipt for a test you authorize. Use a destination you control, inspect its inbox and spam folder, and compare the message that actually arrived with the intended content.

Do not automatically repeat a send after a timeout. First establish whether the original attempt left the mailbox. If the outcome stays uncertain, decide explicitly whether to accept the risk of a duplicate. This is a recommended verification method; no email was sent to produce this article.

For unattended work, write down which evidence the workflow must preserve before you enable it. A report that names the account, action and returned result is more useful for troubleshooting than “all done”. It still needs to be checked against the service when delivery matters. Keep drafting and actual sending as separate acceptance checks in your own setup.

06Where Command Mail adds a different control layer

Command Mail is our product. It is optional if the built-in Gmail route already fits your needs. It is intended for work across several addresses and for connections where drafting, sending a reviewed version and sending independently should be separate permissions^[6].

An agent with mail:draft can save drafts; that permission does not send. With mail:send-approved, it can send the precise revision approved by a person. The executing code checks the revision and sender identity again, claims the approved draft before sending, and prevents automatic retries when the delivery outcome is uncertain^[7]. These checks do not guarantee delivery or provide a recall of a message already sent.

Independent sending requires mail:send and an originating mailbox on autonomy auto. Agents can send human-approved drafts on suggest and rules too, but not on read. New mailboxes start on auto, so check both the permission grant and the mailbox level explicitly^[6][7]. Other organizing and deletion behavior is covered in the permissions reference; do not infer a comprehensive read-only boundary from a prompt or a single scope name.

Mail forwarded into Command Mail is a copy. Changes there do not synchronize back into the original Gmail or Outlook mailbox, and receiving forwarded mail does not by itself make that address a valid sending identity. Free does not send; sending needs at least Pro and a send-capable address^[6][7]. If your goal is simply to operate inside one original Gmail mailbox, the native connector can be the shorter path.

Use Connect Gmail to Claude for setup, or Use multiple email accounts with an AI agent for the multi-address case. You can start free and connect an agent with the draft permissions you choose.

07Evidence and review date

As of 2026-10-18. We retrieved the manufacturer documentation, Google's tool reference and both issue states on that date. Command Mail's statements were also checked against executing code at commit d6ad1ce, including MCP registration, draft approval, sending and sender resolution. This article does not claim a live send test, a new-provider signup or a comparative delivery measurement.

Frequently asked questions

Sources

1. Anthropic: Use Google Workspace connectors support.claude.com, accessed October 18, 2026
2. Anthropic: Connect to Microsoft 365 support.claude.com, accessed October 18, 2026
3. Google: Gmail MCP reference, Developer Preview developers.google.com, accessed October 18, 2026
4. User report: request to prepare forwards as drafts github.com, accessed October 18, 2026
5. User report: a Routine reports success without sending github.com, accessed October 18, 2026
6. Command Mail: plans and agent permissions commandmail.app, accessed October 18, 2026
7. Command Mail: permissions and autonomy, checked against code commandmail.app, accessed October 18, 2026