A Microsoft 365 MCP server puts your work account — Outlook mail and calendar, OneDrive files, Excel, Teams chats and SharePoint — behind a set of tools an AI client can call over the Graph API. Ask Claude to triage your inbox, find a meeting slot, or pull a figure out of a spreadsheet. Here are the two practical routes in 2026.
Option A — community npx server (fastest)
The most-used path is the open-source @softeria/ms-365-mcp-server, which exposes 200+ Graph tools across Mail, Calendar, OneDrive, Excel, OneNote, To Do, Planner, Contacts, Search, Teams and SharePoint. Add it as a stdio server:
{
"mcpServers": {
"ms365": {
"command": "npx",
"args": ["-y", "@softeria/ms-365-mcp-server"]
}
}
}
Authenticate once with the device-code flow — run npx @softeria/ms-365-mcp-server --login and follow the prompt. By default you get personal-account features (mail, calendar, OneDrive); add the --org-mode flag to unlock work/school scopes like Teams and SharePoint. Restart the client and check Node 18+; see MCP config file location.
Option B — Microsoft's own agent path
If you're building inside Microsoft's stack rather than connecting an external client, Microsoft now ships first-party tooling: MCP support is generally available in declarative agents for Microsoft 365 Copilot, and Agent 365 MCP servers expose deterministic, auditable tools for Outlook, Teams, SharePoint and Dataverse to agents in Copilot Studio. That route suits IT-governed deployments where admins provision agents centrally; the npx server above suits an individual wiring Claude or Cursor to their own mailbox.
What you can ask
The everyday wins are triage and lookup: "summarise unread mail from this week," "find a 30-minute slot with the design team," "what changed in this SharePoint doc?" Because the server spans mail, calendar and files, it can chain context across them in a single request.
Scope it safely
Work email and Teams are among the most sensitive scopes you can grant an AI. Sign in with least privilege, stay in personal mode unless you genuinely need org features, and avoid granting send/modify until read-only has proven its value. Review the consent screen carefully and never share cached tokens. See MCP security best practices and MCP permission scoping patterns.
Going further
Compare with the Google stack via Gmail MCP setup and Google Calendar MCP setup, browse the communication category, or wire it into a product-manager loadout.