Summary
Teams stops being the tab you have to go back to.
Reading a thread, replying inside it, reacting and posting a file all run through Microsoft Graph, so the whole exchange happens where the work is. search_messages takes KQL, which turns 'what did Bob say about the migration' into a query with from: and a date window rather than ten minutes of scrolling.
What it is
A Microsoft Teams client over Microsoft Graph, 30 tools split between channel messages, chat messages, people lookup and tenant-wide search.
What you get
- Channel messages read with sender and timestamps, then sent, replied to, edited or soft-deleted, with markdown, mentions and importance levels
- The same for 1:1 and group chats, including creating a chat from a list of user emails and an optional topic
- Reactions set and removed on channel messages and chat messages alike, by Unicode emoji or by name — like, angry, sad, laugh, heart, surprised
- Files uploaded from local disk and posted, to a channel's SharePoint folder or to a chat through OneDrive, as reference attachments
- Inline content pulled back out: images and other hosted content from a channel or chat message returned as base64 with metadata
- Search across every channel and chat through the Microsoft Search API, with KQL filters such as from: and mentions:, plus a direct read of recent @mentions of you
- Directory lookups — the teams you belong to, a team's channels and members, and users found by name or email
Requirements
Npx on your PATH and a Microsoft Graph connection for your organisation; auth_status reports whether that connection is authenticated and which profile it carries.
Setup effort
One command plus a key — npx @floriscornel/teams-mcp@latest, then supply credentials