How I Built a Read-Only MCP Server for Microsoft Teams by Parsing IndexedDB in Go A developer built teamscache, an open-source Go CLI and read-only MCP server that extracts Microsoft Teams chats, messages and @-mentions directly from the new Teams desktop client's local IndexedDB/LevelDB cache, avoiding Microsoft Graph API permissions and tenant admin consent. The tool parses LevelDB tables and Snappy-compressed blocks in pure Go, decodes Blink and V8 serialized values, copies data to a temporary owner-only directory for parsing, and makes zero network requests. It exposes tools such as overview, search_messages and read_conversation to assistants like Claude Code over stdio. If you work as an external consultant or contractor across multiple client tenants, you probably know this problem. You want to automate your workflow or connect an AI assistant like Claude Code to your Microsoft Teams messages, so you look into the Microsoft Graph API. However, you quickly run into a restriction. Reading messages through Graph requires permissions like Chat.Read and tenant admin consent. When you are a guest in another organization's tenant, getting an Azure app registration approved just to read your own chats is usually not possible. However, if you use the new Microsoft Teams v2 desktop client, your recent conversations are already stored on your disk. I built teamscache https://github.com/stn1slv/teamscache , a Go CLI and read-only MCP server that reads chats, messages, and @-mentions directly from the local Teams desktop cache. It requires no Graph API access, no OAuth tokens, and makes zero network requests. The new Teams client com.microsoft.teams2 on macOS, the MSTeams package on Windows is built on Edge WebView2. Like other Chromium-based apps, it stores local application data in IndexedDB , which Chromium saves on disk using LevelDB with values encoded in Blink and V8 serialization formats . When teamscache runs, it performs five steps: --leveldb path . teamscache copies the data and referenced blob files to a temporary directory with owner-only permissions and deletes the copy right after parsing. .ldb tables and .log files including Snappy-compressed blocks in pure Go without running a LevelDB engine. replychains and numbered stores like replychains-2 , chat metadata from conversations , and mentions from mentions-metadata-items , grouped by tenant and user ID. Since LevelDB keeps older versions of updated records until compaction, teamscache uses only the newest version of each record. If someone edits a message or you read a mention in the UI, the tool reflects the current state. You can install teamscache via Homebrew on macOS or Linux: brew install stn1slv/tap/teamscache Or install it with Go 1.27 or later: go install github.com/stn1slv/teamscache/cmd/teamscache@latest https://github.com/stn1slv/teamscache/cmd/teamscache@latest Pre-built binaries for macOS, Linux, and Windows are also available on the GitHub Releases page https://github.com/stn1slv/teamscache/releases . Every CLI command prints structured JSON to stdout and a short summary to stderr , so you can cleanly pipe output to jq or save it to a file: List all tenant and user accounts found in the cache teamscache accounts See recent activity grouped by conversation over the last 7 days teamscache overview --days 7 Check unread @-mentions that need your attention teamscache mentions --unread Search messages by text or sender name teamscache search "architecture review" Read all cached messages in a specific conversation oldest first teamscache read "19:abc@thread.v2" --limit 0 chat.json If you switch between multiple tenants or Edge WebView2 profiles, you can filter any command using --account "