Read Microsoft Teams Messages with Claude on Windows — No Graph API to Read

To let Claude read your Microsoft Teams chats on Windows, install LMCP — a free local MCP server that reads the Teams desktop app’s own local cache on your PC. Because reading never calls Microsoft Graph, there is no Azure app registration, no admin consent and no API key for it — the usual blockers when IT owns the tenant. Your AI can list chats and channels, read history, and search across everything already cached on your machine.

What You Can Read — 100% Local, No API

Through LMCP, your AI assistant can:

List your chats — see all your 1:1 and group conversations with recent activity
Read chat messages — get the full message history from any chat
List your teams and channels — see which Teams workspaces and channels you belong to
Read channel messages — get messages from any channel you have access to
Search messages — find something across all your chats at once
Check call history — direction, participants and duration of your Teams calls

All of this reads the local cache the Teams desktop app already keeps on your PC. Nothing touches Microsoft's servers, and no tenant admin needs to approve anything.

Sending a Message Is a Different Path — Read This Before You Assume It's the Same as Reading

This is the one place Windows genuinely differs from reading, so it is worth being direct about it: LMCP cannot send a Teams message from the local cache the way it reads one. Sending goes through a second, separate tool that calls the Microsoft Graph API, which means it does require connecting a Microsoft 365 account (OAuth) and the ChannelMessage.Send permission first.

In practice: reading Teams is instant and needs nothing beyond having Teams installed and signed in. Sending needs one extra step — running connect_m365_account to link your Microsoft 365 account, after which your AI can send chat and channel messages (with a preview and confirmation, like every other send action in LMCP). If your organization does not allow connecting personal apps to Microsoft 365, sending will not be available to you — reading still will.

How to Install

Download LMCP for Windows and install it:

Run the downloaded LMCP-Setup.exe from your Downloads folder
Follow the installer — no admin rights needed, it installs to your user folder
LMCP starts automatically and appears in your system tray

Takes about 30 seconds. Your AI clients are configured automatically.

Then restart your AI client:

Claude Desktop — quit completely and reopen
Cursor — restart the editor
VS Code — reload the window (Ctrl+Shift+P → “Reload Window”)
ChatGPT / Windsurf — restart the application

Make sure Microsoft Teams (the desktop app) is installed and you are signed in. LMCP finds your Teams data automatically — no additional configuration for reading.

Example Prompts

“What did the team discuss today in the General channel?” — reads and summarizes recent channel messages
“Show my conversation with Marco” — lists recent messages from a specific chat
“Find any messages about the deployment deadline” — searches your chats and channels
“Summarize what I missed in Teams this morning” — aggregates across conversations
“Who did I miss a call from yesterday?” — checks your Teams call history

Real-World Workflows

Daily standup summary

Prompt — paste into your AI

Read the engineering channel messages from today, extract what each person is working on, identify blockers, and create a summary.

Instead of scrolling a busy channel, your AI reads everything and organizes it by person.

Meeting prep from Teams

Prompt — paste into your AI

Check what the team discussed about Project X in the last week across all channels, and list open questions I should bring up in tomorrow's meeting.

Your AI scans multiple channels and prepares a briefing — no Graph API, no per-channel searching by hand.

LMCP also connects your AI assistant to Outlook, OneDrive and Office documents on Windows. See the full list of guides or learn more at local-mcp.com.

Why other solutions require the Graph API for everything

The official way to access Teams data programmatically is Microsoft Graph, which requires Azure AD app registration, tenant-admin consent, OAuth token management, and careful scope selection — a non-starter for most individuals. LMCP bypasses all of that for reading by using the local cache the Teams desktop app already maintains. Sending is the one action that genuinely reaches Teams' servers, which is why it is the one action that needs the same Graph connection any other integration would.

Limitations

Sending requires a connected Microsoft 365 account — reading does not. See the section above.
Only cached messages are available for reading — if you have not opened a chat in months, its older messages may not be on disk.
Requires the Teams desktop app — the web version of Teams does not create a local cache LMCP can read.
Cache freshness — reflects the state from when Teams last synced; keep Teams running for up-to-date reads.

Frequently Asked Questions

How do I let Claude read my Teams chats on Windows without admin approval?

Install LMCP and sign in to the Teams desktop app. LMCP reads Teams' own local cache — there is nothing for a tenant admin to approve for reading.

Can Claude send a Teams message for me on my work laptop?

Yes, but it is a separate path from reading: sending goes through Microsoft Graph, so it needs you to connect your Microsoft 365 account first (connect_m365_account). Reading needs none of that.

Can I connect Claude to Microsoft Teams without the Graph API on Windows?

For reading, yes — entirely. For sending, no — sending a message is the one action that reaches Teams' servers, and Windows does not have a no-API path for it the way reading does.

Does it need admin approval to read Teams?

No. Because reading uses data already on your disk, there is no tenant admin consent to request for it.