outlook-mcp
An MCP server that gives the agent access to mail, calendar, OneDrive files and Power Automate flows through Microsoft Graph
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Reads and sends mail, changes calendar and files
- Handles a client secret and access tokens
- Can trigger Power Automate flows
Install
Manual install
git clone https://github.com/ryaker/outlook-mcp.git
cd outlook-mcp
npm installThen register an Azure app and set the environment variables.
This is third-party code. Review the repository files before installing.
What it does
outlook-mcp connects the agent to Microsoft 365 services through Microsoft Graph. It exposes mail tools: list, search, read, send, mark as read, plus folders and rules. For the calendar it can list, create, accept, decline and delete events. It also covers OneDrive with list, search, download, upload and share links, and it can trigger Power Automate flows and view their run history. The server runs locally and connects to Claude via MCP config, with access granted over OAuth.
Who it is for. For people on Microsoft 365 who want to hand mail, calendar and files to an agent.
Good fit when
- You want the agent to triage and send Outlook mail
- You need to work with calendar events and mail folders
- You need to fetch and share OneDrive files or run Power Automate flows
Not a fit when
- You have no Microsoft 365 account or Azure app registration
- You cannot trust the agent to send mail and act on work data
Example request
Show my latest Outlook emails and create a calendar event for tomorrow at 3 pmLimitations
You need a Microsoft 365 account and an Azure app registration with the right permissions and a client secret. The repository has no license file. Power Automate support is limited: only solution-aware, manual-trigger flows are reachable.
How to disable. Remove the server from the client's MCP config, delete the token file ~/.outlook-mcp-tokens.json and the repository folder.
MCP
- Transport
- stdio
- Authentication
- OAuth
| Environment variables | |
|---|---|
| OUTLOOK_CLIENT_ID required | Application client ID from the Azure app registration. |
| OUTLOOK_CLIENT_SECRET required, secret | The Azure app client secret value. |
| MS_TENANT_ID | Tenant ID for single-tenant apps. |
Security check
- Reads and sends mail, changes calendar and files
- Handles a client secret and access tokens
- Can trigger Power Automate flows
README in short
The README presents the server as a Microsoft 365 assistant over Microsoft Graph and Power Automate. It lists tools across three areas: Outlook mail and calendar, OneDrive files, and Power Automate flows. It walks through Azure app registration, the required permissions, the client secret, and the environment variables. It shows a Claude Desktop config that launches via node plus an OAuth sign-in. There is a test mode with mock data and a troubleshooting section.
FAQ
Which services are supported?
Outlook mail and calendar, OneDrive files and folders, and Power Automate.
How does sign-in work?
Through OAuth 2.0 with Microsoft Graph, and tokens are saved locally in a file in your home directory.
Related
A self-hosted knowledge base with block-level references and a built-in MCP server for connecting AI agents to your notes
A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more
Local search over Markdown notes, docs and meeting transcripts: keywords, semantic search and reranking, with an MCP server
A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI