Microsoft Teams MCP server

microsoft-teams-mcp

MCP server for Microsoft Teams — list your chats, teams and channels, and read whichever chat or channel is currently open, routed through your signed-in browser tab.

This project was developed and is maintained by AI (Claude Code). Use at your

own discretion.

How it works — and its one real limitation

Teams Web's chat and message data lives only in a client-side cache fed by a WebSocket/registrar sync channel — there is no REST or GraphQL endpoint that returns it. So this server does not capture a token and make plain server-side requests the way an API-backed MCP would; instead every call routes through the fetchproxy browser bridge and reads the DOM your signed-in teams.cloud.microsoft tab has already rendered. teams.microsoft.com (the old host) is not supported.

That has one real consequence: this server can only read whichever chat or channel is currently displayed in your browser tab. The bridge can fetch and read — it cannot navigate a tab to a different conversation. teamslistchats and teamslistteamsandchannels always work (their sidebars are always rendered once that nav section is open); teamsgetopenchatmessages and teamsgetopenchannelposts read whatever conversation you have open. To read a different chat or channel, open it in the browser first.

The bridge is on the request path for every call here, not just once to mint a token — unlike an API-backed MCP, there is nothing to cache between calls.

Install

npm i -g @chrischall/microsoft-teams-mcp

Requires the Transporter Chrome extension and @fetchproxy/cli, on a matching major version:

npm i -g @fetchproxy/cli

The first call prints a 6-digit pair code to approve in the Transporter popup; the grant persists.

Install in opencode

opencode reads MCP servers from opencode.json (project) or ~/.config/opencode/opencode.json (global):

{
  "mcp": {
    "servers": {
      "teams": {
        "type": "local",
        "command": ["npx", "-y", "@chrischall/microsoft-teams-mcp"]
      }
    }
  }
}

Configuration

Everything is optional — this server needs no credentials of its own.

Tools

last-activity time, and Teams' own conversation id for each chat.

• teamslistchats — the Chat sidebar: title, last-message preview,

currently open: sender, ISO-8601 time, message id, and text.

• teamsgetopenchatmessages — the message thread of whichever chat is

DIFFERENT view from Chat): every team and channel the user belongs to, with each channel's parent team name.

• teamslistteamsandchannels — the Teams-and-Channels sidebar (a

is currently open: sender, subject (when present), prose time (not ISO-8601 — Teams doesn't expose one for these), message id, and text. Threaded replies under a post are not included.

• teamsgetopenchannelposts — the top-level posts of whichever channel

mentions, replies, reactions, and the like across every chat and channel, each with its title, message preview, prose time, and location (the team/channel or chat it happened in). Requires the Activity view open.

• teamsgetactivity — the Activity feed (the bell icon in the left nav):

• teams_healthcheck — verifies the bridge can reach a signed-in tab.

All five data tools are read-only and take no arguments.

Shortened. The full README is on GitHub.