Microsoft Teams MCP

What microsoft-teams-mcp does

The microsoft-teams-mcp MCP server gives an MCP client access to Microsoft Teams chats, group conversations, meeting chats, teams, channels, messages, activity notifications, and attachments. It can enumerate conversations and channels, read messages by name or ID, find unread messages, identify conversations that changed recently, and export chats or channels to files.

Read operations do not change Teams read indicators by default. The server also supports confirmed actions for sending a message, adding or removing a reaction, and advancing the read marker for a chat or channel.

The server works with the current teams.cloud.microsoft host. The older teams.microsoft.com host is not supported.

How it works

Teams data is requested from Microsoft’s chat-service REST API. Because the required bearer token is available in the signed-in Teams web session, the server uses the ContextMint Bridge browser extension and @fetchproxy/cli to capture the authorization header from a request made by the Teams tab. After capture, requests run from the server and do not require the relevant chat or channel to remain open.

The chat-service token is cached for its approximate 23-hour lifetime. If a request receives a 401 response, the server attempts one recapture and retry. The Activity feed is treated as a Teams conversation, so its view does not need to be open.

Attachment downloads use a separate SharePoint token because shared files are stored outside the chat-service object store. Message search uses a separate Microsoft Substrate token captured from a Teams search request. Search can fall back to scanning recent conversations when Substrate capture or querying is unavailable.

Setup and configuration

Install the package globally with npm i -g @chrischall/microsoft-teams-mcp, then install a matching major version of @fetchproxy/cli and the ContextMint Bridge extension. Chrome is currently required; Safari support is not available. On the first call, approve the six-digit pairing code shown by the server in the Bridge popup.

The server can also run with a direct TEAMS_ACCESS_TOKEN. Setting TEAMS_DISABLE_FETCHPROXY=true disables browser capture and makes that token necessary. Optional settings control the chat-service region and base URL, capture timeout, token caching, and cache-file locations. Search may require a one-time re-pair after adding its Substrate trust scope, and file downloads may require a one-time SharePoint re-pair.

An opencode configuration can register the package as a local MCP process:

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

Tools and capabilities

The microsoft-teams-mcp MCP server exposes tools for:

• Listing all conversations and channels available to the signed-in account.
• Reading chat or channel messages by ID or name.
• Listing unread messages and conversations with new messages.
• Searching message text through Substrate or a recent-conversation scan.
• Reading the Teams Activity feed.
• Fetching an individual attachment, including inline images and SharePoint files.
• Exporting chat and channel messages to files.
• Checking token resolution with a health check.
• Sending messages, adding or removing reactions, and marking conversations read.

Write actions and explicit read-marker changes require confirmation before they modify Teams data.

Limitations and notes

Browser pairing is part of the default authentication flow, and the Teams tab must issue a relevant request before a token can be captured. Search may need a search performed in Teams while capture is waiting. SharePoint tokens are short-lived and scoped to a host family, so the first file from a host may require opening that file once in a signed-in Teams tab.

A file that the account cannot access, or that belongs to an unsupported SharePoint host, may return metadata and an open link instead of file contents. The project documentation states that it is maintained by AI and should be used at the operator’s discretion.