Microsoft Teams MCP

Name: Microsoft Teams MCP
Author: chrischall

by chrischallversion 0.8.5i★ –iRuns on your computer

Registry nameio.github.chrischall/microsoft-teams-mcp

Install

Overview

Description from the maker (original English)

Microsoft Teams for Claude — read any chat or channel and its unread messages; send and react

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiEarly↓ 1K/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Chat & email
You need to fill in: TEAMS_ACCESS_TOKEN, MCP_CONFIRM_SECRET

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: TEAMS_WS_PORT, FETCHPROXY_WS_HOST, FETCHPROXY_IDENTITY_DIR, TEAMS_ACCESS_TOKEN, TEAMS_DISABLE_FETCHPROXY, TEAMS_CHATSVC_REGION, TEAMS_CHATSVC_BASE, TEAMS_CAPTURE_TIMEOUT, TEAMS_TOKEN_CACHE, TEAMS_TOKEN_FILE, TEAMS_SUBSTRATE_TOKEN_FILE, TEAMS_SHAREPOINT_TOKEN_FILE, TEAMS_TIME_ZONE, TEAMS_OUTPUT_DIR, MCP_CONFIRM_MODE, MCP_CONFIRM_ELICITATION, MCP_CONFIRM_TTL_SECONDS, MCP_CONFIRM_SECRET

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "microsoft-teams": {
      "command": "npx",
      "args": [
        "-y",
        "@chrischall/microsoft-teams-mcp"
      ],
      "env": {
        "TEAMS_WS_PORT": "your-value",
        "FETCHPROXY_WS_HOST": "your-value",
        "FETCHPROXY_IDENTITY_DIR": "your-value",
        "TEAMS_ACCESS_TOKEN": "your-value",
        "TEAMS_DISABLE_FETCHPROXY": "your-value",
        "TEAMS_CHATSVC_REGION": "your-value",
        "TEAMS_CHATSVC_BASE": "your-value",
        "TEAMS_CAPTURE_TIMEOUT": "your-value",
        "TEAMS_TOKEN_CACHE": "your-value",
        "TEAMS_TOKEN_FILE": "your-value",
        "TEAMS_SUBSTRATE_TOKEN_FILE": "your-value",
        "TEAMS_SHAREPOINT_TOKEN_FILE": "your-value",
        "TEAMS_TIME_ZONE": "your-value",
        "TEAMS_OUTPUT_DIR": "your-value",
        "MCP_CONFIRM_MODE": "your-value",
        "MCP_CONFIRM_ELICITATION": "your-value",
        "MCP_CONFIRM_TTL_SECONDS": "your-value",
        "MCP_CONFIRM_SECRET": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add microsoft-teams --env TEAMS_WS_PORT=your-value --env FETCHPROXY_WS_HOST=your-value --env FETCHPROXY_IDENTITY_DIR=your-value --env TEAMS_ACCESS_TOKEN=your-value --env TEAMS_DISABLE_FETCHPROXY=your-value --env TEAMS_CHATSVC_REGION=your-value --env TEAMS_CHATSVC_BASE=your-value --env TEAMS_CAPTURE_TIMEOUT=your-value --env TEAMS_TOKEN_CACHE=your-value --env TEAMS_TOKEN_FILE=your-value --env TEAMS_SUBSTRATE_TOKEN_FILE=your-value --env TEAMS_SHAREPOINT_TOKEN_FILE=your-value --env TEAMS_TIME_ZONE=your-value --env TEAMS_OUTPUT_DIR=your-value --env MCP_CONFIRM_MODE=your-value --env MCP_CONFIRM_ELICITATION=your-value --env MCP_CONFIRM_TTL_SECONDS=your-value --env MCP_CONFIRM_SECRET=your-value -- npx -y @chrischall/microsoft-teams-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "microsoft-teams": {
      "command": "npx",
      "args": [
        "-y",
        "@chrischall/microsoft-teams-mcp"
      ],
      "env": {
        "TEAMS_WS_PORT": "your-value",
        "FETCHPROXY_WS_HOST": "your-value",
        "FETCHPROXY_IDENTITY_DIR": "your-value",
        "TEAMS_ACCESS_TOKEN": "your-value",
        "TEAMS_DISABLE_FETCHPROXY": "your-value",
        "TEAMS_CHATSVC_REGION": "your-value",
        "TEAMS_CHATSVC_BASE": "your-value",
        "TEAMS_CAPTURE_TIMEOUT": "your-value",
        "TEAMS_TOKEN_CACHE": "your-value",
        "TEAMS_TOKEN_FILE": "your-value",
        "TEAMS_SUBSTRATE_TOKEN_FILE": "your-value",
        "TEAMS_SHAREPOINT_TOKEN_FILE": "your-value",
        "TEAMS_TIME_ZONE": "your-value",
        "TEAMS_OUTPUT_DIR": "your-value",
        "MCP_CONFIRM_MODE": "your-value",
        "MCP_CONFIRM_ELICITATION": "your-value",
        "MCP_CONFIRM_TTL_SECONDS": "your-value",
        "MCP_CONFIRM_SECRET": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "microsoft-teams": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@chrischall/microsoft-teams-mcp"
      ],
      "env": {
        "TEAMS_WS_PORT": "your-value",
        "FETCHPROXY_WS_HOST": "your-value",
        "FETCHPROXY_IDENTITY_DIR": "your-value",
        "TEAMS_ACCESS_TOKEN": "your-value",
        "TEAMS_DISABLE_FETCHPROXY": "your-value",
        "TEAMS_CHATSVC_REGION": "your-value",
        "TEAMS_CHATSVC_BASE": "your-value",
        "TEAMS_CAPTURE_TIMEOUT": "your-value",
        "TEAMS_TOKEN_CACHE": "your-value",
        "TEAMS_TOKEN_FILE": "your-value",
        "TEAMS_SUBSTRATE_TOKEN_FILE": "your-value",
        "TEAMS_SHAREPOINT_TOKEN_FILE": "your-value",
        "TEAMS_TIME_ZONE": "your-value",
        "TEAMS_OUTPUT_DIR": "your-value",
        "MCP_CONFIRM_MODE": "your-value",
        "MCP_CONFIRM_ELICITATION": "your-value",
        "MCP_CONFIRM_TTL_SECONDS": "your-value",
        "MCP_CONFIRM_SECRET": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

TEAMS_WS_PORT env
fetchproxy concentrator port used for the browser bridge. Defaults to 37149, the fleet-wide shared port.
FETCHPROXY_WS_HOST env
Bind interface for the bridge (default 127.0.0.1; a literal IP only, anything else is ignored). Keep on loopback — it exists for ONE topology: a hosted child in its own network namespace.
FETCHPROXY_IDENTITY_DIR env
Where to store the long-term fetchproxy identity keypair (default ~/.fetchproxy/identity/; an absolute path only, anything else is ignored). Exists for a host that runs a separate child per caller, s…
TEAMS_ACCESS_TOKEN secret env
A pre-obtained Teams chat-service bearer token (the JWT itself). Leave blank to capture one from your signed-in Teams browser tab via the ContextMint Bridge extension.
TEAMS_DISABLE_FETCHPROXY env
Set to true to never capture a token from the browser; then TEAMS_ACCESS_TOKEN is required. Leave blank.
TEAMS_CHATSVC_REGION env
The Teams chat-service region in the API path. Defaults to amer. Leave blank unless your tenant lives elsewhere.
TEAMS_CHATSVC_BASE env
Full override for the chat-service API base (default https://teams.cloud.microsoft/api/chatsvc/ /v1). Leave blank.
TEAMS_CAPTURE_TIMEOUT env
Seconds to wait for the Teams tab to issue a chat-service request when capturing a token. Defaults to 30.
TEAMS_TOKEN_CACHE env
Set to false to keep the captured token in memory only. Defaults to on: it is cached so a restart within its ~23h lifetime needs no browser.
TEAMS_TOKEN_FILE env
Where the captured token is cached. Defaults to ~/.microsoft-teams-mcp/token.json.
TEAMS_SUBSTRATE_TOKEN_FILE env
Where the captured Substrate search token is cached. Defaults to ~/.microsoft-teams-mcp/substrate-token.json.
TEAMS_SHAREPOINT_TOKEN_FILE env
Where the captured SharePoint tokens are cached. Defaults to ~/.microsoft-teams-mcp/sharepoint-tokens.json.
TEAMS_TIME_ZONE env
Default IANA time zone (e.g. America/New_York) for time_local on read results. Unset means UTC only.
TEAMS_OUTPUT_DIR env
Folder teams_export_messages writes exports into. Unset means ~/Downloads/microsoft-teams-mcp.
MCP_CONFIRM_MODE env
What the writes (teams_send_message, teams_react, teams_mark_read and the read tools' mark_read) do on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop): "ask-user" (default…
MCP_CONFIRM_ELICITATION env
"off" never shows a confirmation prompt, so every client gets the MCP_CONFIRM_MODE flow. Set it for a client that says it can show prompts but never does. Defaults to on.
MCP_CONFIRM_TTL_SECONDS env
How long a confirmToken stays valid, in seconds. Defaults to 600.
MCP_CONFIRM_SECRET secret env
Signing key for confirmTokens. Random per process by default; set it only if tokens must survive a server restart.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account chrischall, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Chat & emaili

More stars than 0% of the other 1855 servers in this category
Published to the registry more recently than 95% of the other 1855 servers in this category
Basic checks equal to or better than 100% of the other 1855 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Microsoft Teams MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: TEAMS_ACCESS_TOKEN, MCP_CONFIRM_SECRET

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.8.5) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Vexa, emailmd, MCP WhatsApp Cloud

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Vexa

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

by Vexa-aiWidely used★ 2.9KUpdated 2 months ago

Runs in the cloud✓ vexa.ai

Install

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

by anypostGrowing↓ 5.3K/wk★ 1.4KUpdated 32 days ago

Computer or cloud✓ emailmd.dev

Install

MCP WhatsApp Cloud

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

by codesparEarly↓ 63/wk★ 277Updated 5 months ago

Runs on your computer

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

microsoft-teams-mcp

MCP server for Microsoft Teams — list every chat and channel you are in, read any of them by id or name, pull everything you have not read yet, read your Activity feed, fetch inline images, and — each one confirmed by you first — post messages and reactions, using your signed-in browser session.

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

own discretion.

How it works

Chats and channels are read through Teams' own chat-service REST API (https://teams.cloud.microsoft/api/chatsvc/ /v1). The server needs a bearer token for it, and the only place one exists is your signed-in teams.cloud.microsoft tab: through the fetchproxy browser bridge it captures the Authorization header off a request the Teams web app makes to its chat service — once. From then on every call is a plain server-side request; the token is cached in ~/.microsoft-teams-mcp/token.json for its ~23h lifetime (so a restart needs no browser), and a 401 re-captures once and replays. teams.microsoft.com (the old host) is not supported.

So chats and channels no longer need to be open in the browser — any of them can be read by id or name, and listing covers every chat, not just the ones the sidebar shows. To capture a token, an idle tab is not enough: click into any chat so Teams calls its chat service.

The Activity feed comes from the same API. It is a chat-service conversation of its own (48:notifications), so teams_list_activity reads it like any chat — no Activity view (or any view) needs to be open, and nothing reads the page. The bridge is used for one thing only: capturing the token.

By default nothing here marks anything read. Reading a chat through this server leaves your Teams unread badges exactly as they were — unless you ask for it: teams_mark_read, or mark_read: true on teams_list_messages / teams_list_unread_messages, moves your read marker forward. The writes — teams_send_message, teams_react and marking read — go through the same chat-service API and change nothing until you confirm (see Writes).

Pairing

The bridge remembers a pairing only for the exact set of domains it approved, and approving a grant replaces the stored list of header captures. So all of this server's captures (chat service, SharePoint, Substrate search) declare the same scope: the three domains teams.cloud.microsoft, sharepoint.com and substrate.office.com, plus the chat-service and search captures and one capture per SharePoint host the server has already captured from. Each capture still reads only the one header it needs. The SharePoint hosts are remembered in ~/.microsoft-teams-mcp/bridge-scope.json (beside the SharePoint token cache; not written with TEAMS_TOKEN_CACHE=false) once a capture from them succeeds.

Up to 0.7, each capture declared only its own domain, so the bridge asked to pair again (or to update its grants) whenever the server moved between chats, search and files. Upgrading from 0.7 asks to pair once more, for the combined scope; after that it stays paired.

If you run the bridge in more than one browser or browser profile, each one is a different extension identity, and the server trusts only the one it paired with. Keep the bridge enabled in the browser you pair with (or re-pair deliberately with FETCHPROXY_TRUST_NEW_EXTENSION=1 after switching browsers).

SharePoint file download

A shared file in a chat or channel is not in Teams' own object store (where inline images live) — it is in SharePoint, which does not accept the chat-service token. So teams_get_attachment captures a separate SharePoint token and fetches the file through SharePoint's v2.1 shares API, then downloads the pre-signed link it returns (with no token attached).

Two things follow from that:

One pairing covers it. Every capture this server makes — chat service, SharePoint and search — declares the same ContextMint Bridge scope: the domains teams.cloud.microsoft, sharepoint.com and substrate.office.com, and the same list of header captures. So approving microsoft-teams-mcp once covers all three, and moving between chats, files and search never asks again (see Pairing). The first file from a new SharePoint host asks once to grant that host's capture.
Open the file once per SharePoint host. The SharePoint token is captured from the browser's own request to the file's SharePoint host, is short-lived (~53 minutes), and is scoped to one host family. So the first file from a given host in a session may need you to open it once in a signed-in Teams tab (that browser request is what the token is read from); after that the token is cached and refreshed until it expires. A file your account cannot open, or on a SharePoint host your token does not cover, comes back as metadata and its open link rather than failing.

Substrate search

teams_search_messages searches the way the Teams search box does: through Microsoft Substrate (POST https://substrate.office.com/searchservice/api/v2/query). Substrate does not accept the chat-service token either, so search captures a third token — off the request the Teams tab makes to substrate.office.com/searchservice/* when you run a search there — and caches it in ~/.microsoft-teams-mcp/substrate-token.json. As with the other two, it is read only from the request header, never from page storage.

No separate pairing. Search is part of the one bridge scope every capture declares (see Pairing), so the pairing that reads chats covers it.
Run a search in Teams once. The token is read off the Teams tab's own search request, so the first search may need you to type anything into the Teams search box and press Enter while the capture waits (TEAMS_CAPTURE_TIMEOUT, default 30s).
It falls back to scanning. In the default mode: "auto", when no Substrate token can be captured or the search fails, the tool scans recent conversations instead (source: "scan", with a fallback_reason), and does not wait on another capture for 10 minutes. mode: "substrate" fails instead; mode: "scan" never touches Substrate.

It does not re-capture in a loop. If a freshly captured token is still refused (401), the same 10-minute cooldown applies, so auto goes straight to the scan instead of waiting on the bridge every call.

Verified live 2026-10-12. A token captured off the Teams tab's own

search request (it lives about 1.4 hours) was replayed from Node against

read-only queries such as deploy. Confirmed: the request body (cvid, logicalId

and a scenario are required; the sort is `{ Field: "Time", SortDirection:

"Desc" }`), that no header beyond the bearer is needed, the response fields

(conversation in ClientThreadId, a channel root in ClientConversationId's

;messageid=, the message id in InternetMessageId, sender name and SMTP

address but no MRI, a plain-text Preview of at most ~255 characters, an

approximate Total), paging by from/size (up to 200), and that

conversation and since can be sent server-side as ClientThreadId:"…"

and an unquoted sent>=…. from stays client-side: Substrate's own from:

matches word prefixes, not "display name contains". A redacted response is

in tests/fixtures/substrate-query-response.json.

Install

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

Requires the ContextMint Bridge browser extension and @fetchproxy/cli, on a matching major version. Install the bridge from its releases page: in Chrome, unzip the chrome zip and load it unpacked (chrome://extensions → Developer mode → Load unpacked). Safari isn't available yet (it will ship inside the ContextMint app, which has no public download), so use Chrome for now.

ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README (https://github.com/chrischall/fetchproxy#extension) points to it. Its source is public at https://github.com/nullnet-app/contextmint-bridge: build it yourself, or check a release zip against the .sha256 file published beside it (shasum -a 256 -c contextmint-bridge-chrome- .zip.sha256).

npm i -g @fetchproxy/cli

The first call prints a 6-digit pair code to approve in the ContextMint Bridge 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 — by default the token is captured from your browser.

variable	purpose
`TEAMS_ACCESS_TOKEN`	A chat-service bearer token (the JWT itself) to use instead of capturing one. Never re-captured from the browser: when Teams rejects it, replace it.
`TEAMS_DISABLE_FETCHPROXY`	`true` to never capture from the browser (then `TEAMS_ACCESS_TOKEN` is required).
`TEAMS_CHATSVC_REGION`	Chat-service region in the API path. Defaults to `amer`.
`TEAMS_CHATSVC_BASE`	Full override for the API base (default `https://teams.cloud.microsoft/api/chatsvc/ /v1`).
`TEAMS_CAPTURE_TIMEOUT`	Seconds to wait for the Teams tab to issue a chat-service request. Defaults to `30`. The bridge deadline is derived from it (window + 15s).
`TEAMS_TOKEN_CACHE`	`false` to keep the captured token in memory only. Defaults to on.
`TEAMS_TOKEN_FILE`	Where the captured token is cached. Defaults to `~/.microsoft-teams-mcp/token.json`.
`TEAMS_SUBSTRATE_TOKEN_FILE`	Where the captured Substrate search token is cached. Defaults to `~/.microsoft-teams-mcp/substrate-token.json`. `TEAMS_TOKEN_CACHE=false` keeps it in memory too.
`TEAMS_SHAREPOINT_TOKEN_FILE`	Where the captured SharePoint tokens (one per host, used to download shared files) are cached. Defaults to `~/.microsoft-teams-mcp/sharepoint-tokens.json`. `TEAMS_TOKEN_CACHE=false` keeps them in memory too.
`TEAMS_TIME_ZONE`	Default IANA time zone (e.g. `America/New_York`) for the `tz` argument of `teams_list_messages` and `teams_list_unread_messages`: each message then carries `time_local` (ISO 8601 with offset) next to its UTC `time`. Unset means no `time_local` unless `tz` is passed; a name `Intl` does not know is reported as an error.
`TEAMS_OUTPUT_DIR`	Folder `teams_export_messages` (and `teams_get_transcript` with `save`) writes into (each export gets its own timestamped subfolder). Defaults to `~/Downloads/microsoft-teams-mcp`. When set, a per-call `dest` must lie inside it; when unset, `dest` must be under `~/Downloads`, `~/Documents` or `~/Desktop`.
`TEAMS_WS_PORT`	fetchproxy concentrator port. Defaults to `37149`, the fleet-wide shared port.
`FETCHPROXY_WS_HOST`	Bind interface for the bridge (default `127.0.0.1`; a literal IP only, anything else is ignored). Keep on loopback — it exists for ONE topology: a hosted child in its own network namespace.
`FETCHPROXY_IDENTITY_DIR`	Where to store the long-term fetchproxy identity keypair (default `~/.fetchproxy/identity/`; an absolute path only, anything else is ignored). Exists for a host that runs a separate child per caller, so they can share one identity.

Tools

teams_list_conversations — every chat you are in (1:1, group and meeting chats, not just the visible sidebar, plus your 48:notes self-chat as kind self when Teams lists it), favorites and pinned chats first, then most recent activity first: id, kind, title, unread hint, ISO-8601 last-activity time, last-message preview and sender. unread_only (exact — see belo

Only the beginning is shown; read the rest in the repo

Microsoft Teams MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Chat & emaili

Common questions

Alternatives

Vexa

emailmd

MCP WhatsApp Cloud

README from the maker

microsoft-teams-mcp

How it works

Pairing

SharePoint file download

Substrate search

Install

Install in opencode

Configuration

Tools