msteams-local-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@msteams-local-mcpsearch my recent messages for 'quarterly budget'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
msteams-local-mcp
Read the new Microsoft Teams (v2) message cache locally — and expose it over the Model Context Protocol (MCP) for AI assistants (Claude, etc.).
No Microsoft Graph. No OAuth. No Azure app registration. No network. It only reads what the signed-in Teams desktop client already keeps on your own disk.
Why
Reading your Teams messages through Microsoft Graph requires Chat.Read /
ChannelMessage.Read.All, which many tenants gate behind admin consent — so
if you're an external/guest member of a client's tenant, you often simply can't.
But the desktop client still caches your recent conversations locally, in the
clear, for the account you're signed into. This tool reads that cache.
Existing forensic parsers (e.g. forensicsim,
teams-decoder) target the older
Teams (classic / Teams 1.x) schema and return nothing on the current client.
msteams-local-mcp maps the current Teams 2.x schema (react-web-client:
replychain-manager → replychains → messageMap) on top of the excellent
ccl_chromium_reader for the
low-level Chromium LevelDB + V8 decoding. Nothing here is tied to any tenant or
account — it enumerates every context in the cache.
Related MCP server: Teams Messenger MCP App
How it works
The new Teams client (com.microsoft.teams2 on macOS, MSTeams MSIX on Windows)
is an Edge WebView2 app. It stores recent conversations in an IndexedDB database
backed by Chromium LevelDB, values serialized in V8. This tool:
locates that LevelDB (auto-discovery per OS, or
MSTEAMS_LEVELDB=/path),copies it to a temp dir (the running client holds a file lock),
enumerates each
(tenant, user)context and readsreplychains/conversations,yields plain-text messages (sender, timestamp, content), skipping the rare record that fails to deserialize.
Install
pipx install "git+https://github.com/KamorionLabs/msteams-local-mcp"
# or: uv tool install "git+https://github.com/KamorionLabs/msteams-local-mcp"Requires Python ≥ 3.10 and a signed-in new-Teams desktop client.
Use — CLI
msteams-local-dump accounts # tenant/user contexts + inferred label
msteams-local-dump conversations # chats/channels
msteams-local-dump search "quarterly budget" # substring search across messages
msteams-local-dump search "PR" --account <tenantId:userId> --limit 20Use — MCP
Run the server (stdio):
msteams-local-mcpRegister it with an MCP client. Example (Claude Desktop / Claude Code):
{
"mcpServers": {
"msteams-local": { "command": "msteams-local-mcp" }
}
}Tools exposed (all read-only):
Tool | Purpose |
| who messaged you: recent activity grouped by conversation (best first call) |
| messages received in the last N days, newest first — one call for "what did I miss" |
| @-mentions of you (with content + read state); |
| your unread @-mentions (the only reliable unread signal — see note) |
| substring search across messages, optional |
| messages of one conversation (newest last) |
| chats/channels (id, title, type) |
| the tenant/user contexts, with an inferred org label |
All accept an optional account filter (a key from list_accounts) to scope to one
tenant/org. Note on unread: the local cache stores no general per-message read
marker, so true "all unread" can't be derived; unread_messages returns unread
@-mentions, and recent_messages covers "everything received while I was away".
Performance: the LevelDB is parsed once and cached (in memory + on disk, keyed on the store's signature), so chained calls are near-instant and re-parsing happens only when Teams writes new data.
Scope, limits & ethics
Read-only. This tool never writes to Teams or sends anything.
Your own data. It reads the local cache of the account you are signed into. Use it only on machines and accounts you're authorized to. Respect your employer's / clients' policies and applicable law.
Recent only. The cache holds synced/recent conversations, not full history, and no server-side search.
Schema drift. Teams changes its internal schema between major versions; the mapping may need updates. PRs welcome.
Platforms: developed and tested on macOS (Teams 2.x, 2026). Windows paths are included; Windows testing/PRs welcome.
License
MIT — see LICENSE. Builds on ccl_chromium_reader (MIT).
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityCmaintenanceMCP server that integrates Microsoft Teams messaging (read, post, mention, list members and threads)Last updated6387Apache 2.0
- Flicense-qualityDmaintenanceA Model Context Protocol server that bridges Microsoft Teams and MCP-compatible clients, enabling chat integration, message handling, and advanced search capabilities without REST API endpoints.Last updated1
- Flicense-qualityDmaintenanceA Model Context Protocol server that bridges Microsoft Teams with MCP-compatible clients (LLMs, agentic frameworks, CLI), enabling chat integration, message search, and event streaming without traditional REST API endpoints.Last updated
- AlicenseAqualityAmaintenanceA read-only, offline MCP server for Microsoft Teams that searches chats, reads conversations, and finds people directly from the local on-disk cache with no cloud API.Last updated6388Apache 2.0
Related MCP Connectors
Search your AI chat history (ChatGPT, Claude, Codex) from any MCP client. Remote, private, read-only
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
Official Microsoft MCP Server to query Microsoft Entra data using natural language
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/KamorionLabs/msteams-local-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server