mcp-teams
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 4 tools tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y mcp-teams@0.3.71
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
4 tools that take no input and look read-only were called once with nothing. 1 returned a result.
get_version | Returned a result under 0.1 s · 612 characters |
list_teams | No usable answer tool reported an error: Browser extension is not connected. Open Chrome or Edge with the mcp-teams extension installed (run `mcp-teams setup`). |
list_chats | No usable answer tool reported an error: Browser extension is not connected. Open Chrome or Edge with the mcp-teams extension installed (run `mcp-teams setup`). |
list_meetings | No usable answer tool reported an error: Browser extension is not connected. Open Chrome or Edge with the mcp-teams extension installed (run `mcp-teams setup`). |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
get_version
Shows the mcp-teams server version and build, the browser extension version, 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.
reload_extension
Reloads 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_traffic record, filter, limit, clear
Lists 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_teams include_ids, refresh
Lists 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_chats query, unread_only, limit, refresh
Lists 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.
8 more tools
read_messages conversation, limit, cursor, before, reply_to, include_system, max_length
Reads 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_meetings query, transcript_only, limit, refresh
Lists 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_meeting meeting, limit
One 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_transcript meeting, session, from, max_length
What 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_transcripts query, meeting, meetings, limit
Finds 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_messages query, limit, offset
Searches 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_people query, limit
Looks 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_message conversation, to, title, text, reply_to, subject
Asks 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.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Files it wrote
/tmp/ .mcp-teams/ config.json /tmp/ .mcp-teams/ server.log
Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.
Install facts
| License | MIT |
|---|---|
| Needs | node >=20 |
| Source | github.com/HeeyunCho/mcp-teams |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-pt4ZOC3bCpusLr01jvFYJ/XniYP6qZ0hxphXr24Kxd68NuLsE/K+9jcyAxrDfmsEMEcX9k6X6rziwL7fTJMH2w== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 0.3.71 | 2026-11-16 | Starts with no setup | 13 |
| 0.3.70 | 2026-11-12 | Starts with no setup | 13 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/mcp-teams)
New version out? Ask for a fresh report.