Office 365 Email MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Office 365 Email MCP Send an email to alice@company.com saying 'Meeting at 3pm'."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Office 365 Email MCP
An MCP server that lets an AI agent send email through Microsoft 365 / Office 365 using the OAuth2 client-credentials (app-only) flow and the Microsoft Graph API.
No interactive login at runtime — register an app once, grant it Mail.Send, and the server sends mail headlessly. Ideal for automation, notifications, and agent workflows.
Features
office365_send_email— send plain-text or HTML email, with CC/BCC and local file attachments.office365_test_connection— verify your OAuth2 config by acquiring a token (sends nothing).App-only auth (no user sign-in), tokens cached and refreshed automatically by MSAL.
Clear, actionable error messages for the common auth/permission/mailbox mistakes.
Related MCP server: mcp-outlook-mail
How it works
agent → MCP tool → MSAL (client credentials) → Entra ID → access token
→ POST https://graph.microsoft.com/v1.0/users/{sender}/sendMailPrerequisites
Python 3.10+
A Microsoft 365 tenant where you can register an app (or an admin who can).
A licensed mailbox to send from.
1. Register the app in Microsoft Entra ID
Go to Entra admin center → Identity → Applications → App registrations → New registration.
Name it (e.g.
office365-email-mcp), leave redirect URI blank, Register.Copy the Application (client) ID and Directory (tenant) ID from the Overview page.
Certificates & secrets → New client secret → copy the secret Value (shown once).
API permissions → Add a permission → Microsoft Graph → Application permissions →
Mail.Send→ Add.Click Grant admin consent for your tenant. (Requires an admin; the green check must appear.)
Scope it down (recommended).
Mail.Send(Application) lets the app send as any mailbox in the tenant. Restrict it to specific mailboxes with an Application Access Policy in Exchange Online:New-ApplicationAccessPolicy -AppId <CLIENT_ID> ` -PolicyScopeGroupId mcp-senders@yourdomain.com ` -AccessRight RestrictAccess ` -Description "Restrict office365-email-mcp to the mcp-senders group"
2. Install
# from a clone of this repo
pip install .
# or run without installing, using uv
uvx --from . office365-email-mcp3. Configure
Set these environment variables (see .env.example):
Variable | Required | Description |
| yes | Directory (tenant) ID |
| yes | Application (client) ID |
| yes | Client secret value |
| no | Default sender mailbox (overridable per call) |
4. Add to your MCP client
Claude Desktop / Claude Code (claude_desktop_config.json or .mcp.json):
{
"mcpServers": {
"office365-email": {
"command": "office365-email-mcp",
"env": {
"O365_TENANT_ID": "00000000-0000-0000-0000-000000000000",
"O365_CLIENT_ID": "00000000-0000-0000-0000-000000000000",
"O365_CLIENT_SECRET": "your-secret-value",
"O365_SENDER": "noreply@yourdomain.com"
}
}
}
}If you didn't pip install, use "command": "uvx" with "args": ["--from", "/path/to/repo", "office365-email-mcp"].
Tools
office365_send_email
Parameter | Type | Required | Notes |
| string[] | yes | Primary recipients |
| string | yes | |
| string | yes | Plain text or HTML |
| bool | no | Treat |
| string[] | no | |
| string | no | Overrides |
| string[] | no | Local file paths, < ~3 MB total |
| bool | no | Default true |
office365_test_connection
No parameters. Acquires a token and reports success/failure — run this first when troubleshooting.
Troubleshooting
Error | Fix |
| Client secret expired or wrong tenant/client ID. |
| Missing |
|
|
| The sender isn't in the allowed group from your access policy. |
Security notes
The client secret is a credential — keep it out of source control (
.envis gitignored). Rotate it periodically.Prefer an Application Access Policy so the app can only send as intended mailboxes.
Attachments over ~3 MB exceed Graph's single-request
sendMaillimit; share a link instead.
License
Available Tools
2 toolsoffice365_send_emailA
Send an email through Microsoft 365 via the Microsoft Graph API.
Uses the app-only (client-credentials) OAuth2 flow, so no user is signed in;
mail is sent from the mailbox given by sender or the O365_SENDER env var.
Supports plain-text or HTML bodies, CC/BCC, and local file attachments.
Args: params (SendEmailInput): Validated parameters containing: - to (list[str]): Primary recipient addresses (required). - subject (str): Subject line (required). - body (str): Body content, plain text or HTML (required). - is_html (bool): Treat body as HTML when true (default False). - cc (Optional[list[str]]): CC recipients. - bcc (Optional[list[str]]): BCC recipients. - sender (Optional[str]): From mailbox; overrides O365_SENDER. - attachments (Optional[list[str]]): Local file paths (<~3 MB total). - save_to_sent_items (bool): Keep a Sent Items copy (default True).
Returns: str: A human-readable confirmation, e.g. "Email sent from finance@contoso.com to 2 recipient(s): 'Subject'." On failure, a string beginning with "Error: " describing the problem and how to fix it (auth, permissions, mailbox, rate limits, etc.).
Examples: - "Email the Q3 report to alice@contoso.com" -> to=['alice@contoso.com'], subject='Q3 report', body='...', attachments=['/path/q3.pdf']. - Don't use to read or search mail; this tool only sends.
Inputs: params (required). Returns: result
office365_test_connectionARead-onlyIdempotent
Verify OAuth2 configuration by acquiring an app-only Graph token.
Performs no email send and reads no data. It only checks that the O365_TENANT_ID / O365_CLIENT_ID / O365_CLIENT_SECRET environment variables are present and valid enough to obtain an access token from Microsoft Entra ID. Use this first when diagnosing setup problems.
Returns: str: "OK: ..." on success (token acquired), including whether a default O365_SENDER is configured; otherwise a string beginning with "Error: " explaining what is misconfigured.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools serve entirely distinct purposes: one sends emails, the other verifies OAuth2 connectivity. There is no overlap or ambiguity.
Both tools follow a consistent 'office365_verb_noun' pattern (send_email, test_connection), with no mixing of conventions.
With only two tools, the server is extremely focused on sending emails and testing authentication. While this is appropriate for a minimal integration, it feels slightly under-scoped for a full Office 365 Email MCP.
The server only covers sending emails and connection testing, missing essential email operations like reading, searching, or managing folders. This is a significant gap for a service branded as 'Email MCP'.
Maintenance
Related MCP Connectors
Let AI agents send email from your own Gmail, Microsoft 365 or SMTP inbox, with guardrails.
Manage Microsoft 365 email, calendar, contacts and inbox rules via the Graph API with OAuth 2.0.
Email, calendar and contacts for AI agents: Gmail, Microsoft 365 and IMAP accounts behind one API.
Send email, manage domains, templates, webhooks and broadcasts from your AI agent.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables sending emails through Microsoft Outlook using the Microsoft Graph API. Provides the missing send-email capability for Agent Builder's Outlook connector with support for both delegated and app-only authentication flows.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with Microsoft 365 Outlook Mail, allowing email operations via natural language.314 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Microsoft Outlook emails through the Microsoft Graph API, supporting operations like listing, reading, sending, and moving emails.MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to send or draft email as the signed-in user through Microsoft Graph, including multiple recipients, HTML or plain-text bodies, and file attachments. Uses delegated least-privilege PKCE authentication so messages can be staged as drafts for approval or sent directly.MIT