All servers / Chat / Microsoft Teams MCP server
Microsoft Teams MCP server
MCP server that lets AI assistants work with Microsoft Teams (web) through a Chrome/Edge extension bridge
Tested by ConnectATDScore 88 out of 100. Tested 2026-11-18 on package version 0.3.81. Package: mcp-teams · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 18 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (1.8 seconds including download)
- Tools offered: 13
- Last published: 2026-11-18
- Weekly downloads (npm): 3,690
- License: MIT · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
get_versionno parametersShows the mcp-teams server version and build, the browser extension version (it has its own version line) and whether this server works with it (extensionSupported, and the missingFeatures it lacks), and whether Teams is reachable (which of its services have a session). restartNeeded: true means mcp-teams was updated on disk while this server still runs the old code: the user should reconnect it (in Claude Code: /mcp), and reload the extension if it changed too.
reload_extensionno parametersReloads the mcp-teams browser extension from disk, e.g. after an update changed it, and waits until it is connected again. Returns the extension version before and after. Refused while a send confirmation window is open.
api_traffic3 of 4 parameters describedLists the API endpoints the open Teams tab called while recording was on: method, host, path, status, which headers were sent (names only, never values) and the auth scheme. Used to find out which API Teams uses for a feature. Recording is off until you turn it on: first call with record: true, then click through the feature in Teams, then call again to list what it called. Recording stops after 30 minutes or with record: false; what was recorded stays until clear.
list_teams2 of 2 parameters describedLists the teams you are a member of, each with its channels. Group chats and meeting chats are not teams, even when they are named like one: list_chats lists those. Use 'Team/Channel' or a channel id as the conversation for read_messages and send_message. The list may be up to a minute old (see refresh). Needs a Teams tab open in the browser: without one it fails at once.
list_chats2 of 4 parameters describedLists your chats (1:1, group and meeting chats), most recent first, with their title (or the other members' names), the last message and whether it is unread. Returns ids for read_messages and send_message. The list may be up to a minute old, so the last message and unread state can lag; pass refresh: true for the current ones. Needs a Teams tab open in the browser: without one it fails at once.
read_messages7 of 7 parameters describedReads the latest messages of a chat or channel, oldest first: sender, time, text (formatting removed), files shared and reactions. In channels, replies are nested under their post (a reply whose post is on an older page comes on its own, with replyTo). To read further back, pass the returned olderCursor as `cursor` (with the same conversation and reply_to); it is there whenever older history exists, so keep paging while it is returned. A page usually costs one or two Teams requests, but one call reads at most 20 pages of Teams history: it may then return fewer messages than asked, even none, with `truncated: true`, a note and an olderCursor to go on. `before` (a time) also works but re-reads from the newest message each call, so it hits that limit sooner. Give cursor or before, not both. With reply_to, reads one channel post's whole thread.
list_meetings3 of 4 parameters describedLists your Teams meetings (each scheduled meeting or recurring series has a meeting chat), most recent activity first: subject, scheduled time (for a series, its first occurrence), organizer, whether a transcript exists, and whether another organization hosted it (`external`: its chat and recordings are usually no longer readable afterwards). The list may be up to a minute old (see refresh). Use get_meeting for the calls held and who attended, read_transcript for what was said, read_messages for the meeting chat.
get_meeting2 of 2 parameters describedOne meeting with the calls held in it, newest first (a recurring meeting has one per occurrence): when it started and ended, who joined, the recording's link, and whether there is a transcript.
read_transcript4 of 4 parameters describedWhat was said in a meeting, from its Teams transcript: lines '[hh:mm:ss] Speaker: text', plus how long each speaker talked. Reads the latest call with a transcript unless `session` names another. Long transcripts are cut at max_length; pass the returned continueFrom as `from` to read on. Transcripts are stored in the organizer's OneDrive, so this may open OneDrive in a background tab.
search_transcripts4 of 4 parameters describedFinds what was said in meetings: the transcript lines containing all words of the query, each with the line before it, from the most recent meetings with a transcript (or one meeting). Then read_transcript with `from` reads around a match.
search_messages1 of 3 parameters describedSearches all your Teams chats and channels with Microsoft Search, like the search box in Teams. Returns matching messages with their conversation id (for read_messages), sender, time and a highlighted excerpt.
find_people0 of 2 parameters describedLooks people up by name or email in your organization (and people you work with), as in Teams' people picker: name, email, job title, department, office.
send_message6 of 6 parameters describedAsks to post a message in an existing chat or channel (conversation), to reply to a channel post, or to start a chat with people (to): one person for a 1:1 chat, several for a group chat. If a chat with exactly those people already exists, the message goes there. The extension shows a confirmation window with the message, where it goes and who is in a new chat; nothing is posted, and no chat is created, unless the user clicks Send there. Returns whether it was sent, and when Teams recorded it (time). A sent result can have time: null with a timeNote when Teams accepted the message but its answer, or the time in it, couldn't be read: it was still posted, so don't send it again. Plain text; line breaks are kept and links become clickable.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.