Microsoft Teams

io.github.magurelabsPublished by GitHub account magurelabsv2.0.0Updated Nov 14, 2026

Read Teams chats and channel messages, and send messages or create meetings.

The publisher's own server: Microsoft Learn MCP

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Connects an assistant to Microsoft Teams so it can read chats and channel messages, send messages, and create meetings.

What you can do
  • Read chats and channel messages in Microsoft Teams
  • Send messages to chats and channels
  • Create meetings
When to use it
Useful when you want an assistant to summarize or follow Teams conversations and post replies or schedule meetings without leaving the chat.
Requirements
Runs as a local process via a Docker image (streamable-http transport), desktop only. Requires the MCP_MODE setting (defaults to platform) and the MCP_SERVICE_TOKEN secret, which callers send as the X-Service-Token header in platform mode; hosted and local modes need further configuration per the project docs.
Before you install
The server can send messages and create meetings, so assistant actions are visible to colleagues and may notify them. It requires a shared service token (MCP_SERVICE_TOKEN) that grants access to the connector; keep it secret. Teams content read by the assistant is sent to the model provider.

Installation

In SourceWeft

  1. Open Microsoft Teams in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

1
  1. v2.0.0LatestNov 14, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

Other Microsoft integrations