TeamsCache – Read Local Microsoft Teams Messages via CLI or MCP A tool called teamscache, published by developer stn1slv, reads the local message cache of the new Microsoft Teams (v2) desktop client and outputs chats, messages and @-mentions as JSON, and can run as a read-only MCP server for AI assistants. The tool avoids Microsoft Graph, OAuth, Azure app registration and the network entirely, reading only what the signed-in Teams client already stores on disk, which the author says helps users such as guests in another company's tenant who often cannot obtain Graph permissions like Chat.Read without admin consent. It installs via Homebrew (brew install stn1slv/tap/teamscache), Go 1.27 or later, or make build, requires a new Teams client signed in at least once, and auto-discovers the cache on macOS and Windows but only best-effort on Linux. teamscache reads the message cache of the new Microsoft Teams v2 desktop client on your computer. It prints chats, messages and @-mentions as JSON, and it can also run as a read-only MCP server for AI assistants. It does not use Microsoft Graph, OAuth, an Azure app registration or the network. It reads only what the signed-in Teams client already keeps on your disk. To read Teams messages through Microsoft Graph, you need permissions such as Chat.Read , and many tenants allow them only after admin consent. As a guest in another company's tenant, you often cannot get that consent. The desktop client still keeps your recent conversations on your disk, and teamscache reads them from there. With Homebrew on macOS or Linux: brew install stn1slv/tap/teamscache Binaries for macOS, Linux and Windows are on the releases page https://github.com/stn1slv/teamscache/releases . With Go 1.27 or later: go install github.com/stn1slv/teamscache/cmd/teamscache@latest Or build from source with make build ; the binary is written to bin/teamscache . You need a new Teams client that has been signed in at least once. Auto-discovery of the cache works on macOS and Windows. On Linux it is best effort. 1. Read all cached messages in one chat oldest first : teamscache conversations --limit 0 find the conversation "id" teamscache read "19:abc@thread.v2" --limit 0 2. Filter by account or WebView2 profile when you have multiple tenants or profiles: teamscache accounts get "