Do I need an Azure app registration or API key?

No. connect_m365_account uses Microsoft's device-login flow. You just get a short code, sign in at microsoft.com/devicelogin, and you're connected — no client secret, no API key, nothing to configure in Azure.

Why are there two calls to connect?

The first call returns a login code and the devicelogin URL. You authenticate in your browser, then make the second call so LMCP can confirm the sign-in and complete the connection. It's a standard, secure OAuth device-code flow.

Is my Microsoft 365 data sent to a server?

No. LMCP runs natively on your Mac. Your tokens and your mail, calendar, Teams and OneDrive data stay local — nothing is stored on an LMCP server or any cloud.

Connect Microsoft 365 to AI on Mac

The connect_m365_account tool links your Microsoft 365 account to your AI assistant so it can work with Outlook mail, calendar, Teams, OneDrive and the Microsoft Graph — all from a natural-language prompt. The flow is two simple calls: ask once to get a short login code, sign in at microsoft.com/devicelogin, then ask again to finish connecting. No app registration, no client secret, no copy-pasting tokens.

A real prompt you can type:

"Connect my Microsoft 365 account." — your AI replies with a device code and the login URL. After you authenticate in the browser, you say "OK, I'm signed in, finish connecting" and the link is established.

LMCP is a free, native macOS MCP server with 150+ tools. It lets AI assistants use your real Mac apps and accounts locally. Download LMCP to get started.

Which AI agents work?

Once LMCP is installed, connect_m365_account is available to every major AI client:

Desktop apps — Claude Desktop, Cursor, VS Code (GitHub Copilot), Windsurf and Zed auto-configure through a local stdio connection. No manual setup beyond installing LMCP.
Web AIs — ChatGPT, Claude.ai (web), Grok and Perplexity connect through the LMCP Cloud Relay connector, which securely bridges the web client to your Mac.

Whatever assistant you prefer, the device-login flow is identical.

Automation

Connecting your account is the gateway step. Once linked, connect_m365_account chains with the rest of the Microsoft toolset so the AI can act in a single conversation:

Connect, then "summarize my unread Outlook email and draft replies."
Connect, then "list my Teams channels and pull the latest messages."
Connect, then "find the file Anna shared in OneDrive last week and send it to my calendar invite."

Because the AI orchestrates the tools, you describe an outcome and it handles the sequence — authenticate, query Graph, act.

Context

The connection gives your AI access to your real Microsoft 365 data: your actual mailbox, your meetings, your Teams conversations, your OneDrive files. Answers are grounded in what's truly in your account rather than guesses — so "What did my manager email me about the Q3 review?" returns the genuine thread, with names, dates and attachments intact.

Productivity

Setup takes under a minute and you only do it once. After that, you skip the constant context-switching between your AI window and the Microsoft apps. Triage a full inbox, prep for a meeting from your real calendar, or pull a Teams thread into a summary — tasks that used to mean five tabs and ten clicks become one sentence. Most users save several minutes per email session and avoid breaking focus.

Privacy & GDPR

Everything runs locally on your Mac. The device-login happens directly between your machine and Microsoft; your tokens stay on your Mac and your emails, files and messages are never copied to an LMCP server or any third-party cloud. There's nothing stored remotely to leak or subpoena. This is privacy by architecture — read more in GDPR-compliant by architecture.