SM

shayanline/msoutlook-mcp

Browser automation

このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る

8 stars 5 forks 品質 81 トレンド 30MIT

MCP server for Microsoft Outlook Web. No app registration required, uses your existing Outlook session.

概要

MCP server for Microsoft Outlook Web. No app registration required. Give any MCP client (Claude, Cursor, Devin, ...) read and write access to your Outlook mail, calendar, contacts, and the org directory. It works by reusing your existing Outlook Web session, the same way @shayanline/msteams-mcp reuses the Teams web session: you sign in once in a browser, then tokens are cached and refreshed automatically. Most Outlook MCP servers make you register an Azure AD application, grant admin consent, and manage client secrets. This one needs none of that. It reuses Outlook Web's own first party client ID, so your access is exactly what your account already has, and nothing leaves your own machine. - No Azure app registration, no admin consent, no client secrets. Sign in once in a browser; tokens are cached encrypted and refreshed silently after that. - across mail, calendar, contacts, people, the org directory, and your own account settings.

README

以下は原文 README の抜粋です。原文を見る。

msoutlook-mcp

MCP server for Microsoft Outlook Web. No app registration required.

Give any MCP client (Claude, Cursor, Devin, …) read and write access to your Outlook mail, calendar, contacts, and the org directory. It works by reusing your existing Outlook Web session, the same way @shayanline/msteams-mcp reuses the Teams web session: you sign in once in a browser, then tokens are cached and refreshed automatically.

Why

Most Outlook MCP servers make you register an Azure AD application, grant admin consent, and manage client secrets. This one needs none of that. It reuses Outlook Web’s own first party client ID, so your access is exactly what your account already has, and nothing leaves your own machine.

Highlights

  • Zero setup auth. No Azure app registration, no admin consent, no client secrets. Sign in once in a browser; tokens are cached encrypted and refreshed silently after that.
  • Over 50 tools across mail, calendar, contacts, people, the org directory, and your own account settings.
  • Safe by default. Email bodies are sent as HTML so line breaks always render, and the draft tools let you compose and review before anything is sent.
  • Scheduling and availability. Read free/busy, find meeting times across attendees, and check who is out of office.
  • Cross platform. macOS, Linux, and Windows, with automatic browser detection.

How it works

Microsoft Outlook Web (OWA) uses MSAL to store OAuth tokens in localStorage. This server:

  1. Opens a browser to outlook.office.com via Playwright
  2. Extracts the MSAL token cache from localStorage, using OWA’s own first party client ID (9199bf20-a13f-4107-85dc-02114787ef48)
  3. Caches the access token, refresh token, and session state in ~/.msoutlook-mcp-server/ (AES-256-GCM encrypted)
  4. Refreshes tokens automatically using the refresh token (HTTP, no browser) or a headless browser as fallback

No Azure app registration. No admin consent. No client secrets. Your access is limited to what your account can already do.

Quick start

The top-level key depends on your client. Most clients (Claude Desktop, Cursor, Windsurf) use mcpServers, while VS Code’s .vscode/mcp.json uses servers. Copy the matching block below.

Claude Desktop, Cursor, Windsurf (mcpServers):

{
  "mcpServers": {
    "outlook": {
      "command": "npx",
      "args": ["-y", "msoutlook-mcp@latest"]
    }
  }
}

VS Code (.vscode/mcp.json, uses servers):

{
  "servers": {
    "outlook": {
      "command": "npx",
GitHub で README 全文を見る

インストール

npx -y msoutlook-mcp@latest
MCP 初心者?mcpskill.org のガイドから始めましょう →

設定

{ "mcpServers": { "outlook": { "command": "npx", "args": ["-y", "msoutlook-mcp@latest"] } } }