Microsoft Outlook の個人アカウントを Microsoft Graph API 経由で MCP サーバー。

個人Microsoftアカウントのみ — @outlook.com, [@hotmail.com], [@live.com]. ワーク/スクールのアカウント(Entra ID)はサポートされていません。サーバーは個人アカウント上に構築およびテストされます。 ツールを作業アカウントに振る舞い、個人アカウントの見方を変えずに、歓迎する修正。

**免責事項:**独立したオープンソースプロジェクト。 Microsoft Corporation が提携、推奨、またはサポートしていない。 「Outlook」および「Microsoft Graph」は、Microsoftの商標です。

お問い合わせ

誰がこれなのか

こんな感じです:

• 独自の赤外線にOutlookを配線するエージェントビルダー(OpenClaw、Claudeコード、Cursor、カスタムMCPホスト)とタイプされたツールの表面を望む - ないあなたが解析しなければならない
• マイクロソフトアカウント**(Outlook.com / Hotmail / Live)で構築し、完全な制御をしたい:BYO Azureアプリ、企業同意フローなし、共有クライアントID
• realのカバレッジ* - メール、カレンダー、連絡先、to-do、ドラフト、フォルダ、バッチのオプス、スレッドではなく、メールのみまたはカレンダーのみラッパーではなく

outlook-mcp

MCP server for Microsoft Outlook personal accounts via Microsoft Graph API.

Personal Microsoft accounts only — @outlook.com, @hotmail.com, @live.com. Work/school accounts (Entra ID) are not supported: the server is built and tested on personal accounts. Fixes that make a tool behave on a work account, without changing what a personal account sees, are welcome.

Disclaimer: Independent open-source project. Not affiliated with, endorsed by, or supported by Microsoft Corporation. “Outlook” and “Microsoft Graph” are trademarks of Microsoft.

---

Who this is for

You’ll like this if you’re:

• An agent builder wiring Outlook into your own infra (OpenClaw, Claude Code, Cursor, custom MCP host) and want a typed tool surface — not stdout you have to parse
• Building on personal Microsoft accounts (Outlook.com / Hotmail / Live) and want full control: BYO Azure app, no enterprise consent flow, no shared client ID
• Looking for real coverage — mail, calendar, contacts, to-do, drafts, folders, batch ops, threading — instead of a mail-only or calendar-only wrapper
• Security-conscious: tokens in the OS keyring (Keychain on macOS, libsecret on Linux – never cleartext unless you opt in), granular allow_categories, optional read_only mode, zero telemetry

This isn’t for you if you need work/school M365 accounts (use Microsoft’s official tooling — Entra ID auth and admin-consent flows are out of scope here), or if a basic mail-only client would suffice (this has 76 tools — way more than you need for “read my inbox”).

How it differs from other Outlook tools you’ll find

This is the only first-class MCP server in the personal-Outlook space — most alternatives are bash scripts or skill-shaped CLI wrappers the agent shells out to. That distinction matters: the agent gets typed tool schemas with structured args/returns, not stdout it has to parse. Other things you won’t find elsewhere: /$batch-optimized triage (10-20× faster on bulk ops), recursive folder ops with name resolution, granular per-category permissions, multiple mailboxes (one server per account via OUTLOOK_MCP_CONFIG_DIR), and full attachment write paths including >3MB upload sessions for drafts and calendar events.

---

What This Enables

Give your AI agent full Outlook access. Example prompts that just work:

• “Summarize my unread email from the past 24 hours and flag anything time-sensitive.”