Microsoft-teams-mcp Server

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

Local serverstdio

What is the Microsoft-teams-mcp Server?

Microsoft-teams-mcp is an MCP integration. Microsoft Teams for Claude — read any chat or channel and its unread messages; send and react.

Packages and local setup

The published npm package is @chrischall/microsoft-teams-mcp, version 0.5.1. Its declared MCP transport is stdio.

The package declares TEAMS_WS_PORT: fetchproxy concentrator port used for the browser bridge. 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.; TEAMS_ACCESS_TOKEN: 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: Set to true to never capture a token from the browser; then TEAMS_ACCESS_TOKEN is required. Leave blank.; TEAMS_CHATSVC_REGION: The Teams chat-service region in the API path. Defaults to amer. Leave blank unless your tenant lives elsewhere.; TEAMS_CHATSVC_BASE: Full override for the chat-service API base (default https://teams.cloud.microsoft/api/chatsvc/ /v1). Leave blank.; TEAMS_CAPTURE_TIMEOUT: Seconds to wait for the Teams tab to issue a chat-service request when capturing a token. Defaults to 30.; TEAMS_TOKEN_CACHE: 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: Where the captured token is cached. Defaults to ~/.microsoft-teams-mcp/token.json.; TEAMS_TIME_ZONE: Default IANA time zone (e.g. America/New_York) for time_local on read results. Unset means UTC only.; MCP_CONFIRM_MODE: 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: the first call returns a preview and a confirmToken, and the model must get your approval in chat before using it), "auto" (the model may use the token after reviewing the preview itself) or "refuse". An unrecognised value is treated as refuse.; MCP_CONFIRM_ELICITATION: "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: How long a confirmToken stays valid, in seconds. Defaults to 600.; MCP_CONFIRM_SECRET: Signing key for confirmTokens. Random per process by default; set it only if tokens must survive a server restart..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.5.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related communication MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
TEAMS_WS_PORTfetchproxy concentrator port used for the browser bridge. Defaults to 37149, the fleet-wide shared port.Check documentation
FETCHPROXY_WS_HOSTBind 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.Check documentation
FETCHPROXY_IDENTITY_DIRWhere 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.Check documentation
TEAMS_ACCESS_TOKENA 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.Check documentation
TEAMS_DISABLE_FETCHPROXYSet to true to never capture a token from the browser; then TEAMS_ACCESS_TOKEN is required. Leave blank.Check documentation
TEAMS_CHATSVC_REGIONThe Teams chat-service region in the API path. Defaults to amer. Leave blank unless your tenant lives elsewhere.Check documentation
TEAMS_CHATSVC_BASEFull override for the chat-service API base (default https://teams.cloud.microsoft/api/chatsvc/ /v1). Leave blank.Check documentation
TEAMS_CAPTURE_TIMEOUTSeconds to wait for the Teams tab to issue a chat-service request when capturing a token. Defaults to 30.Check documentation
TEAMS_TOKEN_CACHESet 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.Check documentation
TEAMS_TOKEN_FILEWhere the captured token is cached. Defaults to ~/.microsoft-teams-mcp/token.json.Check documentation
TEAMS_TIME_ZONEDefault IANA time zone (e.g. America/New_York) for time_local on read results. Unset means UTC only.Check documentation
MCP_CONFIRM_MODEWhat 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: the first call returns a preview and a confirmToken, and the model must get your approval in chat before using it), "auto" (the model may use the token after reviewing the preview itself) or "refuse". An unrecognised value is treated as refuse.Check documentation
MCP_CONFIRM_ELICITATION"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.Check documentation
MCP_CONFIRM_TTL_SECONDSHow long a confirmToken stays valid, in seconds. Defaults to 600.Check documentation
MCP_CONFIRM_SECRETSigning key for confirmTokens. Random per process by default; set it only if tokens must survive a server restart.Check documentation