ryaker/outlook-mcp: an Outlook, OneDrive and Power Automate server for Claude, built on your own Azure app
MCP server for Claude to access Outlook data via Microsoft Graph API
At a glance
- What is it?
- ryaker/outlook-mcp is a JavaScript MCP server, published under the package name m365-mcp, that gives Claude 28 tools over Microsoft Graph and the Flow API. It works only after you register your own Azure app, and its last push was on 2026-03-30.
- Who is it for?
- Choose this server if you want Claude Desktop to read and send Outlook mail, manage OneDrive files and trigger manual Power Automate flows, and you are willing to register an Azure app and keep a token file on disk. Skip it for unattended use, flows that are not solution-aware, or any setup that needs recent maintenance, since the last push is from March 2026 and there are no releases.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Activity is slowing. The repository last received commits 7 months ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- ryaker/outlook-mcp456 ★ · +22
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| ryaker/outlook-mcp | 434 | 456 |
22 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Twenty-eight tools across Outlook, OneDrive and Power Automate, plus an authenticate step
The server is named M365 Assistant in its README and registers itself as m365-assistant in the Claude Desktop config. It connects Claude with Microsoft 365 through the Microsoft Graph API and, for flows, the Power Automate API. The tool tables list 15 Outlook tools, 8 OneDrive tools, and 5 Power Automate tools.
On the Outlook side the email tools are list-emails, search-emails, read-email, send-email, and mark-as-read. Calendar tools are list-events, create-event, accept-event, decline-event, and delete-event. Folder and rule tools are list-folders, create-folder, move-emails, list-rules, and create-rule. OneDrive has onedrive-list, onedrive-search, onedrive-download, onedrive-upload, onedrive-upload-large, onedrive-share, onedrive-create-folder, and onedrive-delete. Power Automate has flow-list-environments, flow-list, flow-run, flow-list-runs, and flow-toggle.
The scope is wide, and several of these tools change data: send-email sends real mail, delete-event removes calendar entries, onedrive-delete removes files or folders, and flow-toggle enables or disables a flow. An assistant given all of them can do damage that a read-only mail connector cannot, so decide how much of that you want Claude to reach before you connect a work account.
You must register your own Azure app, and the secret you copy is the VALUE, not the ID
There is no hosted sign-in. Every user creates an app registration in the Azure Portal, names it M365 MCP Server, picks the account type that allows any organizational directory and personal Microsoft accounts, and sets the redirect URI to Web with `http://localhost:3333/auth/callback`. The Application (client) ID goes into the environment file.
Delegated Microsoft Graph permissions to add are offline_access, User.Read, Mail.Read, Mail.ReadWrite, Mail.Send, Calendars.Read, Calendars.ReadWrite, Files.Read, and Files.ReadWrite. Then create a client secret under Certificates and secrets and copy the VALUE. The README repeats this warning three times because using the Secret ID produces the error AADSTS7000215, listed as Invalid client secret.
Two consequences follow. A work tenant with restricted app registration will block you until an administrator allows it, and the secret has an expiration you chose when you created it, after which the server stops authenticating. Neither is handled by the server; both are Azure settings you own.
Two sets of variable names: MS_ prefixes in .env, OUTLOOK_ prefixes in the Claude Desktop config
Setup copies the example file and edits it.
cp .env.example .envThe file holds four values.
# Get these values from Azure Portal > App Registrations > Your App
MS_CLIENT_ID=your-application-client-id-here
MS_CLIENT_SECRET=your-client-secret-VALUE-here
MS_TENANT_ID=your-tenant-id-here
USE_TEST_MODE=falseThe Claude Desktop entry uses different names for the same credentials.
{
"mcpServers": {
"m365-assistant": {
"command": "node",
"args": ["/path/to/outlook-mcp/index.js"],
"env": {
"USE_TEST_MODE": "false",
"OUTLOOK_CLIENT_ID": "your-client-id",
"OUTLOOK_CLIENT_SECRET": "your-client-secret"
}
}
}
}The notes say to use MS_CLIENT_ID and MS_CLIENT_SECRET in .env, but OUTLOOK_CLIENT_ID and OUTLOOK_CLIENT_SECRET in the Claude Desktop config. Mixing them up is an easy way to get authentication failures. Setting MS_TENANT_ID is advised for single-tenant apps to avoid /common endpoint errors, and the sample Claude Desktop env block has no tenant variable, so confirm how a single-tenant app behaves when Claude starts the process.
Sign-in needs a local auth server on port 3333 and leaves a token file in your home directory
Authentication is a separate process from the MCP server. You run `npm run auth-server`, then use the authenticate tool inside Claude, visit the URL it provides, and sign in. Tokens are saved to `~/.outlook-mcp-tokens.json`. The entry point for that process is outlook-auth-server.js, which package.json also exposes as the m365-mcp-auth binary, while the main server binary is m365-mcp.
The auth server listens on port 3333, matching the redirect URI you registered. If something else holds the port, the README gives `npx kill-port 3333` followed by `npm run auth-server`. If Claude reports that authentication is required, the fix is to delete the token file and sign in again.
The cost of this design is that a refresh token for your mailbox, calendar and files sits in a file in your home directory. Anyone or anything that can read that file can act as you within the granted scopes. Put the home directory under disk encryption, and delete the file when you stop using the server. The client secret has the same exposure in two more places: the .env file next to the code, and the env block of the Claude Desktop config, where it sits in plain text. Keep .env out of any repository you push, and remember that the secret expires on the date you picked in Azure, so a server that worked last month can start failing for that reason alone. The token manager module in auth/ handles storage and refresh for both Graph and Flow, per its comment in the directory listing.
Power Automate only reaches solution-aware flows with manual triggers
Flows use a separate token. The README says Power Automate requires a token with the Flow API scope and tells you to configure additional Azure AD permissions for the `https://service.flow.microsoft.com//.default` scope. The Graph permission list above does not cover it, so a user who stops after the Graph setup will have Outlook and OneDrive working and flows not working.
The listed limitations are exact. Only solution-aware flows are accessible. Only manual trigger flows can be run via API. Most operations require an environment ID, which is why flow-list-environments comes first in the tool table.
The consequence for planning: flows that start from an email arrival, a schedule or a webhook cannot be started by flow-run, and flows that live outside a solution will not appear in the list. flow-list-runs can show run history and flow-toggle can enable or disable a flow, but the server does not widen what the Flow API exposes. Check your most important flow against those three conditions before promising anyone that Claude can run it.
Power Automate is also the part the README marks as optional. The Quick Start and the Graph permission list work without it, and the Features line describes Flow API access as an addition to the Graph authentication. If you only want mail and files, skip the Flow scope entirely, which keeps the app registration smaller and the token file less powerful. If you do add it, remember that the environment ID is something you must find in your own Power Platform tenant and pass along with most requests, so Claude can only call flow-list after it has been given or has discovered an environment through flow-list-environments.
Upload tools split at 4 MB, and test mode replaces every Graph call with mock data
OneDrive upload is two tools, not one. onedrive-upload handles a small file under 4MB, and onedrive-upload-large does a chunked upload for anything over 4MB. A model that picks the wrong one for a large file will hit a size problem, so spell out the file size in your prompt or tell Claude which tool to use. onedrive-download returns a download URL rather than the file content, and onedrive-share creates a sharing link, which means files you share this way become reachable by whoever receives the link.
Test mode is built in. Setting USE_TEST_MODE to true, or running `npm run test-mode`, starts the server with simulated responses, so you can check that Claude sees the tools without making real Graph calls. `npm run inspect` runs the MCP Inspector against index.js, and `npm test` runs Jest. Dependencies are small: @modelcontextprotocol/sdk at ^1.27.1 and dotenv at ^16.5.0, with the Inspector, Jest and supertest as development dependencies. The engines field asks for Node.js 14.0.0 or higher.
Use test mode before you connect a real mailbox. It is the only way described to see what the tools return without risking a sent email or a deleted file.
Version 2.0.0 with no releases, a last push in March 2026, and personal scripts in the root
package.json names the project m365-mcp at version 2.0.0, while the repository is called outlook-mcp and the GitHub license field shows unknown. The package.json declares MIT as the license, so confirm the terms yourself before redistributing. The repository has no GitHub releases, so there is nothing to pin except a commit. The last push was on 2026-03-30, more than seven months ago, so do not assume that Microsoft Graph or Flow API changes are being tracked.
The layout is modular: auth, calendar, email, folder, onedrive, power-automate, rules, and utils directories under an index.js entry point and a config.js. The root also contains files that look like one person's tooling rather than product code: backup-logs.sh, move-github-emails.js, create-notifications-rule.js, find-folder-ids.js, test-direct.sh, test-pagination.js, and debug-env.js. Read any script before running it, since several of them presumably act on a real mailbox. A CLAUDE.md file is also present for working on the code with Claude.
Editorial conclusion
Choose this server if you want Claude Desktop to read and send Outlook mail, manage OneDrive files and trigger manual Power Automate flows, and you are willing to register an Azure app and keep a token file on disk. Skip it for unattended use, flows that are not solution-aware, or any setup that needs recent maintenance, since the last push is from March 2026 and there are no releases.
Frequently asked questions
Is there an MCP for Microsoft 365, such as ryaker/outlook-mcp?
ryaker/outlook-mcp connects Claude with Outlook, OneDrive and Power Automate through the Microsoft Graph API and the Power Automate API. It lists 28 tools across those three services.
How do I use the ryaker/outlook-mcp Outlook MCP server?
Run npm install, register an Azure app, copy .env.example to .env, add the server to the Claude Desktop config, start npm run auth-server, then use the authenticate tool in Claude.
What is the ryaker/outlook-mcp server?
It is a JavaScript MCP server published as m365-mcp version 2.0.0. It lets Claude list, search, read and send email, manage calendar events, work with OneDrive files, and trigger manual Power Automate flows.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/ryaker-outlook-mcp)Star history chart for your README
[](https://hysenlabs.com/projects/ryaker-outlook-mcp)Was this useful?